Crashes, Lag, and Performance Troubleshooting

This page was reviewed against v1.0.8 on August 5, 2026. Start by checking the version at the bottom-left of the Menu window. Several named crash paths have been fixed, but the current notes do not claim that every crash, stutter, or long-session slowdown has one cause.

Match the symptom before changing anything

Do not use a save-recovery procedure for a frame-rate problem, or rebuild a working body grid because one interface screen is expensive. The smallest repeatable comparison is more useful than changing several systems at once.

Isolate a crash without risking the save

1. Confirm v1.0.8. Close the game fully and let the current update finish.
2. Record the screen. Note whether Map, Augments, Offline, Trader, Actions, or a normal body view was visible.
3. Record what was moving. Include POI collection, item floaters, energy text, Map rendering, task delivery, or a repair countdown.
4. Repeat the smallest safe sequence once. Do not dismantle the body or spend a Reset merely to reproduce a crash.
5. Change one display variable. If the crash appears around energy numbers, compare one short session with optional energy text disabled. This is an isolation test, not a guaranteed fix.
6. Restore the setting. A difference tells you what to include in a report; it does not prove that every crash has the same root cause.

If the game crashes again, stop repeating the sequence when another attempt could cost progress. Preserve the running version, last safe action, active screen, and whether the save reopened normally.

Build a useful lag baseline

Compare the same save and resolution across three states:

1. a simple Status or body view with no new action started;
2. the Actions panel while its buttons and effects are visible;
3. the Map or a POI while travel, Harvesting, or Salvaging is active.

Record the session length and current power before each comparison. A slowdown that appears only during active Salvager or Harvester work is different from a whole-session slowdown. A drop isolated to Actions is different from Map travel stutter.

When energy stops instead of the game

Energy ending at exactly 9.9999999999998 was a separate floating-point capacity bug fixed in v1.0.7. It should not be diagnosed as a crash, a weak layout, or ordinary storage capacity. Use the energy capacity diagnostic to separate that old signature from a negative rate or a real capacity limit.

Protect recovery options

A crash followed by an older recovered point is not automatically the old Trader percentage-button corruption. Let the current game validate its save before deleting, renaming, or overwriting anything. The confirmed Trader cause, automatic valid-backup fallback, and partial-progress boundary are in Trader Save Corruption and Backup Recovery.

Report a current regression clearly

Include:

• the version shown in Menu;
• the active screen and whether the Map was rendering;
• the current power and approximate session length;
• the component or POI work in progress;
• whether energy text or floaters were visible;
• the smallest repeatable action sequence;
• whether the save reopened at the latest point or an older backup.

For a broad dated status table, return to Launch Troubleshooting and Known Issues. For Auto Explore or Auto Repair behavior that does not crash, use the Map Automation guide.