Updated November 2, 2026
Waiting for shaders to compile when you first launch Phantom Blade Zero on PC can be frustrating. But having to repeat the same process every time you open the game is an entirely different problem.
Some players find that shader compilation restarts on every launch, even after they have already completed it and played the game successfully. Instead of reaching the main menu, they face another lengthy wait that can last 20 minutes or longer.
The issue has been particularly noticeable on Intel Arc graphics cards, although similar behavior has also occurred on other GPU configurations.
One temporary workaround involves adding -noraytracing to Steam's launch options. This has helped some players bypass repeated shader compilation, but it disables ray tracing and is not guaranteed to work on every PC.
This guide explains how to try that workaround, distinguish normal shader preparation from repeated compilation, and troubleshoot the problem without making unnecessary changes to your system.
📋 Table of Contents
- Why Shaders Compile Every Launch
- Fix 1: Try -noraytracing in Steam
- Fix 2: Check After a Windows Restart
- Fix 3: Check GPU Driver & Game Updates
- Intel Arc, AMD and NVIDIA: Which GPUs?
- Shader Compilation Stuck at 77%?
- Should You Delete the Shader Cache?
- Has S-GAME Released a Fix?
- What to Do If Nothing Works
- Frequently Asked Questions
Quick Answer: How to Stop Phantom Blade Zero Compiling Shaders Every Launch
If Phantom Blade Zero recompiles shaders every time you start the game, try the following:
- Open Steam and go to your Library.
- Right-click Phantom Blade Zero.
- Select Properties.
- Open the General tab.
- Find the Launch Options field.
- Enter -noraytracing.
- Close the Properties window and launch the game.
- Check whether shader compilation still appears.
- Close and relaunch the game to see whether the improvement persists.
Important: The -noraytracing option is intended to disable ray tracing. It is a temporary workaround that has helped some players, particularly those using Intel Arc GPUs. It is not a confirmed universal fix.
If you already have other Steam launch options, preserve them and add -noraytracing as a separate argument.
To reverse the change, remove the argument from Steam's Launch Options.
Why Phantom Blade Zero Compiles Shaders Every Launch
Shader compilation prepares graphics instructions that help the game render its environments, lighting, effects, and other visual elements.
This preparation can take time, particularly when launching a game for the first time.
However, the same lengthy compilation should not normally be necessary every time you start the game under an unchanged configuration.
When shader compilation may be normal
A lengthy shader-compilation process can occur after:
- Installing and launching the game for the first time.
- Updating your graphics driver.
- Installing a game update that changes relevant rendering components.
- Making certain changes that require shaders to be rebuilt.
In these situations, shader preparation does not necessarily indicate a bug.
When repeated compilation becomes a problem
The more concerning situation is when the game:
- Completes shader compilation.
- Successfully reaches the main menu.
- Runs normally during gameplay.
- Closes without an apparent problem.
- Starts the same lengthy compilation again on the next launch.
This behavior may indicate that previously prepared shader data is not being reused as expected.
However, the exact technical cause has not been established. Repeated compilation does not automatically prove that a particular shader-cache file is missing or corrupted.
Identify your problem first
| What happens | What to do |
|---|---|
| Shaders compile on the first launch | Allow the process to complete if it is progressing normally |
| Compilation returns after a driver update | Check whether it happens again on the next launch |
| Shaders compile every time you open the game | Try the Steam launch-option workaround |
| Compilation returns after restarting Windows | Follow the Windows restart test below |
| Compilation freezes or the game crashes | Troubleshoot it as a possible startup failure |
If your game recompiles shaders on every launch without a driver or game update, continue to the next section.
Fix 1: Try -noraytracing in Steam Launch Options
One workaround for repeated shader compilation is to start Phantom Blade Zero with ray tracing disabled.
You can test this by adding the following argument to Steam:
-noraytracing
Some Intel Arc users have found that this allows the game to reach the main menu without repeating the lengthy compilation process.
How to add -noraytracing in Steam
- Close Phantom Blade Zero if it is running.
- Open the Steam desktop application.
- Select Library.
- Find Phantom Blade Zero in your game list.
- Right-click the game and select Properties.
- Under General, locate Launch Options.
- Enter -noraytracing.
- Close the Properties window.
- Launch Phantom Blade Zero normally.
Already using other launch options?
Do not delete your existing arguments. Add -noraytracing as a separate argument, leaving a space between launch options.
If the change causes problems, remove only the argument you added.
How to check whether it worked
Do not judge the result from a single launch.
Instead:
- Launch the game with the new option.
- Check whether it reaches the main menu without the usual lengthy compilation.
- Close the game normally.
- Launch it again.
- Check whether shader compilation returns.
If the game opens normally on subsequent launches, the workaround may be helping your configuration.
For a more complete test, restart Windows and launch the game again.
What does -noraytracing change?
The -noraytracing launch argument is intended to start the game without ray tracing.
Ray tracing is used for certain advanced lighting and rendering effects. Disabling it may change how some visual effects appear.
On some systems, starting the game without ray tracing also appears to prevent repeated shader compilation.
However, the exact effect can depend on the game's rendering configuration.
The trade-off is that you may avoid repeated shader preparation, but you will not be using ray-traced rendering features while the option is active.
If you want to use ray tracing again, remove the launch option and test the game after future updates.
How to remove -noraytracing
- Open Steam → Library.
- Right-click Phantom Blade Zero.
- Select Properties → General.
- Find Launch Options.
- Delete -noraytracing.
- Leave any unrelated launch arguments unchanged.
- Close the Properties window.
The game will then launch without that override.
What if -noraytracing does not work?
If shader compilation still restarts every time, remove the argument if you do not want ray tracing disabled.
The workaround is not effective on every system, and repeatedly adding the same argument will not necessarily change the result.
Continue with the diagnostic steps below.
Fix 2: Check Whether It Happens After a Windows Restart
Not every repeated shader-compilation problem follows the same pattern.
Some players experience recompilation whenever they open the game. Others find that a second launch works normally, but compilation returns after restarting Windows.
Testing this difference can help you describe the problem more accurately.
How to test the restart pattern
- Launch Phantom Blade Zero.
- Allow shader compilation to finish if necessary.
- Reach the main menu.
- Close the game normally.
- Launch it again without restarting Windows.
- Note whether shader compilation returns.
- Close the game.
- Restart Windows.
- Launch Phantom Blade Zero again.
- Compare the result.
What the results mean
| Test result | Possible interpretation |
|---|---|
| Compilation happens on every launch | Matches the recurring compilation problem |
| Second launch works, but compilation returns after reboot | Suggests a restart-related pattern |
| Compilation happens only after a driver update | May be expected shader rebuilding |
| Compilation does not return | The issue may have been temporary |
This test does not identify the exact cause. It helps distinguish different symptoms that may require different fixes.
If the issue occurs only after restarting Windows, include that detail when reporting it to the developer.
Fix 3: Check GPU Driver and Game Updates
Graphics drivers and game updates can affect shader compilation.
If the problem started after a recent update, it is worth checking whether a newer version addresses the behavior.
Check your graphics driver
Identify your GPU manufacturer:
- Intel Arc: Check Intel's official graphics driver updates.
- AMD Radeon: Check AMD Software and the official driver release notes.
- NVIDIA GeForce: Check NVIDIA's official driver updates.
Look for fixes related to Phantom Blade Zero, shader compilation, or game compatibility.
Avoid repeatedly reinstalling or rolling back drivers without a clear reason.
Check Phantom Blade Zero updates
In Steam:
- Open Library.
- Select Phantom Blade Zero.
- Check whether an update is available.
- Install the update if necessary.
- Launch the game.
- Test whether compilation still repeats.
A game update may require shaders to compile again once.
The important question is whether the same lengthy process returns on every subsequent launch.
Should you verify game files?
If the game also crashes, fails to start, or behaves abnormally, verifying the installed files is a reasonable troubleshooting step.
To do this:
- Right-click Phantom Blade Zero in Steam.
- Open Properties.
- Select Installed Files.
- Choose Verify integrity of game files.
- Wait for Steam to finish.
Verification can identify missing or damaged game files, but it is not a confirmed fix for the repeated shader-compilation problem.
If your main issue is in-game stuttering rather than startup compilation, see our Phantom Blade Zero Stuttering on PC? Path Tracing & RTX Fixes.
Intel Arc, AMD and NVIDIA: Which GPUs Are Affected?
Repeated shader compilation is not necessarily limited to one graphics card manufacturer.
The issue has appeared on several GPU configurations, with particularly noticeable cases involving Intel Arc cards.
Intel Arc
Affected configurations have included Intel Arc A750, A770, and B580 systems.
Some Intel Arc users have been able to bypass repeated compilation using the Steam launch-option workaround.
However, not every Intel Arc system responds the same way.
If you use Intel Arc, the argument is a reasonable first option to test because it is reversible.
AMD Radeon
Similar repeated-compilation symptoms have occurred on AMD Radeon configurations.
However, there is not enough evidence to establish that the same workaround works consistently on AMD systems.
If you use AMD, you can test it, but do not assume that the cause is identical to the Intel Arc issue.
If you are experiencing visual defects such as white squares or broken character hair rather than shader compilation delays, see our Phantom Blade Zero AMD Graphics Bugs: White Squares & Broken Hair Fixes.
NVIDIA GeForce
NVIDIA users can also encounter long shader preparation or repeated compilation.
The available information does not establish a universal NVIDIA-specific solution for the recurring problem.
Check whether compilation happens after driver updates or on every launch before changing settings.
Is this an Intel-only bug?
No. Similar symptoms have appeared across different GPU brands.
However, that does not prove every affected system has the same underlying technical problem.
Shader Compilation Stuck at 77%?
A separate startup problem occurs when shader compilation reaches a certain percentage and stops progressing.
For example, some players encounter compilation stopping around 77% before the game reaches the main menu.
The 77% figure is one reported example, not a universal failure point. Shader compilation can stall at other percentages, and the underlying cause may differ from the repeated-compilation issue.
What should you do?
First, determine whether the percentage is genuinely stuck or simply progressing slowly.
If the game is still responding and the compilation percentage occasionally changes, allow more time for the process to finish.
If the game crashes, closes unexpectedly, or repeatedly fails at the same point:
- Restart the game once.
- Check for available game updates.
- Check whether your graphics driver is current.
- Verify the game files through Steam.
- Test whether the problem persists.
You can also try the -noraytracing option, but there is no confirmed guarantee that it resolves compilation freezing at 77%.
If Phantom Blade Zero closes before reaching the main menu, follow our Phantom Blade Zero Won't Launch on PC? Startup Crash & Denuvo Fixes.
What if your PC shuts down completely?
A complete system shutdown is different from a game freezing during shader compilation.
Do not repeatedly restart the game if your entire PC powers off during the process.
Check for system stability, cooling, power-related issues, and hardware errors before trying again. If the shutdown repeats, investigate the underlying system problem rather than treating it as a normal shader-loading delay.
Should You Delete the Shader Cache?
You may see suggestions to clear the DirectX Shader Cache or delete game-specific shader files when compilation takes too long.
However, deleting cached shader data generally means that shaders must be prepared again.
If your problem is that Phantom Blade Zero recompiles shaders on every launch, deleting the cache may simply create another lengthy compilation.
Does clearing the cache fix repeated compilation?
There is no verified cache-clearing procedure established as a permanent solution for this specific problem.
The exact cause of the repeated compilation has not been confirmed, so it is not possible to say that a particular cache folder is responsible.
What should you avoid?
Do not:
- Delete unknown game configuration files.
- Modify undocumented shader-cache settings.
- Download replacement shader files from untrusted sources.
- Change Windows registry settings based on unverified fixes.
- Repeatedly clear shader caches without testing whether the behavior improves.
Start with the reversible Steam launch option and basic update checks instead.
Has S-GAME Released a Shader Compilation Fix?
Status as of November 2, 2026: No confirmed permanent fix for repeated shader compilation.
The recurring shader-compilation problem has been acknowledged in an official Steam discussion response, with the issue forwarded for investigation.
However, that acknowledgement does not establish that a patch has already resolved it.
The -noraytracing launch option remains a community workaround rather than an official permanent repair.
What to check after future updates
After installing a new Phantom Blade Zero patch:
- Read the update notes for shader-compilation or rendering fixes.
- Remove -noraytracing temporarily if you want to test the default rendering path.
- Launch the game and allow any necessary shader preparation to finish.
- Close the game normally.
- Launch it again.
- Check whether the lengthy compilation returns.
- Restart Windows and repeat the test if necessary.
If repeated compilation continues, you can restore the workaround if it previously helped your system.
What to Do If Nothing Works
If shader compilation continues on every launch, document the problem and report it to the developer.
Include:
- Your GPU model.
- Graphics driver version.
- CPU and RAM.
- Windows version.
- Game version.
- Approximate shader-compilation duration.
- Whether it happens on every launch or only after restarting Windows.
- Whether the issue started after a game or driver update.
- Whether -noraytracing changes the behavior.
- Whether the game reaches the main menu successfully.
A short recording showing the compilation screen across consecutive launches may help demonstrate the issue.
You can submit a report through the official Phantom Blade Zero support site.
While waiting for an official solution, avoid repeatedly changing unrelated system settings. Keep track of which troubleshooting steps actually change the behavior.
Frequently Asked Questions
Why does Phantom Blade Zero compile shaders every time I launch it?
Repeated shader compilation can occur even after the game has successfully completed the process. The exact cause has not been confirmed, although the behavior may involve shaders not being reused as expected.
How do I stop Phantom Blade Zero recompiling shaders?
Try adding -noraytracing to Steam's Launch Options. This has helped some players bypass repeated compilation, particularly on Intel Arc hardware. It is a temporary workaround and may not work on every PC.
What does -noraytracing do?
The argument is intended to disable ray tracing when launching the game. On some configurations, it may also help avoid repeated shader preparation.
Is -noraytracing safe to remove?
Yes. You can remove the argument from Steam's Launch Options at any time. The game will then launch without that override.
Does -noraytracing work on AMD and NVIDIA GPUs?
It can be tested on different GPU brands, but there is not enough evidence to establish that it reliably fixes repeated compilation on AMD or NVIDIA systems.
Is shader compilation normal after updating graphics drivers?
Yes, shader preparation may be required after a graphics driver update. The more concerning behavior is when the same lengthy compilation returns on every launch without further changes.
Why does shader compilation return after restarting Windows?
Some systems experience repeated compilation specifically after a Windows restart. The precise cause has not been established. Testing a second launch before and after restarting Windows can help identify this pattern.
Should I delete the DirectX Shader Cache?
Not as a first step for this problem. Deleting cached shaders can force another compilation, and there is no confirmed evidence that clearing the cache permanently resolves the repeated-launch issue.
Has S-GAME fixed the shader compilation bug?
The issue has been acknowledged for investigation, but a permanent fix has not been confirmed as of November 2, 2026.
Final Thoughts
If Phantom Blade Zero recompiles shaders every time you launch it, first distinguish normal shader preparation from the repeated startup problem.
The most practical workaround to test is -noraytracing in Steam Launch Options, particularly if you use an Intel Arc GPU. Remember that it disables ray tracing and does not work for everyone.
If compilation returns after every Windows restart, test that behavior separately. Check official driver and game updates, but avoid deleting shader caches or modifying undocumented settings without a confirmed reason.
Bottom line: Until S-GAME provides a permanent fix, use the workaround only if it improves your system and check future updates for an official resolution.
Comments
Post a Comment