Static Dread: The Submarine Bugs & Fixes — Softlocks, 60 FPS Cap & Missing Notes

Quick Answer: Most "I am softlocked" reports in this game are undocumented interactions, not bugs, and the ones that were real bugs got fixed fast. Stiff hatches need the interact key mashed, not pressed — the developer's own wording. The route planner gives you more range for a messy route than a clean one, which is what strands people at the last sonar shift. The 60 FPS cap comes off by turning V-Sync on. Patch 1.0.1 (August 17) closed the day-4 Captain's Quarters softlock, the coffee machine and a mission-menu softlock, and made the first official move on the voice-versus-subtitle mismatch. The mainframe puzzle is not a puzzle — the developers say it is broken on purpose, does not affect your ending, and is meant to be brute-forced. The one thing still open is the missing mainframe console, promised twice and still not shipped.

Version note: Current for Patch 1.0.1, shipped August 17, 2026, and checked August 19. The game is five days old and has had three updates. Patch contents are quoted from the developers' Steam announcements; everything else comes from launch-week forum threads and reviews, with developer replies attributed in place. Single reports are labelled as such.

Four days old, three patches deep, and the first big one closed most of the launch-week softlocks. (Screenshot: solarsuit.games)

Patch Timeline

The August 15 one is worth understanding, because it corrupted endings rather than crashing anything. A player described the symptom before the fix: they picked up a key during what should have been the good-ending route, and afterwards "it seemed like 2 routes were intertwined, i saw both the normal and mutated crews at the same time along with their dialogue." If you played on launch day and your ending felt incoherent, that was the bug. Update before any route-hunting, or the ending you get will not be the one your choices earned.

What Patch 1.0.1 Fixed

The developers grouped it themselves. Quoting the announcement:

Critical

• The Captain's interactions going missing "after loading an autosave made during rest"
• The mission menu "can no longer be opened at the wrong moment and soft-lock your progress"
• "Fixed the coffee machine."

Story and characters

• "Several dialogues didn't account for whether a character was alive or dead — conversations now behave logically as the story unfolds."
• The journal entry about Zack
• Kelly's lines during the Temple quest when she is standing by the door

Gameplay

• Getting stuck in the terminal during the Mutiny ending
• An out-of-bounds gap in the cave during the Cthulhu ending, now blocked by a collider
• The journal entry not appearing when you kill Kelly
• Geometry issues and clipping characters
• The darts leaderboard refreshing daily
• Input now blocked while the Steam overlay is open
• Text overflowing UI borders, plus translation fixes

Two of those are worth reading twice. The first three critical fixes are exactly the day-4 softlock that dominated the launch-week forums, and the alive/dead dialogue fix is the first official movement on the game's most-reported complaint. Both are covered in full below.

Still Promised, Not Yet Shipped

Patch 1.0.1 closes with a "coming later this week" list. Track these rather than assuming they landed:

1. A console with a lore Log, for reading the notes you and your crewmates collect
2. An end-of-game screen showing your playthrough branches, so you can see how much you have unlocked across runs
3. More sound and dialogue fixes — the developers say they are re-listening to every recorded line and bringing the text in line with what is actually said

Not Bugs: Three Things That Look Like Softlocks

Hatches That Animate but Do Not Open

Developer-answered. A player stuck at the biohazard section — needing to reach the radioactive elements, life support restored behind the bulkhead, hatch playing a turning animation and never opening — posted that they were sure it was a bug and could not continue. The developer account solarsuit replied:

"Try pressing it multiple times — to open those hatches you need to apply force to the valve. Do it by hitting the button rapidly to open the door."

It worked. The reporter's response is the honest summary: "Thanks. You really need to make this a lot clearer in the game. It took way to long to figure out what to do."

Rule: mash the interact key on any hatch that turns but does not open. The same player noted they had hit this before elsewhere in the boat and worked around it by accident, so it is not specific to one door.

Running Out of Range on the Route Planner

Covered in full on the beginner guide, but it belongs here too because people report it as a bug at the final sonar shift.

Drawing an efficient route costs you distance. A player who could not reach the green zone — with two torpedo events that claimed to have opened new paths and no visible map change — found the answer himself:

"I had to make very small movements resulting in a lot more 'pips' along my route and that for some reason gave me just enough movement to reach the green zone. If I tried to get to the zone in as few direction changes as possible and minimizing those pips I would run out of movement."

He is right that it is inconsistent, and says the tutorial should explain it. Two supporting notes from that thread: you can route through orange zones, and one player reached the green zone without torpedoing any obstacles at all.

Also from that thread: crew Energy does not limit boat movement. Do not burn a shift resting your crew to fix a range problem.

Doors and Machines That Are Timing, Not Permission

The coffee pot is once per shift, and the Captain will not always see you — sometimes it is simply not that point in the story. Check your task list before deciding the game has broken.

But this one had a real bug underneath it, and it is now fixed. See below.

The Day-4 Captain's Quarters Softlock — Fixed in 1.0.1

This was the launch week's worst trap, and it is closed. The symptom: on day 4, with the torpedo unlocked, no interact prompt on the Captain's Quarters door and no access to the coffee machine, with every crewmate already talked to. Two players hit it; reloading worked for one and not the other.

The developer account solarsuit answered the thread with "Hotfix for that should arrive today or tomorrow," and Patch 1.0.1 named the cause: the Captain's interactions went missing after loading an autosave made during rest. The coffee machine fix shipped in the same batch.

If you are on 1.0.1 and still have no prompt, the recovery advice from that thread still applies, because it was never about reloading harder:

"Reloading the last one, or even last 2 saves might not be enough. You'll have to go earlier than that."

There is no chapter select in this game. Keep manual saves at shift boundaries. The only recovery anyone demonstrated for a genuine story break was going back further than felt reasonable.

The Mainframe Puzzle: There Is No Solution, and It Costs You Nothing

Answered, and the answer reverses what the thread had concluded. The pattern-classification sequence at the mainframe reads like a puzzle you are failing, and three players had talked themselves into believing that reaching it at all was a fail state — "From what I gathered there isn't one, and reaching it is a fail state. If there is one, the game did a terrible job alluding to it."

That is wrong on both counts. Someone answering on the developers' behalf — an account with 269 hours logged on a game that has only been public since August 14, so a pre-release build — settled it in that thread:

"Mainframe's last dialogs in the infinite corridor room are not tied to anything in particular, they reflect broken state of mainframe itself. Endings are not influenced by it in any way. You just bruteforce it."

Three things follow, and all of them save you time:

• You are not being scored. The dialogue in the infinite corridor is flavour for a mainframe that is itself broken, not a test you passed or failed.
• It does not touch your ending. So do not reload to "fix" it. Which ending you get is decided by the pills, the entity and the mutiny, not by this.
• Brute force is the intended input. Keep entering combinations until it moves on.

The one dead lead worth closing: a player who arrived with only the Captain, the Doctor and themselves wondered whether the full crew changes the outcome. Another player with the full crew reported the identical result. Cast composition makes no difference here.

The reason this misleads is presentational, and a player in the thread put it precisely: the sequence gives you the impression you are being handed repeated attempts at a puzzle, so failing it reads as your mistake rather than as the mainframe being broken on purpose.

The 60 FPS Cap: Turn V-Sync ON

Counter-intuitive, and the developer explained why:

"if we didn't cap the FPS, on stronger hardware the game starts running at 300–400 FPS and thrashes the GPU with unnecessary calculations. V-sync is tied to your monitor's refresh rate and forces the game to match whatever the monitor is set to. That's the correct setting in your case."

The player who asked — 4090, 32 GB, Windows 11, 240 Hz monitor, game feeling sluggish at 60 — enabled V-Sync and reported jumping to 200 FPS.

If enabling V-Sync does not help, check the other lead from the same thread: your Windows display settings may still be at 60 Hz even though the monitor supports more. Another player reports running at 120 Hz on a TV without trouble.

Confirmed Open Defects

The Mainframe Notes Still Have Nowhere to Be Read

Your crew announces that notes have been uploaded to the mainframe, and there is no console to read them on. You are not missing a menu. A developer account replied to the thread:

"We're currently fixing this issue and will add the console by the middle of next week"

Do not restart your run over this. A player in that thread asked exactly that — whether to keep playing or wait — and the developer answered:

"We'll add a special Console for reading those notes. Everything you've opened is saved, so after that update you'll be able to load your last day during the Rest segment and read everything you and your crewmates collected."

So the data is being recorded even though you cannot see it. Keep playing, keep a save on your last day, and read the log after the update.

Two smaller notes. The notes are readable from the mess hall in the current build — a player confirmed that, and added that they look important enough to be worth not skipping. And a second player in that thread had reasoned that the inaccessible mainframe was intentional worldbuilding, which the developer's answer rules out.

Status: still not shipped. Patch 1.0.1 on August 17 lists the console under "coming later this week" rather than delivering it, so the commitment has now been made twice without landing.

Spoken Dialogue Does Not Match the Subtitles — Now Acknowledged

The most-reported defect in the game's reviews. Four separate reviewers describe it independently:

• "There are major and frequent discrepancies between what the voice actors say vs. what's written on screen."
• "how horribly mangled the voice dialogue is vs. the written dialogue that appears on the screen. Numerous instances where the voice lines come nowhere close to what's being displayed"
• "The voice acting isn't bad but it rarely match's what's on the screen to the point it contradicts what's being said."

It got worse than cosmetic. One reviewer reported characters inside a single conversation losing track of whether a crewmate is alive or dead. A Russian-language reviewer described a related sequencing failure: a crew member chats with you normally and is then written out in the next beat, as though a conversation in between never played.

Patch 1.0.1 moved on both halves of this, four days after release. The alive/dead problem is named and fixed — "Several dialogues didn't account for whether a character was alive or dead — conversations now behave logically as the story unfolds" — and the broader mismatch is now an announced work item rather than a silence:

"More sound design and dialogue fixes. We're re-listening to every recorded line and bringing the text in line with what's actually said."

Until that pass lands, keep trusting the subtitles. They are what the story state actually is, and the fix direction the developers describe is bringing the text and audio together, not overwriting the text.

The Warhead Chase: How to Actually Get Through It

The late-game monster sequence is the single most-complained-about section, including from players who otherwise liked the game — one negative review calls it "Absolutely horrible, no way to understand where you're supposed to be going."

Two players posted the sequence. This is player-reported, not developer-confirmed:

1. Shoot the monster to its knees.
2. Run to the terminal and power it up.
3. Shoot it to its knees again, until the terminal goes green.
4. Interact with the terminal a second time.
5. Shoot it down once more, then run to the ladder at the start of the level.

Why people miss the terminal: a second player clarifies there are two chambers, and the target terminal presents "an 'interactable' white dot on it which really looks like any other terminal." It must be used twice, and then you return to the first chamber for the ladder.

Three things that are intentional and will make you think you are bugged: the gun jams by design for horror effect, you randomly slow down while running, and checking the mission UI does not pause the game. Also, the monster can spawn ahead of you, so running does not reliably buy distance.

One thing here was a real bug, and 1.0.1 fixed it: the mission menu could be opened at the wrong moment and softlock your progress. If you opened the mission UI mid-chase before August 17 and everything stopped responding, that was the defect, not the design.

The player who worked it out is measured about it — "It relies on you dying a lot till you figure it out... It's good for thrills to a point, but It's unfair level design" — and hopes the developers tweak it. The chase itself has not been changed.

Smaller Reports and Missing Features

• No key rebinding, and none promised. There is no option to redefine keys, raised specifically because running is bound to holding Shift. The developer answered the thread rather than ignoring it, but the answer is not a commitment: "It's actually not that simple - it requires quite a bit of tedious work, especially on the UI side. And to get there we need to mature as a studio!" A player replied that this makes the game inaccessible for some people. Plan around holding Shift.
• The engineering wire minigame not responding. One report, from the stealth upgrade with the warhead aboard: the connect-the-terminals puzzle accepts clicks on the socket squares and plays the click sound, but nothing on the board changes. Another player confirmed the puzzle's goal (wire every square until all the lights are green) but not the fault. Single report, no developer reply — if the board is genuinely inert rather than just hard, reload rather than grinding at it.
• Ultrawide is untested but appears to work. Asked about 21:9 and 32:9, the developer said "It should work, yes, but we didn't test those modes thoroughly." A player then confirmed 32:9 running with no bugs or issues.
• Graphics look rougher than the first game. One reviewer's comparison against Static Dread: The Lighthouse. Single source, and a matter of judgement rather than a defect.
• Demo saves do not transfer, and the demo is gone. The developers closed it on August 3 and stated twice that saves would not carry over and that the demo build differed significantly from the final game.
• Windows only. No Mac or Linux build.

Reporting Something Not Here

Use the Steam discussions — both developer accounts answer there within a day, and several of the answers on this page came from threads that were a few hours old. The developers also run a Discord linked from their release announcement.