A PC game can report a high average frame rate and still feel awful for a split second at a time. One common reason is shader compilation: the game suddenly has to prepare GPU programs it has not used before, and the work interrupts normal frame delivery.
That is why "my GPU is fast enough" does not automatically rule shader stutter out. Sustained rendering load and a one-off compilation stall are different problems. A machine that can draw a scene at 120 FPS can still hitch when software pauses to build something the graphics driver needs before it can draw a new effect correctly.
What a shader is doing
Shaders are small programs used by the GPU for jobs such as lighting, materials, shadows and other rendering work. Games typically ship shader code in an intermediate form, but the exact GPU and driver combination on a PC still matters. That code has to become something the installed hardware can execute.
Microsoft's DirectX team describes runtime shader compilation as one of the causes of long first-launch waits and in-game stutter on D3D12 titles. The PC problem is harder than on a fixed console because developers cannot assume every player has the same GPU and driver.
If a game reaches a new visual effect and the required shader is not ready, the system may compile it just in time. The render pipeline waits, the next frame arrives late, and the player sees a hitch. Average FPS barely captures that moment because the rest of the second can still be fast.
Why some games make you wait first
One solution is pre-compilation. A game can spend time before play building the shaders it expects to need, trading an obvious loading screen for fewer compilation interruptions during gameplay. That is the logic behind the now-familiar "compiling shaders" progress bar.
Another approach is caching. Once a particular shader has been compiled for a game, GPU and driver setup, it can often be reused rather than rebuilt every time that exact work is needed. That is why a second run through the same area can sometimes be smoother than the first.
Microsoft's Advanced Shader Delivery pushes the idea further by distributing suitable precompiled shader data for supported Windows games and hardware. Microsoft says the goal is to remove work from first launch and reduce runtime shader stutter, although support depends on the title, storefront and hardware path rather than applying automatically to every PC game.
Not every hitch is shader compilation
This is the important restraint. Asset streaming, CPU spikes, background software, storage delays, memory pressure and plain old bugs can all cause uneven frame delivery too. Seeing a stutter does not prove a shader was compiling.
That is also why deleting shader caches as a universal troubleshooting ritual is bad advice. A cache can be useful precisely because it prevents repeat compilation; clearing it can force work to happen again. Cache resets may be relevant to a specific documented bug, but they are not a generic performance button.
The better mental model is simple: average FPS describes throughput, while frame pacing describes whether frames arrive on time. Shader compilation can damage the second without meaningfully changing the first. When a game pre-compiles successfully—or has already warmed the shaders it needs—the same hardware can suddenly feel much smoother without gaining any headline FPS at all.
Reporting notes