GUIDE 05 / TROUBLESHOOTING

Fix the next obstacle

Start with the message or symptom you can actually see. A graphics issue, a room mismatch and a missing save need different fixes.

REVIEWED OCTOBER 23, 2026 · INDEPENDENT COMPANION

“Starting graphics” does not finish

  1. Read the missing-feature or graphics message on the game host. Missing JSPI blocks startup; missing WebGPU can use the slower software renderer.
  2. Run the homepage check for local graphics and JSPI signals. The game host recommends a current Chrome or Edge and checks more features on its own page.
  3. If an adapter is available but the game still fails, record the exact error. For broken or flickering video, try Settings → Graphics → Video output → Safe mode on the host.
Review the startup sequence →

Unsupported is different from slow

Read the missing-feature list on the game page. Missing JSPI or required WebAssembly features blocks startup; the host recommends a current Chrome or Edge.

Missing WebGPU or an adapter can fall back to software graphics. That path may be much slower. Check your browser signals without treating them as a complete game test.

A broken or flickering picture

On the game host, open Settings → Graphics → Video output and try Safe mode (copy frames). The source describes this as a slower path and can also activate it after video errors.

For slow rendering, try a lower internal resolution. The host lists 640×512, 1280×1024 and 1920×1536. Save first: a resolution change reloads the game and ends an online session.

Slow after you switched tabs

Return to and focus the actual game tab. The host reports background throttling. Device resources and browser scheduling still affect performance; this companion has no measured frame-rate guarantee.

Follow the specific guide

If the host itself reports an error, keep its exact wording and the File name. Do not erase browser data as a first attempt; that can remove local saves.

SOURCE: File #1 interface + File #2 interface · Verification limits