Sandustry Hotfix 0.5.3

Sandustry’s first Early Access patch is v0.5.3, posted on the Steam news hub on August 14, 2026 — one day after launch. Lantto Games titled it a hotfix for logging, memory, and clearer objectives. It is not a balance pass and not the larger crash patch the developer said is still in progress. This page is the ledger for that note so Launch Week can stay the storefront snapshot and Guides do not invent new recipes from a diagnostics drop.

What v0.5.3 actually changed

The Steam changelog is short. Treat every line as a stability or clarity change, not a factory rewrite.

Better logging

The build writes a main.log so crash reports can include a file instead of a screenshot of a frozen window. Official paths:

OS	Log file
Windows	C:\Users\<you>\AppData\Roaming\sandustry\logs\main.log
macOS	/Users/<you>/Library/Logs/sandustry/main.log
Linux	/home/<you>/.config/sandustry/logs/main.log

Attach that file when you post on Steam discussions or Discord. The Crashes and Performance guide walks through how to find it and what else to send.

Instructional videos unmount

Tutorial clips now unmount when you leave them. The note says this avoids decoder exhaustion — a failure mode where too many video decoders stay alive and the client dies. If your first-hour crash happened while skipping or replaying tutorial movies, update before you blame the shaker line.

Steam-rain clouds use less memory

When Steam condenses into rain, the cloud sprites are cheaper. Large Water Management loops that boil lakes all session were a known memory hog. This does not change rain timing (~30 seconds in community tests); it trims overhead so a wet factory is less likely to OOM.

Factory-tier objectives are readable

When a factory tier (Factory Level) is blocked, the UI now shows why. Special objectives are visually louder. Translations for the new strings were still pending in the 0.5.3 note — English players see the reason first; other locales may still show a stub until a follow-up. That is the patch that makes Research Tree gates less mysterious, not a new gold cost table.

--sandustry-no-overlay-gpu-flags

Steam → right-click Sandustry → Properties → Launch Options. Set:

--sandustry-no-overlay-gpu-flags

Lantto wrote that this might prevent some crashes. The trade-off: the Steam overlay will likely stop working. Achievements still work. Try this after you have a log, not as the first step. Full steps live on Crashes and Performance.

Official Early Access launch trailer — the build this hotfix landed on

What this patch did not do

• No shaker yield change, no research cost change, no new biome.
• No Xbox console port and no Cloud Gaming — those Launch Week facts still hold.
• No promise that every launch-week crash is gone. The note says work continues on a larger patch for the crash pile.
• Demo Hotfix 8 (2025-02-21) is still the last detailed demo list on Demo Patches. Do not mix demo flower-algorithm notes into this EA file.

How to play after 0.5.3

Factory advice on this wiki still matches the August 13 launch loop: diagonal Shakers, Collectors on solid floors, slag burn into the Kinetic Slag Press, then Fluxite. Mid-game energy is documented on How to Get Energy because that chain was already in the EA tree — the hotfix only makes tier gates easier to read.

If a factory tier still looks locked after the update, read the new objective text before you grind another gold chest. The blocker is often a special objective, not a missing 500 gold.

Where to send reports

Lantto asked for Steam reviews and for logs. Useful bundle:

1. main.log from the table above.
2. OS, GPU, and whether you use the overlay flag.
3. Whether the crash hit during tutorial video, steam rain, or a large belt session.

Official homes: Steam news for app 2764460, sandustry.com, Discord. This wiki is unofficial and will not invent a 0.5.4 until Steam posts it.

Related

• Crashes and Performance — Log paths, overlay flag, and what to try before a reinstall.
• Launch Week — Price, Game Pass caveats, discount through 2026-08-27.
• EA Launch — Opening-day snapshot.
• EA Roadmap — Year-of-EA themes, not this hotfix.

Update the client, grab a log if it still dies, then go back to the lake factory. The pixels did not change; the diagnostics did.