What has actually been reported?
A reply in the launch-week pinned Steam discussion described shader preparation stuck at 50% on an RTX 4090 and an Intel i9. The player reported trying a reinstall, reboot, NVIDIA shader-cache clearing and Cloudflare WARP without success. Those are failed attempts described by one player, not a sequence we recommend repeating or a benchmark of all similar PCs.
Another reply noted that some players could enter while others could not, raising the possibility of a server gate. That explanation remains unverified. A percentage on a loading screen does not, by itself, identify the failing subsystem. We have no developer statement diagnosing this exact 50% case, no reproducible test and no supported cache location to provide as a repair target.
Separate a shader delay from a connection hang
Compare the precise screen text with the status-information issue before using advice for a different symptom. The research links “Waiting for status information” to players returning to the map during instability; the shader report describes a 50% preparation screen. They may overlap in timing, but the source set does not prove they share a cause or a remedy.
The official developer post acknowledged DDoS-related connection errors and lag during launch week. Check it for a newer dated update before making repeated local changes. It is a historical incident report, not confirmation that every shader stall is server-side. Equally, a powerful graphics card does not establish that the issue must be server-side. Keep the symptom, your hardware and the suspected explanation as separate pieces of information.
A conservative information checklist
For a useful report, record the game’s visible message, the percentage, how long it has remained there, the date and your system specifications. Note whether the screen ever finishes and whether the game then reaches a map or returns an error. These are editorial suggestions for collecting evidence, not an official support form or a claim about the game’s internal diagnostic tools.
Steam lists Windows 10 or later, 64-bit, DirectX 11, 20 GB storage and a broadband connection. The minimum memory is 12 GB and the recommended amount is 16 GB. Checking those requirements is different from proving that insufficient hardware caused the stall. We have not measured shader compilation duration, so there is no sourced maximum waiting time after which this guide can declare the process broken.
How to use this launch-week evidence
The research snapshot for this guide was compiled on November 9, 2026, after Early Access began on November 4. Official announcements establish what Kefir has said; a forum reply establishes what one player reported. A symptom appearing in both places does not prove that every affected machine has the same cause. We keep the two kinds of evidence separate so you can decide what the next check should be.
No real-time server probe or in-game reproduction runs on this website. An old incident is not proof of an outage right now, and a reply saying that one person got back in is not proof that all regions recovered. Use the linked official discussion and community channels for newer announcements. If you report your own case, include the time, region, server identifier and exact message rather than treating this dated summary as a live status indicator.
Avoid destructive or paid “fixes” without evidence
The player’s failed cache-clearing attempt does not establish a universal cache repair. We do not tell you to delete directories, alter registry entries or install a network booster for this problem. No third-party executable, purchase or account login is offered here. The task research does not establish those actions as an effective or necessary response.
Generic suggestions such as checking Steam file integrity or updating graphics drivers were identified as general client troubleshooting rather than Kefir-confirmed fixes. They should not be advertised as a guaranteed 50% solution. If a later official post provides an exact repair, its date and applicable symptoms should replace this uncertainty. Until then, the accurate answer is that this specific hang was unresolved in the source material, with official community links available for newer evidence.