ROB RUN Stuck on Compiling Shaders or Loading

Is it stuck or still compiling?

ROB RUN is the multiplayer crime sandbox from Kefir (Kefir Games), and our ROB RUN game overview covers the basics if you have not played yet. On loading, the honest answer is short. As of November 9, 2026 the Kefir support center has no article that uses the words compiling shaders. It does not say how long the first load should take or what the game does during that screen. What it does cover is a game that will not load or freezes, plus a list of error codes.

That means we cannot give you a number of minutes to wait, and we will not invent one. One sign is clear, though: if an error code appears, the game has hit a named failure, and the table further down tells you what Kefir suggests for it.

Our read: look at the servers before you look at your PC. In launch week Kefir posted on X twice about attacks. November 5 brought the first one, a large-scale DDoS attack that broke connections. November 7 brought the second: attacks running since the previous night, with lag and failed connections as the result. On November 9 the support center banner said the EU server had technical issues and that a fix was in progress. When a post like that is up, a new driver will not help. Our ROB RUN server status guide lists where Kefir posts these notices.

Fixes to try first

The official answer for a game that freezes or will not load is four checks, and the steps on this page follow the same order.

The connection goes first because nothing else matters if the game cannot get its startup data from Kefir. It is also the cheapest test: open a website and you have your answer in seconds.

The restart has to include Steam, not just the game. Steam itself shows up in the fixes for several codes in the table below, so a half restart often leaves the real problem running.

The driver update takes longer, so it comes after the two quick checks. Do it before you think about reinstalling.

If you only have time for one thing beyond a restart, our pick is the Steam file check, which is part of the official fix for several codes below.

Error codes and what they mean

Kefir keeps one support article for error codes. The table below cuts each entry down to a short label. The list may grow during Early Access, so treat it as accurate as of November 9, 2026.

Code	What it means	Fix, in short
E-0101 / E-0110	Startup data never arrived from the server	Test websites, then repair your connection
E-0102	Network or antivirus spoiled the download	HTTPS scan paused, proxy off, home network
E-0124	A game asset failed inside the client	Steam file check
E-0201	Mid-match disconnect from the server	Restart once your connection is back
E-0301 / E-0302	Your build is behind the live version	Fresh Steam start, then pull the update
E-0303 / E-0304	Local data broken or out of sync	Proxy off, verify, update; first wait 10-15 minutes
E-0401	Steam login check failed	Restart both with the right account online
E-0403 / E-0404	Epic Online Services sign-in problem	Reboot, antivirus exception, file check
E-0405	Steam silent, or a library quarantined	Steam running, quarantine cleared, files verified, library launch
E-0501 / E-0502	Anti-cheat missing, broken or blocked	Reboot, verify, antivirus off, Steam launch only
E-0904	Unknown internal fault	Restart; report to support if repeated

Our read on which code to suspect first: E-0101 and E-0102 sit between you and the servers, so check the outage posts and your own network before you change anything on the PC. Codes that name Steam, files or anti-cheat point at your own install, and the Steam file check is the next move. If your security app keeps a quarantine list, look at it before you reinstall.

If it still will not load

Sometimes the game does not hang at all; it closes to the desktop. That is a crash, and it has its own official fix. The first step is a reboot with every other program shut. Should the crashes come back, the case goes to support, so have the exact error text ready along with your hardware details and a few lines on what happened.

Anti-cheat errors (E-0501 and E-0502 in the table) usually come down to how you start the game. Our read: if you open ROB RUN from a desktop shortcut or another launcher, switch to the Steam library first, since the official fix asks for Steam launches only. Stick to the official steps rather than any workaround.

If you play over Remote Desktop or a cloud streaming service, a separate error, E-0601, can stop the game when it finds no keyboard and mouse. Kefir asks for a physical keyboard and mouse before launch. The platform guide linked in the next section covers this in more detail.

If none of this works, contact the Kefir support center. Include the error code, your PC specs and what you already tried.

When your PC is the problem

If your PC sits below the minimum spec on the Steam page, none of the four checks will make up the difference. We do not repeat the hardware list here; our ROB RUN PS5 and PC platform guide has the minimum and recommended tables.

One performance issue looks like a hardware limit but is not. The game loads and runs, but the frame rate falls apart the moment you move the mouse. The support center traces that to a gaming mouse set to a very high polling rate. The fix starts in the mouse’s own app, where you turn the rate down. Still stuttering after that? Switch off overlays next, then install a fresh GPU driver, and on 13th or 14th Gen Intel CPUs update the BIOS.