[Crash] Start New Game and Crash [27090]

nfearnley · January 2016

The game was running fine last night, before the H2.0 update.

After the H2.0, I deleted my old save and attempted to create a new game.

This caused the game to crash.

The game crashes in this order:

I click New Game
I select Survival
Loading screen appears
Loading happens "[something something] 90%"
Ocean background noise begins
Screens go black
AMD driver crashes
Game crashes

I have tried updating my video card drivers to the most recent version.

I have tried running both the experimental and stable branches.

I have tried reducing the resolution to 1024x768 and running the game in window moded and minimal settings.

Here is my attached DxDiag.txt and output_log.txt.

nfearnley · January 2016

It looks like if I used the -force-d3d9 argument, the crash goes away.

Luitjens · January 2016

nfearnley wrote: »

It looks like if I used the -force-d3d9 argument, the crash goes away.

Yea, suspecting on older AMD dx11 cards this is happening

BoltWarden · January 2016

Same problem here, AMD as well.

-force-d3d9 is working okay for me but I'm currently running into issues with my crosshair disappearing...

DxDiag

Mudmanrv · January 2016

I'm running an older quadcore - with ATI Radeon HD 3870 graphics. up until the H2O update - everything played fine at 1920x1080 - after patch, I can't launch the game.
anything I pick crashes. is there a suggested solution, I haven't found one yet.?

BoltWarden · January 2016

I've found a workaround for my crosshair disappearing, so I can continue to experiement with the '-force-d3d9' start condition.

Many aspects of the game have become a lot more playable for me since being forced to try out the '-force-d3d9' condition, but I am concern now as I just read on the Subnautica Trello that removal of D3D9 has been slotted for the next major update... Roadmap Trello

How likely is it that the currently effected lower end cards will have DX11 compatibility restored by the next major patch? Could I be watching the experimental builds for possible resolution to this issue?