[BUG] As soon as the underwater terrain shows up, the game freezes in DirectX 11 [WORKAROUND]
Alakryon
Hungary Join Date: 2016-05-02 Member: 216268Members
Hungary Join Date: 2016-05-02 Member: 216268Members
Hi,
If I play the game in DirectX 9 (using the -force-d3d9 startup parameter), there are no problems, except LOD artifacts on the terrain and some objects, when I am not set the graphics to max settings.
If I play the game in DirectX 11, the game freezes after a few seconds. At least until now, but I have found an interesting thing, see below, but first the logs:
DxDiag.txt: https://pastebin.com/vfGg5Yej
output_log.txt: https://pastebin.com/ZazVasCn
And now the interesting part.
I started the game in DirectX 9 set the graphic to full, and travelled to the Floating Island and make a save there.
Then I started up in DirectX 11 (did not change anything in the settings, only removed the startup parameter) to produce the logs above, and the game was running fine on the island, then I entered the water and still no problem, until I travelled back towards the escape capsule. As soon as the underwater terrain showed up, the game freezed again!
So until no underwater terrain is in the view, there was no problem at all!
I think it is an important info, maybe the terrain has a special, "too heavy" shader or it is another shader on some object on that terrain, which causes the issue.
If I play the game in DirectX 9 (using the -force-d3d9 startup parameter), there are no problems, except LOD artifacts on the terrain and some objects, when I am not set the graphics to max settings.
If I play the game in DirectX 11, the game freezes after a few seconds. At least until now, but I have found an interesting thing, see below, but first the logs:
DxDiag.txt: https://pastebin.com/vfGg5Yej
output_log.txt: https://pastebin.com/ZazVasCn
And now the interesting part.
I started the game in DirectX 9 set the graphic to full, and travelled to the Floating Island and make a save there.
Then I started up in DirectX 11 (did not change anything in the settings, only removed the startup parameter) to produce the logs above, and the game was running fine on the island, then I entered the water and still no problem, until I travelled back towards the escape capsule. As soon as the underwater terrain showed up, the game freezed again!
So until no underwater terrain is in the view, there was no problem at all!
I think it is an important info, maybe the terrain has a special, "too heavy" shader or it is another shader on some object on that terrain, which causes the issue.
Comments
I have also tried to install a lot of drivers for it, tried the WHQL tested ones and also the Beta Crimson drivers, right now I am using the Crimson v16.2.1 drivers released at 2017, 27th of February.
- Tried with all kinds of drivers from 2013 ones to the newest ones
- Tried with the default drivers in Windows 10 coming from Microsoft Update
- Tried to lower the GPU and VRAM clocks
- Tried to alter TDRDelay in registry
But no solution under DirectX 11, when the underwater terrain comes into view, the game is freezing to death.
The error message in event viewer is:
"Display driver amdkmdap stopped responding and has successfully recovered."
Only the DirectX 9 mode is usable for me, but as I read, it will be disabled in the future, and also running slowly than the DirectX11 mode...
If you're on the Stable version of the game you might want to try moving to the Experimental builds and see if that helps you in any way. Theres no guarantee it will but who knows
So for me there is still no solution.
Sadly using DirectX 9 is not an option from now on, it ahs been removed, so the game is completely unplayable this way.
It is no matter if I try to use OpenGL (using -force-opengl), DirectX 11, or using real fullscreen mode (using -window-mode exclusive), the game suddenly causes the graphics driver to recover, and then freezes because of that. No matter what detail level or resolution is used.
It is very sad that there is a game which was bought for money, it worked before at least with DirectX 9 as a safe mode, and now, when the final version comes out, it is unplayable at all.
I have decreased the resolution from 1920x1080 to 1280x720, and used the low detail level, turned off everything except V-Sync, and used windowed mode.
This way I can play for hours without a freeze.
However I had a problematic part, outside at the Thermal Plant I had a save in my Cyclops, and if I loaded back that save, if I went into any direction in the sub for about 5 meters, the game freezed again. It was very frustrating.
I have turned on the console, used "biome safe" to teleport out, then "warpme" to teleport back into the sub, and the 5 meter freeze issue was gone!
So after that I had chance to finish the whole game, without freezes.
I hope this help out some people who is a similar situation.
Game runs around 100fps, fps drops every now and again when I load in new zones like the kelp forrest.
But, when I entered the lost river, it drops from 100fps to 6, so have to come to a complete stop and wait for the lag to stop, then move 5m and the frames crashes again.
It even lags so bad that that the straight up CTD without so much as an error message...
System Im running is a Ryzen 1300X, 8gb 3000ghz ram and a 1050ti.
Tried to set all the settings to low, but nothing changed... So the game is pretty much unplayable for me now, cant proceed below the lost river...