Sandustry Performance and Save Safety – Diagnose Without Risk
Troubleshoot Sandustry crashes, lag, and save concerns with reversible checks, official reporting context, and a clean evidence template.
Published 2026-08-21 · Updated 2026-08-21 · Early Access guidance
Start with the support boundary
Performance is hardware-, driver-, operating-system-, save-, and build-specific. Steam currently lists official requirements and the community hub includes pinned topics for crash/FPS fixes, bug reporting, and finding save files. Follow those current official posts before experimenting with community workarounds. This page does not claim a universal FPS gain or publish an unverified save path. Its purpose is to help you collect a clean comparison and avoid destructive troubleshooting.
Capture a baseline
Record game build, platform, operating system, CPU, GPU, memory, display resolution, graphics settings, mod status, and whether the issue occurs in a new or existing save. Note the exact location and factory state. Measure the same scene for several minutes without changing anything. A large active pixel simulation may behave differently from an empty area, so include approximate material activity. Avoid installing tools or deleting data before you have a baseline.
Apply reversible checks
Restart the game and system, close unrelated heavy applications, verify that storage has free space, and compare window/display settings one change at a time. If Steam's official support post recommends file verification or a specific launch option, follow its current wording. Disable mods only after recording the list and ensuring the save can be opened safely without them. Do not download unknown executables, replace game files manually, or edit a sole save copy.
Protect saves
Use the official pinned save-location guidance for the current platform. Exit the game fully before copying anything. Copy the relevant save data to a separate dated folder, then verify the copy exists and has a plausible size. Never test destructive changes on the only copy. Cloud synchronization is useful but is not a substitute for a local versioned backup because an unwanted state can synchronize. Restoration steps vary, so consult current official support before overwriting live data.
Isolate factory load
Compare the affected save in a quiet region and near the busiest factory. Temporarily stop inputs through normal in-game controls rather than deleting structures, then observe whether stability changes. If it does, narrow by material activity, fluids, temperature reactions, logistics, or a particular module. That is a diagnostic clue, not proof of an engine defect. Preserve a minimal reproduction save if the official reporting channel accepts one.
Write a useful report
Provide a short title, current build, platform, hardware, mod status, reproduction steps, expected result, actual result, frequency, and what reversible checks changed. Attach logs or saves only through an official channel and review them for personal data. State whether the issue survives restart and occurs in a new save. Avoid claiming a universal bug from one machine. A precise report is more actionable and makes future guide updates evidence-based.
Sources and evidence notes
- Sandustry on Steam
Tier 1. Developer/publisher description, Early Access status, features, and requirements; checked 2026-08-21.
- Sandustry Steam discussions
Tier 4. Used to identify recurring questions and official support topics, not to establish universal mechanics.
- Sandustry by Lantto
Tier 1. Developer overview of falling sand, automation, exploration, bosses, puzzles, and tech; demo-era mechanics are not treated as retail balance facts.