Launch Troubleshooting and Known Issues

This page is a dated launch-status checklist reviewed on July 29, 2026. It separates v1.0.1 fixes, same-day developer confirmations, and unresolved reports that still need a reproducible cause.

Confirm the version first

v1.0.1 addresses three launch problems:

Before rebuilding a grid or abandoning a save, update the game, restart it, and reproduce the symptom once on the current version.

POI pickup after an Augment

The developer separately marked the reported POI pickup problem fixed. If pickup still fails:

1. confirm the game is current;
2. leave and re-enter the affected view if that is safe;
3. test a different visible POI;
4. record the exact POI, Augment, and sequence before reporting it.

Do not use an unverified save edit or destructive file workaround.

Map stuck at 0/0

A launch-day world-generation failure could produce an unusable Map at 0/0. The developer confirmed that an early Trader spawning too close could also soft-lock Scavenge and marked that Trader case fixed. The separate broken Map state was still being worked on in the reviewed discussion.

If this still occurs on the current version:

1. record the exact version before restarting;
2. note whether Navigation, Mobility, and the Map had just been unlocked;
3. check whether the Map has any usable destination at all;
4. avoid deleting a grid or editing a save to solve a world-generation fault;
5. report the reproduction sequence and whether a new run produces a world.

WASD camera movement or selecting a destination cannot repair a world that never generated usable coordinates.

Collector and timed components

The full-release base Collector has a 20-second cooldown, and its tier-two version is described as faster and more compact. Wait through a complete cooldown before reporting that it is inactive. For Smart Grabber, Sensor, and Spinner timing questions, use the component behavior reference.

Frame-rate symptoms

The current fix caps the previously uncapped behavior at 60 FPS. If performance remains poor after updating, compare the simplest visible screen with the dense grid and Map, then check ordinary system and driver conditions. This page does not claim that every remaining performance problem has the same root cause.

If an item is still inactive

A non-working component is not automatically a launch bug. Check connector contact, direction, energy under active load, input availability, output capacity, and a complete pulse or work cycle. The inventory diagnostic gives the full order.

Intentionally unresolved here

This page does not prescribe a destructive save edit, universal component workaround, fastest reset, best build, or full-map fix without stronger evidence.