Shader Compilation Stutter vs Traversal Stutter Explained
Published
On this page
Modern PC games suffer from two different kinds of stutter, and fixing them means telling them apart: shader compilation stutter is a first-time hitch when the CPU compiles a new graphics shader on the spot, and it fades as the shader cache fills; traversal stutter is a streaming hitch that recurs whenever you move into a new area and the game loads assets from disk. Shader stutter is CPU-bound and cured by a warm cache; traversal stutter is storage/memory-bound and cured by faster storage and more headroom. This guide explains what causes each, how to identify which one you have, and how to reduce both.
Why a game with high FPS still stutters
A game can report 150 FPS and still feel awful, because average FPS hides individual bad frames. Stutter is one frame that takes far too long to build — a frametime spike — and a single 60ms frame in a stream of 6ms frames is a visible jolt no matter how high the average is. That’s why smoothness is measured by 1% lows and frametimes, not average FPS. The two spikes below are the most common causes in 2024–2026 titles.
| Shader compilation stutter | Traversal stutter | |
|---|---|---|
| Cause | CPU compiling a shader it hasn’t prepared | Streaming assets from disk into memory |
| When | First time an effect/area/weapon appears | Every time you enter a new area or fast-travel |
| Does it fade? | Yes — as the shader cache fills | No — recurs on each new region |
| Bound by | CPU (and shader cache) | Storage + RAM/VRAM |
| Fix direction | Precompile, warm cache, more cores | Faster SSD, more RAM/VRAM, lower settings |
Shader compilation stutter
Shader compilation stutter is a hitch that happens the first time the game needs a graphics shader it hasn’t compiled yet. Shaders are small programs the GPU runs for every visual effect — lighting, particles, a gun muzzle flash. Before the GPU can run one, the CPU has to compile it from the game’s intermediate code into instructions for your specific GPU. If the game didn’t compile it ahead of time, it compiles it the moment the effect first appears, delaying that frame by anywhere from a few to tens of milliseconds.
Tell-tale signs:
- Hitches in the first hour of a new game, or right after a driver update (which can invalidate the shader cache).
- A hitch the first time you see a new weapon, spell, or explosion — then that exact moment is smooth on replay.
- It gets better with playtime as more shaders land in the cache.
How to reduce it:
- Let the shader pre-compilation step finish. Many DX12/UE games run a “compiling shaders” pass at launch or first load — don’t skip it.
- Don’t clear the shader cache without reason. A clear forces everything to recompile. Only clear it to fix corruption — see how to clear shader cache to fix stuttering for when it’s actually the right move.
- Give the CPU cores to work with. Compilation is multi-threaded; close background apps eating CPU so compilation finishes faster and off the critical frame.
- Keep drivers current but stable — update for a game’s launch, then leave it alone so the cache stays warm.
You can’t fully eliminate it, because some shaders only appear in rare situations, but a complete first playthrough builds most of the cache.
Traversal stutter
Traversal stutter is a hitch that happens as you move through the world and the game streams new data from disk — textures, meshes, level chunks — into RAM and VRAM. Because you keep entering new areas, it does not fade with playtime: crossing the same bridge or fast-traveling to the same city hitches every time.
Tell-tale signs:
- Hitches that track your movement — sprinting into a new district, opening a door to a new zone, fast-travel loads.
- Recurs at the same thresholds each time, not just on first sight.
- Worse on a hard drive or slow SATA SSD, or when VRAM/RAM is full and the game is constantly evicting and reloading assets.
How to reduce it:
- Install the game on an NVMe SSD. Streaming from an NVMe drive instead of a HDD is the single biggest fix for traversal hitches.
- Free up VRAM and RAM. Lower texture quality by one step if you’re near your VRAM limit, and make sure you have enough system RAM at the right speed so the game isn’t thrashing — see does RAM speed increase FPS if you have one.
- Turn down streaming-heavy settings — texture streaming pool, view distance, and volumetric detail all raise the data rate the engine must stream.
- Cap your frame rate just below your refresh rate so the GPU isn’t maxed out while the engine is trying to stream — a stable cap gives streaming headroom. See best FPS cap for low latency.
Getting to consistent frametimes
Both stutters are frametime spikes, and both add felt input delay at the moment they hit — the frame you’re looking at is late, so your input lands late. Beyond the two fixes above, the general smoothness levers apply: eliminate driver-level micro-stutter (NVIDIA / MPO flicker), keep a consistent frame cap, and keep the OS timer tight so frame pacing doesn’t drift — the higher and steadier your frame delivery, the smaller every remaining hitch feels. The goal is never the biggest average FPS number; it’s the flattest frametime line.
Related guides
Frequently asked questions
What is shader compilation stutter?
Shader compilation stutter is a brief freeze that happens the first time a game needs a graphics shader it hasn't prepared yet. The CPU has to compile that shader into GPU code on the spot, which takes a few milliseconds to tens of milliseconds, and the frame it was building is delayed — you see a hitch. It's worst in the first hour of a new game or right after a driver update clears the shader cache, and it fades as more shaders get compiled and cached.
What is traversal stutter?
Traversal stutter is a hitch that happens as you move through a game world and it streams new assets — textures, meshes, and level data — from disk into memory. Unlike shader stutter, it doesn't go away with playtime, because you keep entering new areas that need new data loaded. It's common in large open-world games, especially on slow storage or when system RAM and VRAM are tight.
How do I know which stutter I have?
Shader compilation stutter happens the first time you see a new effect, weapon, or area and then stops recurring in that same spot — replay a section and the hitch is gone. Traversal stutter recurs every time you cross the same threshold or fast-travel, because the streaming happens each time. If a shader-precompile step or a cache clear removes the hitches, it was shader stutter; if hitches track your movement and storage activity, it's traversal stutter.
Can you fix shader compilation stutter?
Partly. Let the game's shader pre-compilation step finish before playing, keep your GPU drivers current but avoid clearing the shader cache unnecessarily (a clear forces recompilation), and make sure the game can use multiple CPU cores to compile. On DirectX 12 titles a full first playthrough builds most of the cache, after which the stutter largely disappears. You can't eliminate it entirely because some shaders only appear in specific situations.
Does more RAM or a faster SSD fix stutter?
A faster SSD and more RAM mainly help traversal stutter, not shader stutter. Streaming assets from an NVMe SSD instead of a hard drive, and having enough system RAM and VRAM so the game isn't constantly evicting and reloading data, both reduce streaming hitches. Shader compilation stutter is CPU-bound — it's about compiling code, not loading files — so it benefits from more CPU cores and a warm shader cache, not from storage speed.