Vulkan is more like the foundation for graphics libraries like SDL. It's a lot of low-level code that isn't needed if all you need is a rectangle to display some pixels on.
If you can still get XP drivers for your new PC then you could install XP on a separate partition (reduce the main partition first with e.g. a Linux boot CD and gparted) or on a separate HDD.
My original complaint is not about what kinds of glitches are used, but how they are triggered. Are they triggered via gameplay or via non-gameplay.
Then what is gameplay? For the game there is no definite technical distinction except "byte X being Y means controller input moves the player sprite and the byte being Z uses controller input for doing something else".
Navigating the menus is often an indistinguishable part of playing the game, e.g.
- using a JRPG's inventory
- de-/activating suit functions in Super Metroid
- using the built-in save&reset function in Link's Awakening while the shopkeeper subtracts your money
Why would accurate emulation influence that?
The RNG always behaves the same when given the same input unless the savestate loading doesn't restore the entire system state (which would be a bug).
Hi. One similar question again: since there have been already several H.265 encoders (such as x265) in use, has anyone tested how H.265 performs on TAS movies compared to H.264 that we currently use? When do you think might H.265 start to replace H.264 here? Thank you. :)
I'm not sure if anyone has done the testing yet. I personally have not played around with it, though I really should. Eventually if it is better, I could see a move to it.
→ 
