2026.06 - PSO (Pipeline State Object)

Shader hitches are no longer just a shader problem on modern Unity targets. With DirectX 12, Vulkan, and Metal, the engine is dealing with full Pipeline State Objects: the shader plus the surrounding GPU state, including vertex layout and other render-state details. That means a single distinct PSO can trigger driver-level compilation, and if it happens at the wrong moment, the player feels it immediately.

The practical goal is straightforward: move as much compilation as possible out of gameplay and into loading or other controlled phases. In practice, that means profiling a development build for markers like Create GPU Program and enabling shader-compilation logging before chasing the wrong culprit. If a hitch disappears on a clean rerun, that does not prove the problem is gone; Unity and driver caches can mask the issue, so cache clearing and even a reboot may be needed to reproduce it reliably.

The broader takeaway for teams is that newer graphics APIs buy you control and performance potential, but they also add validation work that rarely shows up in a feature roadmap. PSO warm-up, cache-miss testing, and fallback paths become part of shipping discipline, especially when experimental APIs or Addressables complicate the loading flow. The exact implementation details vary, but the operational burden is real: if you do not budget for PSO management early, you end up paying for it in frame-time spikes later.