Start by checking when the hitch happens. A pause the first time an effect appears, after a game or graphics-driver update, or while entering a new area points to different possible causes—and shader compilation is only one of them. Repeating the same scene after a warm-up run is a useful first check, not proof of the cause.
First, match the hitch to its trigger
Use the timing and trigger to decide what to check next. A player-visible hitch alone cannot tell you whether the cause is shader compilation, asset loading, or something else.
| When it happens | What it may indicate | Useful check |
|---|---|---|
| The first time you see an effect, material, or scene element | The game may be compiling a shader or creating a graphics pipeline state (PSO) when it needs to draw it. | Replay the same area or trigger the same effect after the initial run and compare. |
| On the first run after a game or driver update | Cached shader work may need to be rebuilt or repopulated. | Allow a warm-up run, then repeat the same route or scene. |
| While moving into a new area, loading assets, or encountering many actors | Streaming, synchronous loading, spawning, or other game-side work may cause a frame-time spike. | Note whether the hitch follows a location or gameplay event rather than a first-use visual effect. |
| In the same scene on every run, or in several unrelated games | A one-time cache warm-up is less likely to explain the whole problem. | Record the game, graphics API if known, driver state, scene, and whether the hitch repeats after warm-up; check game-specific support guidance. |
Why shaders and PSOs can hitch
A shader tells the graphics hardware how to render an effect or surface. A PSO, or pipeline state object, combines rendering settings the game needs for a draw. If the game discovers it needs a shader or PSO at the moment it must render something, compilation can delay frame delivery.
Unreal Engine engineers describe the timing plainly: “Shader compilation stuttering happens when a render engine discovers that it needs to compile a new shader right before it uses it for drawing something, so everything stops while waiting for the driver to finish compilation.” Epic’s February 2025 explanation also notes that driver and engine caches cannot eliminate every case of work arriving too late.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- Powered by Radeon RX 9070 XT
- WINDFORCE Cooling System
- Hawk Fan
- Server-grade Thermal Conductive Gel
- RGB Lighting
Drivers can keep compiled shaders so later runs can reuse them. That is why an initial run—or a run after a driver update—may behave differently from a later run. AMD’s Adrenalin Edition 26.9.2 background shader compilation FAQ recommends allowing about 15 minutes of gameplay before capturing performance measurements for that feature. Treat this as AMD’s recommendation, not a guaranteed warm-up period for every game, GPU, or PC. AMD’s feature FAQ
Try a warm-run comparison before changing caches
- Choose a repeatable trigger. Use the same save, route, effect, or area where the hitch occurred.
- Play through it once. Note whether the hitch occurs on first use, after an update, or at a location transition.
- Repeat the trigger. If the hitch is materially reduced, cache warm-up is consistent with the symptom, but does not prove shader compilation was the cause.
- If it persists, broaden the diagnosis. Check whether the hitch follows loading or spawning, whether the game recently updated, and whether the same issue appears in unrelated games. Use the game’s support guidance for game-specific steps.
Repeatedly deleting shader caches is not a general optimization. Deletion can force the game and driver to rebuild work that could otherwise be reused.
When clearing a shader cache may help
Cache clearing is a targeted troubleshooting step, not a universal fix. Epic Support documents a specific case: Fortnite can repeatedly recompile DirectX shaders in DX12, causing heavy stuttering, and clearing the shader cache may address it. Epic’s instructions vary by GPU vendor; follow the current steps on its Fortnite DX12 support page rather than applying those paths to other games. The first match after clearing may still stutter while shaders are rebuilt.
Rank #2
- NVIDIA Ampere Streaming Multiprocessors: The all-new Ampere SM brings 2X the FP32 throughput and improved power efficiency.
- 2nd Generation RT Cores: Experience 2X the throughput of 1st gen RT Cores, plus concurrent RT and shading for a whole new level of ray-tracing performance.
- 3rd Generation Tensor Cores: Get up to 2X the throughput with structural sparsity and advanced AI algorithms such as DLSS. These cores deliver a massive boost in game performance and all-new AI capabilities.
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure.
- OC Mode : 1500 MHz (Boost Clock)/Default Mode : 1470 MHz (Boost Clock)
NVIDIA says its driver shader cache stores compiled shaders for reuse, and that a size limit set too low can evict shaders still in use and contribute to stuttering. Check the current driver interface and your own configuration before changing the limit; there is no one cache-size setting established here as right for every player. NVIDIA’s driver settings reference
When the hitch follows movement through the world
A hitch on entering a new area, loading assets, or triggering a burst of actors is not automatically a shader problem. Epic’s Unreal Engine engineers identify synchronous loading, excessive spawning, and streaming content into a scene as other sources of frame-time spikes. These causes may require changes by the game developer; buying more GPU, RAM, storage, or cooling hardware is not a diagnosis and is not established as a general fix.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.For developers: investigate and reduce late PSO work
Unreal Engine 5.8’s PSO precaching system gathers potential render pipeline states and compiles them asynchronously ahead of use. It can reduce runtime hitches, but it also consumes system memory and background processing time, so validate the trade-off on target hardware. Epic recommends considering outstanding precache requests during loading screens, and provides logs and Unreal Insights timers to find PSOs that were missed or completed too late. The documented default runtime PSO hitch threshold is 20 milliseconds; it is an engine diagnostic default, not a universal threshold for human perception. UE 5.8 PSO Precaching documentation
Rank #3
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
For a bundled PSO cache workflow, collect states during playtests and compile them earlier. The cache is graphics-API-specific, and Epic cautions that a build should be assessed with a current cache. Even good precaching cannot cover every possible state or eliminate traversal hitches caused by loading and streaming. Epic’s Fortnite example describes a driver-cache-empty load taking around 20–30 seconds longer to enter a Battle Royale match; that is an example from that game, not a general UE5 loading-time figure. Epic’s UE 5.8 performance considerations Epic’s engineering article
What to record if stuttering continues
- Whether the hitch occurs on first use, after an update, or every time.
- The specific trigger: an effect or material, entering an area, loading, or a burst of spawned objects.
- The game, graphics API if known, and whether the issue occurs in other games.
- Whether repeating the same route after a warm run changes the hitch.
- Any relevant game-specific support guidance. For a development build, inspect PSO logs and Unreal Insights for late or missed precache work.
There is no established percentage of UE5 games that stutter, and no single fix applies to every game. The useful next step is evidence about timing and repeatability: it helps distinguish cache warm-up from a recurring game or traversal hitch.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
