ROB RUN stuck on compiling shaders or an infinite loading screen
First-launch shader work, the cache-clearing fix, and how to tell a slow PC from a broken server.
The first launch compiles shaders and can take several minutes. If it never finishes, close the game, clear the DirectX shader cache, verify the game files and update your driver. If the loading screen hangs on location travel rather than startup, it is the server-status problem instead.
Two different screens get called “loading” in ROB RUN, and they have different causes. Startup shader compilation is your PC. Location travel is the server. Fixing the wrong one wastes an evening.
Which screen are you on?
| Screen | When it appears | Likely cause | Where to go |
|---|---|---|---|
| Compiling shaders | At startup, especially the first launch after install or a driver update | Your PC building a shader cache | This page |
| Waiting for status information | When travelling between locations | Server load or connection | Server status |
| Black screen then crash | At startup | Driver, anti-cheat, corrupted files | This page, then verify files |
The first launch is allowed to be slow
Unreal-based games compile shaders on first run and after driver changes. Several minutes of a progress bar is normal on the minimum spec — the published floor is a GTX 1050 Ti with 12 GB of RAM. A machine at the minimum will be slow here, not broken.
Let it finish once. Closing the game mid-compile is how you end up doing it again, and again.
If it never finishes
- Close the game completely End the process, not just the window.
- Clear the DirectX shader cache Windows search → Disk Cleanup → select your system drive → tick “DirectX Shader Cache” → OK. This is the fix players report most often.
- Verify the game files Steam → Properties → Installed Files → Verify integrity of game files.
- Update the graphics driver A clean driver install is better than an update over an old one if you have crashed repeatedly.
- Check free space The game needs 20 GB, and shader compilation writes to disk. Less than a few GB free is a real cause of stalls.
- Try once more with antivirus exceptions Add the game folder and Easy Anti-Cheat to your antivirus exclusions. Real-time scanning during shader writes is a known slowdown.
Is your PC the problem?
- 12 GB of RAM is the published minimum. On 8 GB, Windows plus the game will page to disk and every load becomes a minute.
- A hard drive instead of an SSD roughly doubles load times in open-world games. This one is worth fixing.
- A GPU below a GTX 1050 Ti is outside the supported floor. Shader compilation and texture streaming both suffer first.
- Laptop power saving can throttle the GPU during a long compile. Plug in and set the performance profile.
After it loads
If the game loads but stutters, the problem is different. See performance and FPS. If it loads and then drops you back to the map, that is the server-status problem, not a shader problem.
FAQ
How long should ROB RUN take to compile shaders?
Several minutes on first launch is normal, especially at the minimum spec. If it runs far longer with no progress, clear the DirectX shader cache and verify files.
Why is ROB RUN stuck on the loading screen?
If it happens when travelling between locations, it is the server-status issue. If it happens at startup, it is shader compilation or corrupted files.
Does clearing the shader cache help?
It is the most commonly reported fix for a compile that never finishes. Windows Disk Cleanup has a DirectX Shader Cache option.
“Waiting for status information” in ROB RUN: what it means and how to fix it
The loading screen that hangs for a minute and dumps you back on the map — causes, fixes, and the error code table.
ROB RUN performance: settings that actually raise FPS
Where the frame time goes in a city full of players, and the settings worth changing first.
ROB RUN system requirements: the exact PC specs
Minimum and recommended specs as published by Kefir, plus what they actually mean for a 5,000-player sandbox.