Subnautica 2 Errors: Fix Paths, and When to Ask for a Refund
Every documented Subnautica 2 error, the fix order that works, and how to tell a fixable bug from one that merits a refund.
Last updated 2026-09-25 · evergreen reference
This page lists the errors Subnautica 2 actually throws on PC and the order to fix them in. Start with verification and drivers, then move to the engine-specific causes. The point is to get you to a working game quickly — but also to tell you when you are done: if you have worked through this list and the game still will not run, that is the point at which a refund request is reasonable, and you should include what you tried when you contact the store.
The errors and their fixes
Symptom, cause, and the fix that resolves it.
Crash on launch
Cause: Typical Early Access causes: unverified files, stale drivers, a corrupted DirectX shader cache, or overlay conflicts with the UE5 pipeline.
Fix: Verify game file integrity, do a clean driver install, clear the DirectX shader cache from Windows Disk Cleanup, run the executable as administrator, and disable Discord and GeForce Experience overlays.
Do not force DirectX 11
Cause: Subnautica 2 requires DirectX 12 for Lumen and Nanite.
Fix: Editing Engine.ini to force DX11 causes an immediate crash. Leave the renderer on DX12 and lower Lumen instead.
“The game may not have exited correctly”
Cause: A standard Unreal notification that simply means the last session ended unexpectedly.
Fix: If the game then crashes on that window every launch, clear the temporary cache files inside the game folder in %LOCALAPPDATA% — without touching the Saved folder — and verify file integrity through Steam.
Fabricator or base crafting consumes resources and produces nothing
Cause: A known Early Access interface bug where the crafting animation stalls or tool slots get confused.
Fix: Save the game and reload the same save; base mechanics restart fully. Also avoid placing portable containers directly on the floor inside base modules, as they can fall through the floor and block the construction grid.
Freeze when swimming out of caves into open water
Cause: Dynamic object streaming plus Lumen lighting as the ocean loads new invisible sectors.
Fix: Confirm the game is on an SSD — on a hard drive these freezes are unavoidable — and lower Global Illumination to Medium or Low.
Friends cannot join co-op, or the loading screen never ends
Cause: Version mismatch or blocked network services.
Fix: Make sure every player has the same game version, restart Steam and the game, verify files, try changing the host, and check firewall, antivirus and VPN settings. Disabling crossplay temporarily can isolate it.
Frame rate degrades after two to three hours
Cause: A known memory leak in the Early Access build.
Fix: Save and restart the game every few hours. The developer has confirmed this will be patched before full release.
Fix order if you do not know which one you have
Cheapest and most reversible first.
1. Verify and restart
Verify game file integrity through your launcher and restart the PC. This clears stuck background tasks and driver hooks, and repairs the corrupt downloads that launch-day server load makes common.
2. Drivers, cleanly
Install the latest GPU driver from the vendor site rather than Windows Update, and choose the clean-install option. Both NVIDIA and AMD ship game-ready drivers for major releases that fix compatibility outright.
3. Strip overlays and background hooks
Disable Steam, Discord, Xbox Game Bar, GeForce Experience and MSI Afterburner overlays, along with RGB utilities and hardware monitors. These inject code into the game process and are one of the most frequent crash triggers.
4. Rebuild the shader cache
Clear the DirectX shader cache from Windows Disk Cleanup and delete the game’s own shader cache folder, then let it rebuild. Corrupted shader caches cause crashes that look like hardware faults.
5. Only then touch hardware settings
Remove GPU and CPU overclocks including RAM XMP/EXPO, check temperatures, and if the crash pattern points to CPU instability rather than the GPU, update the motherboard BIOS before assuming your hardware is faulty.
When to stop and request a refund
Drawing the line on unfixable problems.
Documented, acknowledged faults
If a fault is acknowledged by the developer as a known issue, say so in your refund request and include the crash pattern. Store refund windows are usually 14 days with under two hours of play, but documented technical faults that make a game unplayable are a valid reason to push past that — attach your crash logs and the steps you already tried.
What to include in the ticket
Include the full error text, when the problem began, whether it followed a patch or driver update, your hardware and driver versions, and the troubleshooting steps already attempted. A refund request with evidence is far more likely to be granted than one without.
Related pages
This is an independent player reference and is not official documentation for Subnautica 2 Errors: Fix Paths, and When to Ask for a Refund. GameFixPro does not host or link to copyrighted assets. Modding guidance is for single-player use only — never use mods in online multiplayer. Verify current requirements, prices and policies with the publisher before acting.