Quick Answer
If Subnautica 2 is crashing or running poorly, start with the boring fixes first: install current drivers, verify files, lower expensive graphics settings, disable overlays for a test, and reproduce the issue on one normal route. Hotfixes have improved stability, but useful reports still need hardware, settings, patch version and what you were doing when the crash happened.
Current Status
Hotfix 2 included stability and gameplay fixes, but Early Access performance questions will keep moving as patches land. This page is for practical triage, not miracle tweaks. The goal is to separate one-off crashes from repeatable problems that can be reported clearly.
Start with a clean baseline
Before changing ten settings, make one baseline run. Restart the game, verify files if your platform supports it, update GPU drivers, and load the same save. Pick a normal route: leave base, swim or drive through a resource area, open a menu, return. If the crash happens in the same place or after the same action, you have something useful.
Avoid testing only in a menu or only while standing still at base. Subnautica 2 performance depends on water, creatures, lighting, streaming, UI and inventory behavior. A stable menu does not mean a stable route. A bad route test also does not mean the whole game is broken. You are looking for a pattern.
Settings worth testing
Lower reflections, shadows, volumetric or water-adjacent settings first, because underwater scenes can stack visual cost quickly. If you are chasing stutter, cap frame rate to a value your system can actually hold. A locked lower frame rate often feels better than a high target that swings every time you enter a dense area.
Disable overlays for one test: platform overlay, capture software, monitoring tools and any extra hook that sits between the game and the display. Do not leave everything disabled forever if you rely on it. The point is to isolate. If the crash disappears only when an overlay is off, you have a narrower problem to report.
DX12, AMD and hardware-specific reports
Players often search for DX12 or AMD because those words show up around modern crash reports. The safest advice is not to invent a universal fix. Check driver version, Windows updates, shader or cache behavior if your GPU tools expose it, and whether the crash is tied to loading, alt-tabbing, a specific biome, or a specific UI action.
If your system has hybrid graphics, make sure the game is using the intended GPU. If you changed launch options from a forum post, undo them for a baseline test. A tweak that helped one machine can make another less stable, especially during Early Access when patches are already changing performance behavior.
How to write a useful bug report
A good report is short and specific: patch version, platform, CPU, GPU, driver, graphics preset, save location, and the last thirty seconds before the crash. "It crashes all the time" is emotionally true, but hard to act on. "Crash after opening fabricator at base after returning from Silver route" is useful.
If the problem is frame rate rather than a crash, include where you tested. Base, shallow route, Tadpole driving, creature-heavy area and menu browsing are different performance cases. Submit the report once you can repeat it or describe the pattern. That is how a frustrating session becomes evidence instead of noise.
