How Advanced Shader Delivery Reduces Shader Stutter in PC Games
Advanced Shader Delivery reduces shader stutter by supplying compatible, precompiled shaders with a supported PC game's download. Instead of making your computer perform all that compilation when the game starts or a new effect appears, it lets the graphics system reuse work completed beforehand. That can shorten shader preparation screens and prevent compilation from interrupting gameplay.

The important qualification is that it targets a particular cause of uneven performance. Advanced Shader Delivery, or ASD, does not fix every hitch, raise every game's frame rate, or activate automatically across your entire library. The game, delivery platform, graphics hardware and driver must support the process, and the supplied data must cover the rendering work the game actually requests.
Why shader compilation causes stutter
Shaders are programs that run on the GPU and help produce effects such as lighting, shadows and surface appearance. PC games commonly distribute an intermediate form of these programs. The graphics driver then converts that code into instructions suitable for the installed GPU.
In Direct3D 12, shaders are also used within pipeline state objects, or PSOs. A PSO combines shader programs with the settings required for a rendering operation. Preparing that pipeline can involve expensive compilation.
The timing creates the problem. If a game needs a pipeline immediately but its compiled version is unavailable, the frame can be delayed while the driver prepares it. A first encounter with an effect may therefore hitch even when the surrounding gameplay runs smoothly.
Consider a hypothetical game targeting 60 FPS. Its frame budget is approximately 16.7 milliseconds. A single frame taking 70 milliseconds lasts more than four normal frame intervals. That is an illustrative calculation, not a benchmark, but it explains why a brief interruption can feel severe while an average FPS counter still looks healthy.
How Advanced Shader Delivery works
ASD connects information gathered from the game with a GPU vendor's compiler and a storefront's distribution system. The result is a downloadable database containing compiled work appropriate for the player's configuration.
1. Collect the game's pipeline information
The process starts with a State Object Database, or SODB. It records descriptions of the game's pipeline and state objects, together with the intermediate shader code needed to reconstruct them.
This is more useful than a folder of unrelated shader files. A rendering pipeline depends on how its pieces fit together, so the compilation process needs their associated state as well as the shader code itself.
2. Compile the data before the player needs it
GPU vendors supply compiler components that can run outside the game. These turn the collected inputs into a Precompiled Shader Database, or PSDB. Microsoft's delivery approach moves this expensive preparation into the cloud, where the relevant compiled results can be prepared for distribution.
The term “offline compiler” describes compilation outside the running game; it does not mean the player must disconnect from the internet. Nor does it mean a physical example of every target GPU must be rendering the game during compilation.
3. Deliver and register the matching database
The supported installer distributes the appropriate PSDB and registers it on the PC. Direct3D can then locate the database when the game creates its rendering pipelines.
Registration matters: downloading a database is useful only if the runtime can associate it with the right application and compatible hardware environment. ASD is therefore a coordinated installation and graphics feature, rather than a universal cache file players can copy between unrelated computers.
4. Reuse compiled work during play
When a requested pipeline has a compatible precompiled entry, the system can reuse that result instead of performing the full compilation at that moment. Missing entries still need a fallback path.
This is why coverage matters so much. A database that successfully handles most requests can provide a substantial improvement without guaranteeing that every possible scene, graphics option or effect is covered.
How it differs from ordinary shader caching
A conventional driver cache saves compilation results produced on your PC so they can be reused later. It is valuable, but an empty cache does not already contain the work required for a first encounter. NVIDIA also documents that installing a new driver clears its cache, which can bring back first-run stutters.
| Approach | When preparation happens | Main benefit |
|---|---|---|
| Ordinary driver cache | Compiled results are saved after local preparation | Avoids repeating work on later runs |
| In-game precompilation | The game prepares pipelines before they are needed | Moves compilation away from active gameplay |
| Advanced Shader Delivery | Precompiled data arrives through a supported installer | Reduces compilation needed on the player's device |
| NVIDIA Auto Shader Compilation | Supported DirectX 12 shaders rebuild locally during idle time after driver updates | Moves rebuilding away from the next gaming session |
NVIDIA Auto Shader Compilation and Microsoft's ASD address related frustrations through different workflows. Having the NVIDIA feature available does not, by itself, demonstrate that a particular game is receiving an ASD database.
Which PCs and games support Advanced Shader Delivery?
Support status below is checked as of October 3, 2026. Microsoft's October 1 announcement separates available support from expansion scheduled for later in the month. A hardware announcement should not be read as confirmation that every configuration is already enabled.
| Hardware | Documented status |
|---|---|
| AMD RDNA 1, 2, 3, 3.5 and 4 | Supported with Adrenalin 26.6.1 or newer |
| Qualcomm Snapdragon X2 Series | Listed with driver 2026.08.3 or newer |
| NVIDIA RTX GPUs | Expansion announced for later in October; verify rollout before assuming availability |
| Intel Arc B570/B580 and Core Ultra Series 2/3 | Expansion announced for later in October; verify the specific system and driver |
The announcement specifies Windows 11 version 24H2 or newer. Microsoft's AMD rollout documentation additionally lists Xbox Gaming Services version 37.113.11003.0 or newer. Its June update moved that rollout beyond the Xbox Insider preview, so older instructions requiring everyone to join the preview are outdated for that release.
Microsoft's published supported-title list includes games such as Avowed, Forza Horizon 6, Hogwarts Legacy and Starfield. Those examples are not a compatibility guarantee for every GPU, store edition or driver. Check the combination you actually use.
The Xbox PC app is the documented consumer delivery route for these rollouts. Microsoft's APIs are designed to allow other storefronts to participate, but that design does not establish that a Steam or Epic Games Store installation of the same title already receives ASD.
What improvement should you expect?
The clearest potential gains are shorter initial shader preparation and fewer first-use compilation hitches. The effect depends on where a game previously performed that work. A title that compiled extensively before reaching its menu may mainly start faster. Another that encountered pipelines during gameplay may feel smoother when new effects appear.
ASD should therefore be judged using separate questions: did the game become ready sooner, and did disruptive frame-time spikes become less frequent? A faster launch and a higher sustained frame rate are different outcomes.
For a concrete look at that distinction, Tom's Hardware's six-game ASD comparison examines loading and gameplay on a Radeon RX 9070 XT. Its results belong to that test setup, game builds and driver environment; they should not become a promised percentage improvement for another PC.
A useful personal comparison keeps the game version, graphics settings, resolution, power mode and route consistent. Record launch-to-play time separately from gameplay smoothness. A second run may improve because the ordinary cache has warmed up, so a smoother repeat run alone cannot prove ASD caused the improvement.
Why some compilation or stutter can remain
The database may not cover every rendering path
Microsoft's developer guidance distinguishes programmatic collection from manual capture. Manual collection covers the pipelines exercised during the captured play sessions. Other scenes, presets or hardware-specific rendering paths can produce requests that were never recorded.
That explains why developers validate cache hit rates rather than relying only on the presence of a database. Microsoft's statistics APIs expose whether the precompiled cache is serving the requested work. A high hit rate indicates broad reuse; it is not proof that the game has no other performance bottlenecks.
Updates can change the required data
A game patch can introduce new rendering work, while a driver change can require a different compatible compiled result. ASD's installation infrastructure accounts for updates and driver changes, but the relevant database still has to be available and delivered.
The practical implication is that a shader-related message after an update does not automatically mean the entire feature has failed. Check completion of the game and shader downloads, then assess whether the same preparation repeats on subsequent launches.
The slowdown may have another cause
Precompiled shaders do not increase VRAM capacity, repair slow asset delivery, or remove every CPU and GPU bottleneck. Treat ASD as a solution to compilation delays, not a replacement for diagnosing persistent performance problems.
For example, thermal throttling reduces processor speed to control temperature. If performance deteriorates as a session continues and temperatures rise, PC overheating checks are more relevant than repeatedly deleting shader files.
How to check whether ASD is helping your game
- Confirm support for the actual installation. Check the title, storefront, Windows version, graphics hardware and driver together.
- Complete pending updates. Update the Xbox PC app, Gaming Services and the game, and use a supported graphics driver. Let associated downloads finish before evaluating a first launch.
- Look for the launch indicator. Microsoft documents the message “Precompiled shaders installed” in the launch window when ASD is working.
- Observe the original symptom. Check the preparation screen or repeat the scene where the first-use hitch occurred. Keep settings unchanged while comparing behavior.
- Investigate persistent problems separately. If the indicator appears but the game still hitches, record the affected scene, settings and versions for the game's support team.
Avoid clearing a healthy shader cache as routine maintenance. The cache exists to preserve useful work, and removing it can force that work to be recreated. Reserve a reset for a specific troubleshooting reason or instructions from the relevant developer or hardware vendor.
Frequently asked questions
Does Advanced Shader Delivery increase average FPS?
It can improve measurements affected by compilation stalls, but a universal average-FPS increase is not its purpose. Evaluate startup time and frame-time consistency separately from sustained rendering performance.
Can I force ASD on in an unsupported game?
A generic Windows tweak cannot supply a missing, compatible PSDB. The developer, compiler support and distribution process must provide the required data. Treat claims of an all-games activation switch skeptically.
Does cloud compilation mean the game is cloud-streamed?
No. The compilation output is downloaded for use by the locally running game. ASD does not move gameplay rendering to a remote server. Any separate online or offline-play restrictions still depend on the game and its launcher.
Will changing graphics settings undo the benefit?
Not necessarily. Settings can select different rendering pipelines. If those pipelines are represented in the compatible database, they can benefit too; otherwise, additional preparation may be needed. Keep settings fixed when investigating a particular hitch.
Start with compatibility, then check the result
For a supported installation, finish the required downloads, check the precompiled-shader indicator and revisit the moment that previously stuttered. If the problem persists, use its timing and repeatability to guide the next investigation. That gives you a useful answer about your game without confusing shader delivery with a cure for every performance issue.