Moon Sweepers Crash and Low FPS Troubleshooting

Moon Sweepers crash checks: record your setup first

Separate failure to launch, a crash after playing and low FPS during a working session. Record the CPU, GPU, operating system, game version, resolution and exact error. The official requirements page is the starting point for compatibility, not proof that a large automated base will achieve a particular FPS. [1]

• Note whether the issue occurs in a new world or only in an existing one.
• Note whether you are hosting or joining.
• Keep the error text and the action immediately before the failure.
• Record current launch options so any change can be reversed.

A freeze shortly after loading is a separate symptom

Patch 1.0.5 reports a freeze about half a minute after loading a world on both DirectX 11 and DirectX 12. That timing is useful context when recording a failure; the developer’s statement does not establish that a new freeze has the same cause or that switching renderers repairs it. [4]

Record how long the world runs before the freeze, the installed build, renderer, host/client role and whether the same action precedes it. Compare those details with the dated announcement before changing several settings.

• Read the dated 1.0.5 stability changes ↗Match the symptom and version to the developer’s report before treating an old setting suggestion as a fix.

AMD and DirectX: begin with the documented default

According to patch 1.0.4, Windows now defaults to DirectX 11 to prevent AMD GPU crashes. The same notes document -force-d3d12 for deliberately selecting DirectX 12. If that override is present during an AMD crash diagnosis, record it and test the current default rather than assuming the recommended-specification DX12 entry requires the override. [2]

• Open the game’s Steam Properties and inspect any launch options.
• If you previously added -force-d3d12, keep a note of it before removing it for a default-renderer comparison.
• Change only that one factor for the comparison.
• Report the renderer and whether the symptom changed; do not treat a successful launch as proof of long-session stability.

Update deliberately and keep a reproducible record

Bring the game to the current Steam build and review its official changes. Use your hardware vendor’s official support channel for drivers. Driver, overlay or graphics-setting comparisons are general diagnostic steps; the sources checked here do not prove that one of them fixes every Moon Sweepers crash.

• Keep a copy of the original settings before changing them.
• Test one change at a time with the same scene or action.
• Avoid unofficial “repair” executables or configuration files from an unknown source.
• Do not disable system security protections to make a game launch.

Use scene comparisons to investigate low FPS

The 1.0.3 notes report optimisation work on large bases, driving and ground loading. Patch 1.0.5 separately reports fewer garbage-collection stutters on large bases and fixes for memory leaks after leaving a world or removing structures. These are developer-reported changes, not this site’s benchmark or a promised FPS increase. [3][4]

Compare the same settings in a simple area and the scene that performs poorly, then keep the scene, settings and observation interval with the result. Distinguish regular low frame rate from intermittent stutter and from a freeze after loading.

Preserve saves after a crash

Patch 1.0.4 documents automatic local backups and damaged-save checks after a crash. Copy existing files before attempting manual recovery. A crash diagnosis should not begin by deleting the world or overwriting the only remaining backup. [2]

Saves created by 1.0.4 cannot be opened in older versions, according to the developer. Downgrading is therefore not a neutral recovery step. [2]

• Review the backup and version-compatibility warning ↗Automatic damaged-save repair is separate from an independently verified manual restoration procedure.

Send a useful report if the problem remains

Use the developer’s official bug-report route from the 1.0.5 announcement. Include the version, hardware, exact error, renderer choice, timing, a short reproduction and what you already compared. If you only have a player report or a suggested setting, label it that way rather than reporting it as a confirmed fix. [4]

• Compare the official PC requirements ↗
• Check the Steam Deck and Linux compatibility evidence ↗Record the OS and Proton version as well as the game build when investigating a compatibility-layer result.
• Choose a different troubleshooting symptom ↗