- Sandustry white screen problems are often linked to browser rendering, shaders, or image-color handling.
- Chrome or Edge may be more reliable when Firefox stops at loading or reports
w is undefined. - Disable Shadows can improve underground performance and reduce severe rendering problems.
- Mobile browsers may load the interface while failing to render the playable world correctly.
- Console logs help separate browser errors from hardware, memory, or network issues.
Sandustry White Screen: Identify the Symptom
Sandustry white screen issues can appear in several forms. Some players reach the loading screen but never enter the world, while others see a black or blank game view with the hotbar and menus still working. Treating every blank screen as the same problem can waste time, so first match the symptom to the likely cause.
The most useful distinction is whether the interface appears. If the inventory, tabs, or hotbar are visible but the environment is missing, the game has probably loaded part of its interface while the renderer, lighting system, or GPU path is failing. If the game remains on “Launching” or “Loading starting,” the problem may occur earlier during asset loading or browser initialization.
| Symptom | Likely area | First action |
|---|---|---|
| Stuck on “Launching” | Browser startup, assets, memory | Reload once, then test another supported browser |
Loading screen with w is undefined | Firefox image or color-profile handling | Update Firefox, then try Chrome or Edge |
| Black world with visible menus | Renderer, shaders, mobile GPU | Disable shadows and test a desktop browser |
| White or blank canvas | GPU acceleration or WebGL path | Restart the browser and test hardware acceleration |
| Very low FPS underground | Lighting and shadow workload | Turn off Disable Shadows in Options |
Player reports also describe browser-specific behavior. Chrome has worked where Firefox failed, while some Chromebook, Android, and older laptop configurations reached only part of the game. That does not prove one browser is universally best, but it makes browser comparison an important diagnostic step.
Loading Failure
The game never reaches the playable world. Focus on browser compatibility, cached assets, extensions, and console errors.
Black World
Menus may respond while terrain remains invisible. Focus on shaders, lighting, GPU selection, and mobile browser limitations.
White Canvas
The game surface may fail to render at all. Focus on hardware acceleration, WebGL support, and browser restarts.
Before clearing site data or changing advanced settings, open Sandustry in a fresh tab, disable browser extensions for the site, and test Chrome or Edge. This preserves your local save while quickly identifying a browser-specific problem.
Step-by-Step Browser Troubleshooting
Follow these steps in order. The sequence begins with changes that are easy to reverse and ends with diagnostic actions that may affect local browser data. Do not clear storage until you understand how your current save is stored.
Reload Without Repeating the Launch Loop
Close extra Sandustry tabs and restart the browser. Open only one game tab, then wait for the loading process to finish. Repeatedly opening new tabs can increase memory pressure, especially on Chromebooks and older laptops.
Test Chrome or Edge
If Firefox remains on the loading screen or shows w is undefined, test the same page in Chrome or Edge. Reports indicate that the game has launched in Chrome when Firefox failed, although browser behavior can change after updates.
Use a Clean Session
Temporarily disable ad blockers, script controls, and privacy extensions for the Sandustry page. You can also test a private window, but remember that private sessions may not preserve local saves after closing.
Change Rendering Options
If you can reach the menu, open Options and enable Disable Shadows. This is particularly useful when the world becomes slow underground or when lighting shaders cause severe performance drops.
Capture the Console Error
On desktop Chrome or Edge, open Developer Tools with Ctrl+Shift+J or F12, reload the game, and copy the first meaningful error. A specific message such as Failed to load resource is more useful than general timing warnings.
| Test | What it checks | Keep the result |
|---|---|---|
| Chrome or Edge | Browser compatibility | Note whether the world renders |
| Firefox with no extensions | Firefox-specific behavior | Record any w is undefined message |
| Private window | Extension and cache interference | Do not use it as your only save session |
| Disable Shadows | Lighting and GPU workload | Compare underground FPS and visibility |
| Console reload | Startup and asset errors | Copy the first relevant error line |
A browser console may show warnings about forced reflow, non-passive wheel listeners, unsupported feature attributes, or closed message ports. These do not automatically explain a white screen. Prioritize errors that mention the game bundle, failed resources, undefined values, WebGL, canvas, or asset loading.
Do not clear cookies, IndexedDB, or site storage as a first response. Sandustry player feedback has highlighted the need for better save backup and export tools, so storage removal may erase local progress if no backup is available.
Graphics, Shaders, and Hardware Fixes
A blank game view can result from the difference between interface rendering and world rendering. Sandustry uses a visually demanding sand simulation, lighting effects, and underground environments. A system may handle the menu while struggling with the terrain renderer, shadows, or shader workload.
The first in-game adjustment is Disable Shadows. This setting has been recommended as a temporary performance fix for underground slowdowns. It may not solve every white screen, but it reduces one major rendering workload and is safe to test.
On laptops with both integrated and dedicated graphics, confirm that the browser is using the stronger GPU. Some players have reported that the browser selected integrated graphics by default, producing poor performance in demanding scenes. The exact instructions depend on your operating system and graphics driver, so use your system’s graphics settings rather than changing random browser flags.
| Hardware or setting | Possible effect | Recommended response |
|---|---|---|
| Integrated GPU | Lower underground performance | Assign the browser to the dedicated GPU if available |
| Limited system memory | Long loading or browser crashes | Close other tabs and applications |
| Mobile GPU | Partial interface with missing world | Test desktop hardware when possible |
| Shadows enabled | Heavy underground rendering load | Turn on Disable Shadows |
| Older browser build | Asset or WebGL incompatibility | Update the browser and restart it |
If the world is black but water or dug-out dark areas appear correctly, the problem may involve lighting or shader behavior rather than a total game failure. Lowering the rendering burden is more appropriate than repeatedly refreshing the page.
If Sandustry opens but becomes nearly unplayable underground, enable Disable Shadows before changing system settings. This is a reversible adjustment and directly targets a reported source of frame-rate loss.
Desktop Browser
Usually the strongest troubleshooting environment because it provides console access, better input support, and more graphics options.
Chromebook
Can work, but long loading times, memory limits, and school-device restrictions may interfere with startup.
Mobile Browser
May display menus while failing to render the world correctly. Treat mobile support as less consistent than desktop play.
Firefox Errors and Launch Failures
The clearest browser-specific error in the available Sandustry troubleshooting record is w is undefined. It appeared during Firefox loading and was connected to a blueprint image whose embedded color profile was interpreted differently by Firefox. The developer reported that stripping the profile or resaving the image corrected that underlying asset issue.
For players, the practical response is simple: update the game page, restart Firefox, and test another browser if the error continues. Do not attempt to edit the game bundle or replace local files. This type of failure generally requires an application-side fix rather than a player-side code change.
Another reported startup message is Failed to load resource: net::ERR_FAILED bundle.js. This can indicate a failed asset request, blocked resource, interrupted connection, extension interference, or a temporary browser problem. Capture the full console context before assuming that the error identifies the exact cause.
| Console message | What it may indicate | Player response |
|---|---|---|
w is undefined | Firefox asset or color interpretation issue | Try Chrome or Edge and report the full error |
net::ERR_FAILED bundle.js | Failed script or resource request | Reload, disable extensions, check the page again |
| Forced reflow warning | Performance warning | Usually not the primary white-screen cause |
| Unrecognized feature warning | Browser attribute mismatch | Usually secondary unless loading also fails |
| Repeated promise callbacks | Startup task is retrying or failing | Copy nearby errors and restart the session |
When reporting a failure, include the browser name and version, operating system, device type, whether the interface appears, and the first meaningful console error. This is more actionable than reporting only “the game is broken.”
For reference, use the Sandustry itch.io comments and troubleshooting discussion when comparing known browser, loading, mobile, and performance reports. The page includes developer replies about Firefox errors, shadows, Chromebook loading, and partial mobile rendering.
Include your browser, operating system, device, whether Chrome or Firefox was used, and the exact first console error. Mention whether menus, inventory, water, or underground areas remain visible.
Recovery Checklist and FAQ
Use this checklist after a browser update, device change, or repeated loading failure. It focuses on preserving progress while narrowing down the cause.
Troubleshooting Checklist:
- Close duplicate Sandustry tabs and restart the browser
- Test Chrome or Edge if Firefox remains stuck
- Disable browser extensions for the Sandustry page
- Enable Disable Shadows if the world is slow or dark
- Record the first meaningful console error before clearing storage
| Situation | Safer next move | Avoid first |
|---|---|---|
| Stuck on Launching | Test a clean browser session | Repeatedly opening many tabs |
Firefox shows w is undefined | Try Chrome or Edge and report the error | Editing game files |
| Menus work but world is black | Disable shadows and test desktop hardware | Assuming the save is corrupted |
| Game crashes after loading | Close other applications and capture logs | Clearing local storage immediately |
Q: How do I fix the Sandustry white screen?
Restart the browser, test Chrome or Edge, disable extensions for the page, and enable Disable Shadows if you can reach the Options menu. If the issue continues, capture the first console error.
Q: Why does Sandustry load in Chrome but not Firefox?
A reported Firefox issue involved an image color profile being interpreted differently during loading, producing a `w is undefined` error. Use an updated browser and test Chrome or Edge while the issue is being resolved.
Q: Why is the screen black on my phone?
Mobile browsers may load the interface while failing to render the world correctly. Try a current desktop browser when possible, and report your phone model, operating system, browser, and visible game elements.
Q: Can I clear browser data to fix the loading screen?
Clearing site data can remove cached failures, but it may also affect local save data. Treat it as a later troubleshooting step and consider whether your progress has a backup first.
The most reliable troubleshooting path is to identify the exact symptom, compare browsers, reduce rendering load, and preserve diagnostic information. A white, black, or stalled screen does not necessarily mean the save is lost. In many cases, the difference between a working and broken session is the browser renderer, graphics path, or a single asset-loading error.
Keep one stable desktop browser session for regular play, use a second browser for diagnosis, and save console details before making storage changes. This makes future Sandustry launch problems easier to isolate.