Video walkthrough
Watch the route, then match the frames
Video 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 route retest reference
Watch for: Hotfix review, old-route retesting, creature tuning, and Early Access route confidence.
Route proof frame review
Watch for: Start with Hotfix update review / Route retest checklist at 01:28. Compare the screenshot cue, route note, and player action before following the guide in-game.
Retest note frame review
Watch for: Start with Hotfix update review / Route retest checklist at 02:56. Compare the screenshot cue, route note, and player action before following the guide in-game.
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 Patch system and identify the landmark, depth band, or objective state before following the next step.
Use Route proof to confirm what changed; if the video only shows a close-up, rebuild the route from the previous landmark.
Treat Retest note as the exit rule: finish the objective, return, and update storage or crafting before adding side goals.
Patch system
Start by naming which gameplay system the patch changed.
Action: Identify whether the patch changed resources, creatures, crashes, or progression.
Route proof
Retest the route entry and first proof point before trusting old footage.
Action: Retest the route entry before repeating the full guide.
Retest note
Update the route note when behavior, resources, or blockers change.
Action: Compare the first proof point with the older screenshot or video.
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:10Checkpoint 1: Identify whether the patch changed resources, creatures, crashes, or progression.Start by naming which gameplay system the patch changed.Expand
Patch system
Start by naming which gameplay system the patch changed.
Player action
Identify whether the patch changed resources, creatures, crashes, or progression.
If this fails
Reset to the last confirmed landmark or objective state, then repeat only the route-critical step.
01:28Checkpoint 2: Retest the route entry before repeating the full guide.Retest the route entry and first proof point before trusting old footage.Expand
Route proof
Retest the route entry and first proof point before trusting old footage.
Player action
Retest the route entry before repeating the full guide.
Proof before moving on
Retest the route entry and first proof point before trusting old footage.
Watch this timestampIf this fails
Use the video frame as evidence, but record entry, proof, and exit as separate notes.
02:56Checkpoint 3: Compare the first proof point with the older screenshot or video.Update the route note when behavior, resources, or blockers change.Expand
Retest note
Update the route note when behavior, resources, or blockers change.
Player action
Compare the first proof point with the older screenshot or video.
Proof before moving on
Update the route note when behavior, resources, or blockers change.
Watch this timestampIf this fails
Return, craft, sort storage, or retest the route before turning this page into a longer objective chain.
00:10Checkpoint 4: Update the route note and avoid claiming exact coordinates if details moved.Start by naming which gameplay system the patch changed.Expand
Patch system
Start by naming which gameplay system the patch changed.
Player action
Update the route note and avoid claiming exact coordinates if details moved.
If this fails
Reset to the last confirmed landmark or objective state, then repeat only the route-critical step.
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.
Patch system
Start by naming which gameplay system the patch changed.
Route proof
Retest the route entry and first proof point before trusting old footage.
Retest note
Update the route note when behavior, resources, or blockers change.
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
After a patch, retest routes by checking what system changed, repeating only the route entry and proof point, and updating notes before trusting older footage.
Visual checkpoint
Start by naming which gameplay system the patch changed.
Map anchor
Patch Route Retest Anchor in Patch retest route board. Use it for use this when older footage may be useful but early access changes could have moved details.
Abort rule
Following old footage after a patch without checking the changed system.
Field manual translation
After a patch, retest routes by checking what system changed, repeating only the route entry and proof point, and updating notes before trusting older footage. 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
After patches - Identify whether the patch changed resources, creatures, crashes, or progression.
Best entry habit
Patch note - Retest the route entry before repeating the full guide.
Stop condition
Following old footage after a patch without checking the changed system. - Compare the first proof point with the older screenshot or video.
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
- Patch note
- Old route
- Proof checkpoint
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
Identify whether the patch changed resources, creatures, crashes, or progression.
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.
Start by naming which gameplay system the patch changed.
Retest the route entry before repeating the full guide.
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.
Retest the route entry and first proof point before trusting old footage.
Compare the first proof point with the older screenshot or video.
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.
Update the route note when behavior, resources, or blockers change.
Update the route note and avoid claiming exact coordinates if details moved.
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.
Start by naming which gameplay system the patch changed.
After-action plan
What to do after the guide works
Bank the result
Update the route note and avoid claiming exact coordinates if details moved.
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
A version-aware tracker for Early Access hotfixes, creature tuning, DLSS updates, progression fixes, and guide pages that need retesting.
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-upPatch Notes and Hotfix Tracker
A version-aware tracker for Early Access hotfixes, creature tuning, DLSS updates, progression fixes, and guide pages that need retesting.
Use if the route branchesBug Fixes and Stuck State Guide
A practical troubleshooting page for stuck Tadpole states, dock clearance, hotbar input issues, and when to reload safely.
Save for the next diveFailed Route Recovery Guide
A failed route recovery guide for lost routes, stuck states, bad oxygen timing, missing tools, full inventory, and restarting a dive without repeating the same mistake.
Detailed notes
patch retest route route plan
Patch Route Retest Guide is useful when the route is treated as a focused job instead of a full-map sweep. Start by naming the blocker, checking the loadout, and matching the first landmark before copying the video. The player goal is not to memorize every second of movement; it is to understand why the route begins there, what proves progress, and when the route should stop.
Route type: patch retest route
Proof to confirm: same entry, proof point, or changed behavior confirmed
Primary blocker: Patch note
Best follow-up: Update the route note and avoid claiming exact coordinates if details moved.
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 use the video evidence
Watch for the entry frame, the proof frame, and the exit frame. The entry frame tells you whether you are in the right terrain band. The proof frame tells you whether the scan, pickup, blueprint, puzzle state, or build decision actually happened. The exit frame protects the run from turning into a panic search after the objective is already solved.
Entry frame: match terrain before diving deeper
Proof frame: confirm same entry, proof point, or changed behavior confirmed
Exit frame: return before adding side goals
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
Stop retesting when the route entry or proof point no longer matches; rewrite the route note before continuing. If the route fails, change one variable before trying again: bring the missing tool, empty inventory, approach from a clearer landmark, or wait until oxygen, vehicle depth, or defensive options match the route. That makes the next attempt safer and gives the page useful field notes instead of repeated guesswork.
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
Patch Route Retest 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. Identify whether the patch changed resources, creatures, crashes, or progression. 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. Retest the route entry before repeating the full guide. 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: Patch note
Route action: Identify whether the patch changed resources, creatures, crashes, or progression.
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. Compare the first proof point with the older screenshot or video. 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 Old route
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. Following old footage after a patch without checking the changed system. Retesting the whole route when the entry proof already failed. 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
Following old footage after a patch without checking the changed system.
Retesting the whole route when the entry proof already failed.
Treating one old coordinate as final during Early Access.
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.