Troubleshooting
Azeroth Survivors is not loading
Start with the message you see. A missing WebGPU feature, a busy creator host, and a local build that lacks client data are different problems with different fixes.
Browser path
Check WebGPU before changing anything else.
The creator page explicitly checks for WebGPU. A browser without it cannot render the game canvas, even when the page itself opens normally.
- Try a current Chrome, Edge, or Safari release.
- Update the browser and graphics drivers, then reload the creator page.
- Close other GPU-heavy tabs and try again if the canvas remains black.
- If WebGPU is still unavailable, use the creator's Windows option rather than a random mirror.
Busy host or local build
Separate availability from installation errors.
A working page can still be temporarily busy. The community rebuild has a different failure surface because it depends on toolchains and user-supplied client data.
- For a busy browser host, wait and check the creator Discord or current page notice.
- For a local build, confirm the requested client Data files exist before rebuilding.
- Read the repository's current Makefile and README instead of reusing an old command from a video.
- Record the browser, operating system, error text, and source URL before asking for help.
Match the symptom
Start with the failure you can actually see
A page that opens, a canvas that stays black, a busy host and a local build that stops during setup point to different next steps.
WebGPU warning
Browser or graphics support
Try a current browser and updated graphics stack, then check the creator page again.
Black canvas
Rendering path
Close other GPU-heavy tabs, reload, and note whether the page reports a WebGPU problem.
Busy host
Availability
Wait for the creator host or check its current notice and Discord before changing local settings.
Build stops
Toolchain or data
Read the failing repository step and confirm the required client Data files are present.
Useful support request
Collect enough detail for someone to reproduce it
A short, structured report is easier to answer than a screenshot with no context. Keep the original error text when possible.
- Copy the exact message and the URL or local command that produced it.
- Include your browser, operating system and whether you are using the creator page or local repository.
- Say whether the failure happens before the canvas, after entering a run, or during the build scripts.
- For a local build, include the failed make target and whether the client Data folder exists.
- Remove private paths or tokens before sharing logs publicly.
FAQ
Quick answers
Why does the page say my browser has no WebGPU?
The creator-hosted page requires WebGPU to render its canvas. Use a current supported browser and update your graphics stack; if the feature is unavailable on your device, use the creator's alternate route.
Should I use a browser flag to force WebGPU?
Only follow a current instruction from the creator or your browser documentation. Do not treat an old flag or an unofficial download as a guaranteed fix.
Should I enable an experimental browser flag?
Only follow a current instruction from the creator or your browser documentation. An old flag can change behavior without fixing the underlying GPU or compatibility problem.
How do I tell whether the problem is the host or my browser?
Check the creator page message first, try a current supported browser, and compare whether the page itself loads while the canvas fails. Record the result before switching to another route.