Start here

First separate a long compilation from a crash. Use the repair sequence below for actual failures.

  1. Verify WARDOGS files in Steam.
  2. Install the current stable NVIDIA, AMD or Intel graphics driver.
  3. Run the bundled Elytra setup and choose Repair.
  4. Restart Windows, then test one clean launch.

Team17 has used this same first-line sequence for current launch and shader-stage failures. A shader crash does not prove that the shader cache itself is corrupt.

Confirm that the failure really happens at shader compilation

Progress bar crashesRecord the percentage and any crash code before changing files.
Grey screen before the barTreat it as a launch-stage failure and use the same safe repair order.
WD-L code firstUse the error-code guide; the launcher or Elytra may be failing before Unreal reaches shaders.
Whole PC restartsStop repeated launches and check Windows reliability and hardware stability first.

A visible “compiling shaders” screen describes where the game stopped, not one guaranteed root cause. Driver state, game files, Elytra and unstable clocks can all overlap with the same symptom.

Why is WARDOGS compiling shaders every time?

Season 2 players report compilation returning on successive launches, sometimes without a crash. Those reports do not prove one universal cache defect. A slow first run after an update, a repeated full compilation on an unchanged setup and a progress-bar crash are different cases.

  1. Let one successful pass finish.Record elapsed time and progress. If the bar is moving and the game reaches the menu, do not force-close it just because another player's machine was faster.
  2. Compare two normal launches.Keep the game build, GPU driver and settings unchanged between them. Reinstalling the driver for each test changes the conditions.
  3. Check cache settings and free storage.For NVIDIA, consult the linked vendor cache guidance. Installing a new driver clears its cache; an undersized cache can evict entries. Check whether a cleanup tool is removing shader caches, without disabling security protections or adding blanket exclusions.
  4. Report persistent repetition.Include build, GPU/driver, storage, both launch times and whether compilation actually crashes. Do not assume clearing the cache on every start will make it persist.

We have not verified a universal Season 2 fix for repeated compilation. NVIDIA-specific cache behavior should not be presented as an AMD/Intel setting or proof that the game's own shader pipeline works the same way.

Use the safe repair order before cache surgery

  1. Verify game files.Steam → Library → WARDOGS → Properties → Installed Files → Verify integrity of game files.
  2. Update the stable GPU driver.Use the normal vendor release channel and restart after installation.
  3. Repair Elytra.Open the WARDOGS installation folder, run the supplied Elytra setup and choose Repair.
  4. Return CPU and GPU tuning to stock.Team17 has recommended disabling overclocking while diagnosing launch crashes.
  5. Test once after reboot.Do not change several unrelated settings before the next launch.

If shader compilation still crashes

Collect evidence before moving to more invasive changes:

  • Write down the exact percentage where compilation stops.
  • Save the WD-L code or Windows crash message if one appears.
  • Note GPU model, driver version and whether CPU/GPU tuning is enabled.
  • Check whether WARDOGS or Elytra was blocked by Windows Security, firewall or antivirus.
  • Use Team17's Report a Problem forum when the official repair sequence fails.

If the failure changed from a WD-L launcher code to a shader-stage crash, do not assume the original issue is solved; record both stages because the new symptom may point to a separate failure.

What not to do first

  • Do not delete random shader folders. A community cache path can be wrong for your driver or current build.
  • Do not download replacement DLL files. Use Steam verification and the bundled repair tool.
  • Do not disable Windows security features by default. Security trade-offs need an exact reason, not a generic shader symptom.
  • Do not roll back Windows or drivers blindly. Match any rollback to a current, documented compatibility issue.

Common questions

Should I clear the DirectX or NVIDIA shader cache?

Not as the first move. Team17's current response to a shader-compilation crash starts with file verification, and the broader crash guidance adds GPU driver and Elytra repair. Cache deletion is a community troubleshooting step, not the universal official first-line fix.

Why does it stop at 94% or another fixed percentage?

The percentage helps describe the failure but does not identify one universal bad file. Record it for support and follow the repair sequence before deleting folders.

Is a shader crash the same as WD-L020?

No. WD-L020 can occur before the game reaches shader compilation. Use the error-code page when a WD-L code is visible.

Sources and verification

Developer information and community observations are labelled separately. A player report is not a guarantee from the developer. Use the stated source-check dates; a later page edit does not recheck the underlying game data.

  1. Season 2 first-hand reports: compiling every startupPlayer reports establish the repeated-compilation symptom, not a universal cause or a verified fix.
  2. NVIDIA Control Panel: Shader Cache SizeVendor documentation explains cache reuse, driver-update cache invalidation and eviction when the configured cache is too small. This is general NVIDIA guidance, not a WARDOGS-specific diagnosis.
  3. Team17 Support: WARDOGS crashesPinned developer support thread for current launch crashes, known WD-L codes and the first-line repair sequence.
  4. Team17 reply: crash while compiling shadersCurrent-build shader-compilation report where Team17 Support first asks the player to verify the game installation.