How to use this fixed-issue index
Begin by comparing the symptom you observed with the exact scope of the developer's patch list. Each group below says the patch lists an issue as fixed or improved; it does not claim that this Field Manual reproduced the issue before or after the update. Similar symptoms can have different causes.
Check that Steam has finished updating the game, note whether you were using the demo or version 1.0, and record the build information visible to you before submitting a report. This page intentionally avoids community registry edits, save deletion, unofficial file replacements, and other speculative remedies.
Patch 1.0 (1577) — August 10, 2026
The developer patch lists a sometimes-missing mouse cursor after tabbing out during intros, cinematics, or scene transitions as fixed. It also lists mission events not resetting correctly when replaying the same mission, and turret position or movement not resetting correctly between missions.
Other fixed entries cover excessive interaction and system log spam; Russian, Spanish, and Polish mission-localization errors; and off-centre spotters in Blindfire. These labels describe the patch post's scope and should not be expanded into claims about every localization string, every replay state, or every cursor problem.
The improved section names error detection and reporting, random crashes on some systems, reduced RAM and VRAM usage, crater visuals, and excessive log spam. “Improved” is not the same as “eliminated.” Hardware, drivers, background software, and a distinct defect may still matter, so report a continuing problem with context rather than assuming a universal cause.
Patch 1577 also lists a stopwatch horizontal-offset setting for ultrawide monitors as added, and removal of the Chromatic Aberration post-processing effect from the pause menu. Those are change notes, not troubleshooting instructions. Patch 1577 is the latest of the three launch patches reviewed here.
Patch 1.0 (1558) — August 8, 2026
The developer patch lists save-file corruption and failure to enter missions after a crash as fixed. If a current problem resembles that wording, report the exact sequence and current build instead of deleting or replacing save data based on an unofficial suggestion. The patch statement alone does not establish the state of a particular existing file.
Additional fixed entries name the cat's eyes disappearing on Very Low graphics settings; elevation and the elevation linkage lever not resetting after exiting a mission following a shot; duplicated final fragments of patron names on cannons; the cat remaining carried after mission completion and glitching; and engine-control lights not working.
The improved section names cases where the main menu or mission loaded but mouse movement was unavailable, plus Discord code-generation or account-linking issues. Patch 1558 also adds a Motion Blur toggle for shake events such as firing or being hit. It does not promise that every input or account-linking problem has one shared cause.
Patch 1.0 (1547) — August 7, 2026
The developer's first listed launch patch names Czech and French localization errors that broke mission intel as fixed. The wording is specific to the listed localization problem; it should not be generalized into a statement that all translation or mission-intel issues were resolved.
The same post lists the cat-drop tooltip failing to disappear when looking at other interactables, coffee-machine interaction trouble while trying to return to the main menu, a pause-menu submit button not responding in certain scenarios, and an incorrect or duplicate newspaper and record at the end of the High Tide mission.
Patch 1547 also points players to the developer's HUB // Reports, Feedback & Localization thread. That reporting route is more appropriate for a current reproducible issue than a community workaround with unknown build context. Include concise observations and avoid presenting a guess as the cause.
Report an issue through the developer hub
Use the developer-linked Reports, Feedback & Localization hub for current reports. State whether the issue occurred in the demo or full game, the current build if visible, the language and relevant platform context, what you were doing immediately before the symptom, and whether it repeats. Screenshots or logs should be shared only when the destination requests them and after reviewing them for private information.
Link to the closest patch entry if the symptom appears related, but say that it resembles the entry rather than asserting it is the same defect. Clear reports help developers compare current behavior with their own records. This index will add a remedy only when a developer source lists it; it will not convert community speculation into instructions.
