{"id":78589,"date":"2026-09-16T12:00:00","date_gmt":"2026-09-16T16:00:00","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=78589"},"modified":"2026-08-30T23:06:17","modified_gmt":"2026-08-31T03:06:17","slug":"fix-star-wars-zero-company-black-screen-78589","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/fix-star-wars-zero-company-black-screen-78589\/","title":{"rendered":"Fix STAR WARS Zero Company Black Screen After Splash Logo"},"content":{"rendered":"

The splash logo appears. The screen goes black. The music keeps playing \u2014 or it doesn\u2019t. 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<\/a> Zero Company<\/em> refuses to load past the opening logo on PC.<\/p>\n

Let\u2019s 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<\/a> 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 \u2014 a black screen that hangs indefinitely or eventually drops you to desktop. One counterargument: \u201cMy other games run fine. The install must be broken.\u201d<\/em> Fair point. But a genuinely broken install \u2014 missing core files, bad sectors on the drive \u2014 produces error messages, not a silent black screen. You would see \u201cfile not found\u201d popups, a crash reporter, or an immediate CTD. The black screen that appears after<\/em> 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.<\/p>\n

Why the Black Screen After the Logo Is a Shader Issue<\/h2>\n

STAR WARS Zero Company<\/em> compiles shaders every time you launch \u2014 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.<\/p>\n

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<\/a>.<\/p>\n

The Case Against a Corrupted Install<\/h3>\n

The strongest counterargument is that a file verification should catch any corruption. And it does \u2014 for missing or damaged game assets. But the shader cache is not part of the game\u2019s verified files. It lives in a separate folder (%LOCALAPPDATA%Star Wars Zero CompanySavedConfigWindows<\/code>codecodecodecodecodecode and also in %LOCALAPPDATA%NVIDIADXCache<\/code>codecodecodecodecodecode 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 \u201call files successfully validated,\u201d and still hit the black screen. That is why the standard \u201cverify files\u201d advice often fails here.<\/p>\n

Step-by-Step Fixes for the Black Screen<\/h2>\n

Clear the Shader Cache<\/h3>\n

Open Disk Cleanup. Click the Windows<\/a> Start button, type \u201cdisk cleanup,\u201d select your C drive. In the list, check \u201cDirectX Shader Cache.\u201d Click OK, delete the files. This removes the system-level cache.<\/p>\n

Next, open File Explorer. Go to %LOCALAPPDATA%NVIDIADXCache<\/code>codecodecodecodecodecode (or %LOCALAPPDATA%AMDGLCache<\/code>codecodecodecodecodecode for AMD). Delete everything inside. Do the same for %LOCALAPPDATA%NVIDIAGLCache<\/code>codecodecodecodecodecode. If you have an Intel<\/a> GPU, check %LOCALAPPDATA%IntelShaderCache<\/code>codecodecodecodecodecode.<\/p>\n

Restart your PC. Launch STAR WARS Zero Company<\/em>. The first launch will take longer \u2014 sometimes 3 to 5 minutes \u2014 because the game must rebuild all shaders. Do not alt-tab or click away. Let it finish.<\/p>\n

Force DirectX 12 via Launch Options<\/h3>\n

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.<\/p>\n

Steam users:<\/strong> Right-click the game in your library, select Properties. In the \u201cLaunch Options\u201d field, type -dx12<\/code>codecodecodecodecodecode. Close the window and launch.<\/p>\n

EA App users:<\/strong> Click Manage \u2192 View Properties. Under \u201cAdvanced Launch Options,\u201d type -dx12<\/code>codecodecodecodecodecode. Click Save. Launch the game.<\/p>\n

If the black screen persists, remove the flag and try -dx11<\/code>codecodecodecodecodecode instead. Some GPUs (older Nvidia cards, certain AMD RDNA2 cards) actually work better on DX11. The point is to test both.<\/p>\n

Disable In-Game Overlays<\/h3>\n

Overlays inject code into the rendering pipeline. That injection can corrupt the shader compilation process.<\/p>\n