Video walkthrough
Watch the route, then match the frames
Video chapters
5 stepsVideo references
Watch or inspect the route before you dive
Click YouTube cards to load the player. Open frame cards to compare local screenshot notes. Use the evidence to confirm landmarks, movement, and encounter pacing, then follow the written checklist below.
Patch and troubleshooting context
Watch for: Stuck state, clearance check, input/order of operations, and safe recovery.
Clearance check frame review
Watch for: Start with Tadpole dock bug fix at 00:38. Compare the screenshot cue, route note, and player action before following the guide in-game.
Unstuck result frame review
Watch for: Start with Tadpole dock bug fix at 01:22. Compare the screenshot cue, route note, and player action before following the guide in-game.
Official update checks
Patch notes that can change this guide
Video watch notes
What to pause, compare, and write down
Do not watch the video like entertainment only. Use these notes as a second-screen checklist: pause on landmarks, confirm the player action, then return to the written route.
Watchlist
Pause on Bug state and identify the landmark, depth band, or objective state before following the next step.
Use Clearance check to confirm what changed; if the video only shows a close-up, rebuild the route from the previous landmark.
Treat Unstuck result as the exit rule: finish the objective, return, and update storage or crafting before adding side goals.
Bug state
Pause when the stuck state is visible and record what the game is currently doing.
Action: Stop interacting once the bug state is visible.
Clearance check
Many vehicle issues start as clearance or state problems, not permanent save damage.
Action: Record the vehicle, door, dock, or hotbar condition.
Unstuck result
Verify the result before saving again so the fix does not preserve a worse state.
Action: Try spacing, undock, relog, or input reset steps before risky fixes.
Video route timeline
Turn the video into playable checkpoints
Use this section like a second-screen route sheet. Open each checkpoint, compare the frame, do the action, then stop if your route no longer matches the video evidence. It keeps the guide useful even when Early Access shifts small placements or creature behavior.
00:08Checkpoint 1: Stop interacting once the bug state is visible.Pause when the stuck state is visible and record what the game is currently doing.Expand
Bug state
Pause when the stuck state is visible and record what the game is currently doing.
Player action
Stop interacting once the bug state is visible.
Proof before moving on
Pause when the stuck state is visible and record what the game is currently doing.
Watch this timestampIf this fails
Reset to the last confirmed landmark or objective state, then repeat only the route-critical step.
00:38Checkpoint 2: Record the vehicle, door, dock, or hotbar condition.Many vehicle issues start as clearance or state problems, not permanent save damage.Expand
Clearance check
Many vehicle issues start as clearance or state problems, not permanent save damage.
Player action
Record the vehicle, door, dock, or hotbar condition.
Proof before moving on
Many vehicle issues start as clearance or state problems, not permanent save damage.
Watch this timestampIf this fails
Use the video frame as evidence, but record entry, proof, and exit as separate notes.
01:22Checkpoint 3: Try spacing, undock, relog, or input reset steps before risky fixes.Verify the result before saving again so the fix does not preserve a worse state.Expand
Unstuck result
Verify the result before saving again so the fix does not preserve a worse state.
Player action
Try spacing, undock, relog, or input reset steps before risky fixes.
Proof before moving on
Verify the result before saving again so the fix does not preserve a worse state.
Watch this timestampIf this fails
Return, craft, sort storage, or retest the route before turning this page into a longer objective chain.
00:08Checkpoint 4: Reload only after checking whether the current save is safe.Pause when the stuck state is visible and record what the game is currently doing.Expand
Bug state
Pause when the stuck state is visible and record what the game is currently doing.
Player action
Reload only after checking whether the current save is safe.
Proof before moving on
Pause when the stuck state is visible and record what the game is currently doing.
Watch this timestampIf this fails
Reset to the last confirmed landmark or objective state, then repeat only the route-critical step.
00:38Checkpoint 5: Submit a community note if the bug repeats in the current build.Many vehicle issues start as clearance or state problems, not permanent save damage.Expand
Clearance check
Many vehicle issues start as clearance or state problems, not permanent save damage.
Player action
Submit a community note if the bug repeats in the current build.
Proof before moving on
Many vehicle issues start as clearance or state problems, not permanent save damage.
Watch this timestampIf this fails
Use the video frame as evidence, but record entry, proof, and exit as separate notes.
Gameplay evidence
Screenshots to match before you keep swimming
Use these frames as visual checkpoints. If the terrain, lighting, or landmark does not match, slow down and re-check the route instead of forcing the next step.
Bug state
Pause when the stuck state is visible and record what the game is currently doing.
Clearance check
Many vehicle issues start as clearance or state problems, not permanent save damage.
Unstuck result
Verify the result before saving again so the fix does not preserve a worse state.
Route decision lab
Decide if this route is worth running now
This section turns the video into a practical in-game decision. Use it before leaving base, after the first landmark, and again before entering a deeper or darker area.
Route purpose
When a Subnautica 2 bug blocks progress, stop adding new actions. Save the current state if safe, document the location, try the least destructive fix first, then reload only after preserving the route note.
Visual checkpoint
Pause when the stuck state is visible and record what the game is currently doing.
Map anchor
Bug Fix Troubleshooting Anchor in Troubleshooting route note. Use it for use this when a bug blocks progress and you need a safe order of operations before reloading.
Abort rule
Spamming inputs and making the stuck state harder to describe.
Field manual translation
When a Subnautica 2 bug blocks progress, stop adding new actions. Save the current state if safe, document the location, try the least destructive fix first, then reload only after preserving the route note. Use this progression route manual as a second-screen checklist: identify the entry condition, confirm the objective with a visual proof point, then stop when the return rule is met. This keeps the article practical for Early Access patches without pretending every coordinate or state is final.
Primary job
Troubleshooting - Stop interacting once the bug state is visible.
Best entry habit
Current save - Record the vehicle, door, dock, or hotbar condition.
Stop condition
Spamming inputs and making the stuck state harder to describe. - Try spacing, undock, relog, or input reset steps before risky fixes.
Patch-safe reading
Exact item positions can shift during Early Access. The useful part of this page is the route logic: what to prepare, what visual cue to confirm, what objective to finish, and when to turn back.
Updated
2026-06-12 / tracking / Early Access
What this guide covers
Requirements
- Current save
- Known location
- No panic clicks
Use this if
You want a route you can follow from video evidence without needing exact official coordinates. The screenshots and steps are written to help you recognize areas, landmarks, and decisions while playing.
Early Access can move details. Treat this as a video-based walkthrough and verify landmarks in your own build.
Step-by-step walkthrough
Follow the video route without guessing
Stop interacting once the bug state is visible.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.
Pause when the stuck state is visible and record what the game is currently doing.
Record the vehicle, door, dock, or hotbar condition.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.
Many vehicle issues start as clearance or state problems, not permanent save damage.
Try spacing, undock, relog, or input reset steps before risky fixes.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.
Verify the result before saving again so the fix does not preserve a worse state.
Reload only after checking whether the current save is safe.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.
Pause when the stuck state is visible and record what the game is currently doing.
Submit a community note if the bug repeats in the current build.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.
Many vehicle issues start as clearance or state problems, not permanent save damage.
After-action plan
What to do after the guide works
Bank the result
Submit a community note if the bug repeats in the current build.
Clean the inventory
Move route-critical materials into labeled storage so the next dive starts with empty space and a clear job.
Pick the next guide
How to split jobs, share discoveries, avoid duplicated work, and keep co-op exploration organized in Subnautica 2.
Next route queue
Use these as the next blockers to solve after this route. Each queue card keeps the same evidence style: source video, gameplay frames, and a written checklist.
Best immediate follow-upMultiplayer Co-op Guide
How to split jobs, share discoveries, avoid duplicated work, and keep co-op exploration organized in Subnautica 2.
Use if the route branchesTadpole Upgrades Guide
A Tadpole upgrade checklist for depth modules, route expansion, module priorities, and safer vehicle planning.
Save for the next diveVehicles and Upgrades
A vehicle and upgrade planning guide for depth, storage, route safety, and progression in Subnautica 2.
Detailed notes
Treat bugs like state problems
The useful question is what state the game thinks you are in: docked, undocked, seated, input-locked, blocked, or out of clearance. Solve the state first.
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Safe troubleshooting order
Least destructive fixes first: step back, change clearance, re-enter vehicle, reset input, reload, then report. This keeps the save cleaner.
Clearance
Re-enter
Input reset
Reload
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Practical field read
Bug Fixes and Stuck State Guide works best when you treat it as a session flow with a narrow job. Start with the loadout check: Current save. Then follow the first action without adding side goals: Stop interacting once the bug state is visible.. The page should help you recognize the moment the plan becomes safer than improvising before you risk a longer dive. If the route starts producing unrelated discoveries, bank the note and return to the original objective instead of turning one guide into a full map sweep.
Loadout check: Current save
Route check: Known location
First action: Stop interacting once the bug state is visible.
Proof point: Troubleshooting
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
How to turn this into the next dive
After the first proof point, decide whether the route is solved, blocked, or worth repeating. Record the vehicle, door, dock, or hotbar condition.. If it is solved, return and convert the result into crafting, storage, a map note, or the next related guide. If it is blocked, change only one variable: bring the missing tool, clear inventory, enter from a cleaner landmark, or wait for better oxygen and vehicle support. Try spacing, undock, relog, or input reset steps before risky fixes.. Avoid the two habits that make this route feel unreliable: Spamming inputs and making the stuck state harder to describe.; Reloading before remembering the route or objective state..
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Video route notes
Bug Fixes and Stuck State Guide should be followed as a progression route, not as a memory test. Start by watching the first route movement and naming the entry condition before copying the path in-game. Stop interacting once the bug state is visible. Then pause again when the video reaches the first visible proof point, because that is where the guide changes from general advice into an action you can repeat. Record the vehicle, door, dock, or hotbar condition. If the route starts to feel different in your build, keep the same player goal: turn the video into a safe repeatable session plan.
Entry check: Current save
Route action: Stop interacting once the bug state is visible.
Proof to look for: objective proof
Version note: Early Access / tracking
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Screenshot checkpoints
Use screenshots as checkpoints instead of decoration. The first image should answer where the route begins, the second should show what confirms progress, and the third should explain what to do after the scan, pickup, puzzle state, or threat read is visible. Try spacing, undock, relog, or input reset steps before risky fixes. This is especially important in Early Access because exact positions can drift while landmarks, depth bands, room states, and player decisions stay useful. A good screenshot lets you say, "I am at the right kind of place," before you risk oxygen, storage space, or vehicle safety.
Entry frame: match the landmark before moving deeper
Proof frame: confirm objective proof
Exit frame: know the return direction before adding side goals
Loadout frame: check Known location
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Stop rule and next dive
The most useful part of this page is the stop rule. Spamming inputs and making the stuck state harder to describe. Reloading before remembering the route or objective state. When the objective is confirmed, return and convert it into progress: craft the upgrade, sort the material, save the route note, or mark the blocker as solved. If the route fails, do not repeat the same swim blindly. Change one variable at a time: enter from a clearer landmark, reduce inventory clutter, bring the missing tool, or wait until oxygen and vehicle support match the route. That turns a failed progression route into better field knowledge instead of another overextended dive.
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Common mistakes
Spamming inputs and making the stuck state harder to describe.
Reloading before remembering the route or objective state.
Assuming a bug fix video still applies after a hotfix.
FAQ
Is this guide for the current Subnautica 2 build?
This page is written for Early Access and includes a visible update date. Treat exact values as tracking notes until the current build is field-tested.
Does this page use official screenshots?
Pages combine attributed official Steam / Unknown Worlds media, local gameplay frame captures, and source-video evidence cards. New player-submitted captures should keep the route, timestamp, and build context attached.
Community notes
Add a field report
Player reports enter a moderation queue. Approved notes can load from Supabase; pending drafts stay visible in this browser for follow-up.
Near starter shallows
Approx. 70-120m from pod
Confirm oxygen before leaving the first landmark. The route is much safer when you mark the return path before collecting side materials.
Guide-wide
N/A
Creature patrol ranges and fragment placement can shift between builds, so treat exact distances as field estimates until multiple players confirm them.