Known issues and fixes
One table for everything currently broken, its status, and whether there is anything you can do about it. Issues get added here first and only get their own page when they need one.
Last verified
· Game build 0.184.0.196275
Everything currently tracked
| Issue | Status | What you can do |
|---|---|---|
| Menu not responding / menu navigation broken | Open | Menus fail to respond correctly or become impossible to navigate cleanly. |
| Menu lists scroll upward on their own | Open | Long lists drift or jump upward, making selection unreliable. |
| Framerate collapse during large battles | Open | Comfortable framerates in the colony fall sharply during dense combat. Difficulty appears to worsen it. |
| Crashes to desktop | Open | Reported in several contexts, including the Prologue’s Elysia Frostfield decisive battle. |
| Steam Cloud overwriting offline progress | Workaround | Playing offline then syncing can present a conflict dialog. Choosing the wrong side discards your session. |
| Ultra-widescreen display problems | Hotfixed | The Prologue received an ultra-widescreen hotfix. Re-test on the current build before reporting. |
| Space / expedition screen rendering incorrectly | Reported | Reported on the discussion board as the space screen being visually broken. |
| Buildings not visible | Reported | Placed structures failing to render. Reported on the discussion board. |
| Developer console locked in public builds | By design | Not a bug. The developers lock the standard console in public builds to prevent engine crashes, which is why console-command guides for this game do not work. |
Start here if you do not know which one you have
- Game will not launch or crashes to desktop → crash troubleshooting.
- Runs, but combat is a slideshow → low FPS. Change the upscaler setting first.
- Menus fight you → menu bug, or lists scrolling upward if it is specifically drifting.
- Progress vanished → save files and Steam Cloud.
- None of these → post on the Steam discussion board with your build number and dxdiag. That board is where the developers actually respond.
Why console command guides do not work here
Worth stating up front because people waste an evening on it: the developers deliberately lock the standard developer console in public builds to prevent engine crashes. Guides promising console commands for this game are either describing a different game or a build you do not have.