6/18/2023 0 Comments Yuzu switch emulator![]() ![]() ![]() (And we’re glad there are more than two options now.) The usual limitations apply: the cache still asks the driver for validation, so updating it to a newer or older version will require a recompilation, and since the cache is vendor-specific, you won’t get to keep the cache if you switch to a new GPU from another vendor. Possibly due to fewer checks being performed? All GPU vendors see reduced stuttering when facing new shaders! As it turns out, locally stored files are much quicker to save compared to relying on the GPU driver. While the objective was accomplished, the benefits didn’t stop there. NVIDIA and Intel are faster at shader building than AMDīut this isn’t just another fix for AMD Windows users. Booting the game with 25000 shaders used to take close to 15 minutes, with the driver only providing the first 3000 shaders or so, and the rest always being recompiled. This has saved me literal hours of time while playing Xenoblade Chronicles 3 with an RX 6600, as the game has the lovely perk of many heavy shaders. the shaders), and having the usual suspects like the Windows AMD driver fail to store 95% of them because of some arbitrary low size limitation, Wollnashorn decided that doing it with the official Vulkan API is better.īy storing the entire pipeline cache in a custom file among yuzu’s folders, AMD GPUs running on Windows can now properly load large caches in mere seconds, as it should be. ![]() One change that slipped by, made by a new contributor, improved the Vulkan experience so dramatically, it almost feels like cheating… The change is simple: instead of relying on the GPU driver to store and validate the pipeline cache (a.k.a. 1.5, several other GPU related changes had to be delayed. During the time it took to merge last month’s Project Y.F.C. ![]()
0 Comments
Leave a Reply. |