The splash logo appears. The screen goes black. The music keeps playing — or it doesn’t. You wait. Nothing happens. This is not a random crash. It is a shader compilation failure, and it is the single most common reason STAR WARS Zero Company refuses to load past the opening logo on PC.
Let’s be direct: the black screen after the logo is almost never a hardware problem. Your GPU is not dying. Your PSU is not underspecced. The issue lives in how the game builds and stores its shader cache. A corrupted cache, a missing DirectX runtime, or a conflict with an overlay will each produce the exact same symptom — a black screen that hangs indefinitely or eventually drops you to desktop. One counterargument: “My other games run fine. The install must be broken.” Fair point. But a genuinely broken install — missing core files, bad sectors on the drive — produces error messages, not a silent black screen. You would see “file not found” popups, a crash reporter, or an immediate CTD. The black screen that appears after the logo means the engine loaded the executable, initialized the renderer, and then stalled during shader compilation. That is a cache or runtime issue, not a corrupt download.
Why the Black Screen After the Logo Is a Shader Issue
STAR WARS Zero Company compiles shaders every time you launch — unless it finds a valid precompiled cache. If that cache is corrupt, the engine enters an infinite loop or silently fails. The result: black screen. The game is not frozen. It is stuck trying to build a shader it cannot complete.
Three things corrupt the shader cache most often: an incomplete driver update, an overlay that injects into the rendering pipeline (Discord, Nvidia app, Steam overlay), or a sudden power loss during a previous shader compile. The fix is to delete the cache and force the game to rebuild it from scratch.
The Case Against a Corrupted Install
The strongest counterargument is that a file verification should catch any corruption. And it does — for missing or damaged game assets. But the shader cache is not part of the game’s verified files. It lives in a separate folder (%LOCALAPPDATA%Star Wars Zero CompanySavedConfigWindowscodecodecodecodecodecode and also in %LOCALAPPDATA%NVIDIADXCachecodecodecodecodecodecode or the AMD equivalent). Verifying game files on Steam or repairing on EA App will not touch the shader cache. You can run the verification, have it return “all files successfully validated,” and still hit the black screen. That is why the standard “verify files” advice often fails here.
Step-by-Step Fixes for the Black Screen
Clear the Shader Cache
Open Disk Cleanup. Click the Windows Start button, type “disk cleanup,” select your C drive. In the list, check “DirectX Shader Cache.” Click OK, delete the files. This removes the system-level cache.
Next, open File Explorer. Go to %LOCALAPPDATA%NVIDIADXCachecodecodecodecodecodecode (or %LOCALAPPDATA%AMDGLCachecodecodecodecodecodecode for AMD). Delete everything inside. Do the same for %LOCALAPPDATA%NVIDIAGLCachecodecodecodecodecodecode. If you have an Intel GPU, check %LOCALAPPDATA%IntelShaderCachecodecodecodecodecodecode.
Restart your PC. Launch STAR WARS Zero Company. The first launch will take longer — sometimes 3 to 5 minutes — because the game must rebuild all shaders. Do not alt-tab or click away. Let it finish.
Force DirectX 12 via Launch Options
The game defaults to DX11 on some systems, and DX11 can trigger the black screen on certain GPU/driver combinations. Forcing DX12 often bypasses the stall.
Steam users: Right-click the game in your library, select Properties. In the “Launch Options” field, type -dx12codecodecodecodecodecode. Close the window and launch.
EA App users: Click Manage → View Properties. Under “Advanced Launch Options,” type -dx12codecodecodecodecodecode. Click Save. Launch the game.
If the black screen persists, remove the flag and try -dx11codecodecodecodecodecode instead. Some GPUs (older Nvidia cards, certain AMD RDNA2 cards) actually work better on DX11. The point is to test both.
Disable In-Game Overlays
Overlays inject code into the rendering pipeline. That injection can corrupt the shader compilation process.
- Steam overlay: Right-click the game → Properties → General → uncheck “Enable the Steam Overlay while in-game.”
- EA App overlay: Click the three horizontal lines → Settings → Application → toggle “In-Game Overlay” off.
- Discord overlay: User Settings → Game Overlay → toggle off “Enable in-game overlay.”
- Nvidia overlay: Open Nvidia app → Settings → toggle “In-Game Overlay” off.
- Xbox Game Bar: Press Windows + G → Settings → uncheck “Remember this is a game.”
Close all overlay apps entirely. Do not just disable the overlay — close the application from the system tray or Task Manager.
Update GPU Drivers with a Clean Install
A dirty driver update — one installed over an older version without a clean wipe — leaves behind stale cache entries. Perform a clean installation.
Nvidia: Go to the Nvidia website, select your GPU and OS. Download the latest GeForce Game Ready Driver (version 616.56 as of this writing). Run the installer, choose “Custom (Advanced),” check “Perform a clean installation,” then proceed. Restart.
AMD: Download the latest Adrenalin driver from AMD’s site. Run the installer, select “Factory Reset” when prompted. Restart.
After the restart, clear the shader cache again (as in the first step) and launch the game.
Adjust In-Game Config File
If you can reach the game’s config file, you can force settings that bypass the black screen without needing to get into the menu.
Navigate to %LOCALAPPDATA%Star Wars Zero CompanySavedConfigWindowscodecodecodecodecodecode. Open GameUserSettings.inicodecodecodecodecodecode in Notepad.
Find the line bNANiteEnabled=Truecodecodecodecodecodecode. Change it to Falsecodecodecodecodecodecode. This disables Nanite, which can cause shader compilation hangs on some GPUs.
Also find FrameGenerationMode=codecodecodecodecodecode. Set it to 0codecodecodecodecodecode (off). Find FrameRateLimit=codecodecodecodecodecode. Set it to 60.000000codecodecodecodecodecode. Save the file. Right-click it → Properties → check “Read-only” → Apply. This prevents the game from overwriting your changes.
Launch the game. If it works, you can later uncheck Read-only and adjust settings in-game.
Increase Virtual Memory
Low paging file size can cause shader compilation to fail silently. Set a manual size.
Open Control Panel → System → Advanced system settings → Performance Settings → Advanced → Virtual Memory → Change. Uncheck “Automatically manage paging file size.” Select your C drive. Choose “Custom size.” Set Initial size to 12288 MB (12 GB) and Maximum size to 24576 MB (24 GB). Click Set, OK, restart.
Rename the Config Folder
If nothing else works, rename the entire config folder. This forces the game to create a fresh config with default settings.
Go to %LOCALAPPDATA%Star Wars Zero CompanySavedConfigcodecodecodecodecodecode. Rename the Windowscodecodecodecodecodecode folder to Windows_oldcodecodecodecodecodecode. Launch the game. It will create a new Windowscodecodecodecodecodecode folder. The black screen may be gone — but you lose all your graphics settings.
When the Usual Fixes Fail: Advanced Troubleshooting
A small number of users report that the black screen persists even after all the above steps. In those cases, the issue is often an unstable CPU or memory overclock. The game’s shader compiler is sensitive to marginal instability that other games tolerate.
Download Intel Extreme Tuning Utility (XTU) if you have an Intel CPU. Open it. Under “Performance Core Ratio,” reduce the value by one or two multipliers (e.g., from 55x to 53x). Apply. Restart. Launch the game. If the black screen disappears, your overclock was the culprit. AMD users can try similar undervolting or clock reduction in Ryzen Master.
This is not a permanent fix — you can restore your overclock after the first successful launch. But the shader compilation pass is the most demanding phase for CPU stability. Once the cache is built, the game runs fine even with the overclock re-enabled.
One edge case: users with multiple monitors at different refresh rates sometimes hit the black screen because the game tries to initialize on a display that is not the primary. Disconnect all but one monitor, set that monitor to 60 Hz, and try launching. If it works, you can reconnect the other monitors after the shader compile finishes.
The black screen after the splash logo is frustrating, but it is solvable. Start with the shader cache. Work through the list. One of these steps will get you past it.
