Azeroth Survivors Black Screen or Stuck Loading
A black canvas in Azeroth Survivors is often the first load still pulling the client, not a dead page. If the console names HTTP 429, you are on the busy path. If it names a lost GPU device, the boot script has already stored a report under rogue.gpuCrash.
Work through it in order
- Confirm the server is up. A 429 looks like a failed start and is not a graphics bug.
- Give the first visit about a minute. An older public test saw roughly 140MB and about 1150 requests before the first frame. Source: community, not re-measured here for 0.110.0.
- Open the console. “This browser has no WebGPU” belongs on the WebGPU page. “HTTP 429” belongs on the busy page.
- If the device was lost, read localStorage key
rogue.gpuCrashon the official origin. The report names the pipeline the GPU process had not finished. Android phones in particular have crashed shader compilers; the boot script already skips the warm pass on Android. - If the browser build will not finish, use the official Windows archive from the download page.
How long should the first load take?
One public measurement, on an older build, saw about 140MB, about 1150 requests, and around a minute to the first frame. Treat a silent minute as loading. Treat several minutes with a console error as a failure. We have not re-timed 0.110.0.
Where is the crash log?
On the official origin, DevTools, Application, Local Storage, key rogue.gpuCrash. The boot script writes a pipeline report there and prints it on the next load. Read it on wow.aethus.pl, not on this desk.