Check your browser.
Then start playing.

In Chrome, open chrome://settings/system. Turn on Use graphics acceleration when available, then choose Relaunch. In Edge, open Settings → System and performance and enable the equivalent setting, then restart Edge. Reopen this page and run the checks again.

This fixes one cause of unavailable WebGPU, not every loading freeze. If it still stops, collect the first red console error and check chrome://gpu or edge://gpu. Do not disable antivirus or use unsafe GPU flags.

Free disk space stores the download; RAM and GPU memory run the game. A loading timer alone does not prove that memory is exhausted. An error such as memory access out of bounds can also be an engine bug, so buying more RAM is not a confirmed fix.

If loading stops at 24% or another percentage, note the last loading message, check that all 14 archives finished installing, and collect the first red browser-console error and any failed Network request. Try the lower-memory option above. Include your actual RAM, GPU, browser version, and Story/Sandbox choice in the report.

Close the game tab and try the lower-memory link above. Compare Story and Sandbox modes. If the world stays black, open browser developer tools (F12 on Windows; ⌥⌘I on Mac), capture the first WebGPU / shader errors, and attach them with these diagnostics to issue #2. A working menu does not prove that world shaders or all game files loaded.

Close every game tab, stop the local server with Ctrl+C if you use one, and launch again. Update the browser and graphics driver (macOS updates supply Mac drivers). Check chrome://gpu or edge://gpu for hardware acceleration and Problems Detected. Close GPU-heavy apps. Post the first error and diagnostics to issue #1.