| Pros | Cons | |------|------| | Completely removes shader stutter | Temporary invisible objects/textures | | No need for a full cache | Some particle effects may flash | | Works well on high-core CPUs | Rare crashes with specific games |
For Tears of the Kingdom, async pipeline is considered mandatory. For Fire Emblem: Three Houses, it causes crashes – test per game.
Here is where the performance issue arises. Translation takes time. shader cache yuzu
When you encounter a new effect in a game for the first time—let's say a specific explosion animation—Yuzu realizes it hasn't translated that code yet. It pauses the game for a fraction of a second to compile the shader. Once compiled, it renders the explosion.
While this happens, the game freezes. This is what emulator enthusiasts call shader compilation stutter. | Pros | Cons | |------|------| | Completely
Most people talk about "shader cache," but Yuzu actually builds two things:
The pipeline cache is like the stage manager in a theater. Even if you know every line (shader), if you don’t know when to walk on stage (pipeline), you’ll trip. Yuzu’s pipeline cache prevents micro-stutters—those tiny 10ms hiccups that make a game feel "off." Here is where the performance issue arises
Yuzu supports two primary graphics APIs: OpenGL and Vulkan. They handle shaders very differently.
| Feature | OpenGL | Vulkan | | :--- | :--- | :--- | | Shader Compilation | Typically slower, more noticeable stutter. | Faster, smoother compilation. | | Cache Sharing | Easy to share between different GPUs. | Highly specific to your exact GPU driver version. | | Initial Stutter | High. | Low to Medium. | | Best For | Older games, Intel integrated graphics. | Most modern games. The Legend of Zelda series. |
Verdict: Always use Vulkan for shader caching unless you have a specific compatibility issue. Vulkan’s pipeline cache is more efficient, and while the stutters are still there, they are less violent than on OpenGL.