Star Wars Zero Company is a demanding title. Shader compilation is its Achilles’ heel. When the cache corrupts, you get a crash reporter, a frozen loading screen, or a GPU crash dump. The fastest, most reliable fix is to clear that cache. Not verifying files. Not updating drivers. Not reinstalling the game. Clear the cache first. This article explains why and exactly how.
Why Shader Cache Corruption Is the Prime Suspect
Shader compilation is the process where your GPU translates game code into instructions it can run. Modern games like Star Wars Zero Company compile thousands of shaders the first time you launch after a driver update, game patch, or hardware change. Those compiled shaders are stored in a cache. On subsequent launches, the game loads the cached versions instead of recompiling.
Here’s the problem: that cache can corrupt. A power loss during compilation. A driver update that half-clears old shaders. A game patch that changes shader source code but leaves old cache entries. Any of these breaks the cache. The game tries to load a corrupted shader, the GPU throws a fatal error, and you get the crash reporter.
The source material (troubleshooting guides for Star Wars Zero Company) lists clearing shader cache as step four, after restarting and updating drivers. That’s too conservative. In practice, if your game crashes during shader compilation (the “compiling shaders” screen at launch is where most crashes happen), the cache is almost certainly the culprit. Skipping to that step first saves time.
The Specific Mechanics
On Windows, shader cache is managed by the GPU driver and by DirectX itself. For Nvidia GPUs, the driver cache lives in %LocalAppData%NVIDIAGLCachecodecodecodecodecodecode. AMD stores its cache in %LocalAppData%AMDGLCachecodecodecodecodecodecode. Intel’s is tucked in %LocalAppData%IntelShaderCachecodecodecodecodecodecode. But there’s a second layer: Windows Disk Cleanup can clear what’s called “DirectX Shader Cache.” That’s the system-level cache, separate from the driver cache.
For Star Wars Zero Company, the game also stores compiled shaders in its own installation folder. Check the game directory — look for a folder named ShaderCachecodecodecodecodecodecode or shaderscodecodecodecodecodecode. That’s where the game’s own compiled data lives. Deleting that folder forces the game to rebuild everything from scratch.
Here’s the practitioner-level nuance most guides miss: the system-level cache (cleared via Disk Cleanup) and the driver-level cache (cleared by deleting the GPU folders) are not redundant. You need to clear both for a truly clean slate. If you only clear one, the other may still hold corrupted data that the game loads first.
How to Clear the Shader Cache for Star Wars Zero Company
Step-by-step, authoritative, no fluff.
Method 1: Windows Disk Cleanup (Quick)
- Press
Win + Rcodecodecodecodecodecode, typecleanmgrcodecodecodecodecodecode, press Enter. - Select the drive where Windows is installed (usually C:).
- Scroll down and check “DirectX Shader Cache.”
- Click OK, then “Delete Files.”
- Restart your PC.
This clears the system-managed cache. It’s safe and fast. But it does not touch the game-specific or driver-specific caches.
Method 2: Manual GPU Cache Deletion (Thorough)
- Nvidia: Open File Explorer, paste
%LocalAppData%NVIDIAGLCachecodecodecodecodecodecode into the address bar, delete everything inside. - AMD: Paste
%LocalAppData%AMDGLCachecodecodecodecodecodecode, delete contents. - Intel: Paste
%LocalAppData%IntelShaderCachecodecodecodecodecodecode, delete contents.
These folders regenerate automatically. Deleting them does not hurt anything.
Method 3: Game-Specific Cache Folder
Navigate to your Star Wars Zero Company installation folder (default on Steam: steamappscommonStar Wars Zero Companycodecodecodecodecodecode). Look for any subfolder named ShaderCachecodecodecodecodecodecode, shaderscodecodecodecodecodecode, or CompiledShaderscodecodecodecodecodecode. Delete it. If you’re unsure, search the entire game folder for .cachecodecodecodecodecodecode or .shadercodecodecodecodecodecode files — those are compiled shaders.
After all three methods, restart your PC and launch the game. The first launch will take longer (expect 5–15 minutes of shader compilation). That’s normal. Each subsequent launch will be faster as new caches are built.
The Counterargument – Dismantled
Some players argue that clearing the shader cache is a drag. “I don’t want to wait 15 minutes for shaders to compile every time I update a driver,” they say. “Better to wait for a game patch that fixes the corruption.”
That reasoning is flawed. Waiting for a patch assumes the corruption is a bug that the developer will fix. In many cases, the corruption is environmental — a driver conflict, a power event, or a mismatched game-dll version. The patch, if it comes, won’t fix your personal cache. It might even make things worse by changing shader source code while leaving your old cache intact. The 15-minute wait is a one-time cost. The alternative is crashing repeatedly until you give up. Clearing the cache is the only way to guarantee a clean base.
Additional Verification Steps (Use These Only If Clearing Cache Fails)
If you’ve cleared all caches and the game still crashes at shader compilation, move down the list:
- Update GPU drivers: Nvidia, AMD, Intel all ship shader compiler fixes in their Game Ready drivers.
- Disable overlays: Discord, GeForce Experience, Xbox Game Bar — any overlay can interfere with shader compilation.
- Run in compatibility mode, DX11: Star Wars Zero Company may handle shaders better under DX11 than DX12. Add
-dx11codecodecodecodecodecode in Steam launch options. - Verify game files: Corrupted base game files (not the cache) can also cause compilation failures. Steam can repair them.
These are backup steps. For shader compilation crashes specifically, they are far less effective than clearing the cache.
FAQ
Does clearing shader cache delete saved game data?
No. Saved games, settings, and progress are stored separately in DocumentsMy GamesStar Wars Zero Companycodecodecodecodecodecode or the Steam Cloud. Cache deletion only removes compiled shader data.
Will I lose performance after clearing the cache?
Temporarily, yes. On the first launch, the game runs slower while recompiling. Once the new cache is built, performance returns to normal — often better, because corrupted entries that caused stuttering are gone.
How often should I clear the shader cache?
Only when you encounter compilation crashes, or after a major driver or game update. Clearing it proactively is unnecessary but harmless.
Is there a difference between clearing cache via Disk Cleanup vs manually?
Yes. Disk Cleanup clears only the system-level DirectX cache. Manual deletion clears the driver-level cache. For stubborn crashes, do both.
Can a SSD speed up shader compilation?
Yes. If Star Wars Zero Company is installed on a slow HDD, shader compilation can take twice as long. Moving the game to an SSD reduces the first-launch wait.
What This Means for Future Launches
Shader compilation is becoming a bigger problem as games get more complex. Star Wars Zero Company is not unique. The same fix works for many Unreal Engine 5 titles. But here’s a nuance most troubleshooting guides ignore: the CPU architecture of your processor matters. AMD Ryzen chips and Intel Core chips compile shaders at different speeds and with different error profiles. Some crash patterns that seem like cache corruption are actually CPU driver or microcode issues. That said, clearing the cache remains the first, cheapest, most effective step — and it works for the vast majority of cases. When it doesn’t, the problem is likely elsewhere, and you’ve already ruled out the most common cause.
