Satisfactory

Satisfactory

View Stats:
DX12: "Fix" (workaround) for "GPU Crashed or D3D Device Removed"
Not sure why it's working, and it may only be temporary or I randomly got lucky, but when I tried to enable DX12 I got this error after loading my savegame:

---------------------------------------------------------------
GPU Crashed or D3D Device Remove.

Use -d3ddebug to enable the D3D debug device.
Use -gpucrashdebugging to track current GPU state.
---------------------------------------------------------------

So, taking a wild stab in the dark (not even sure if this is how you're supposed to do it, or if this actually made any difference), from within steam I added both of those command line arguments.

If you go to your library, right click on "Satisfactory", select properties. Under "General" at the very bottom, "Launch Options", I just typed -d3ddebug -gpucrashdebugging

Again, no idea if those arguments were meant to be added to Satisfactory, or somewhere else, but at least for right now DX12 is running for me. I'll return and update if it's short-lived or just a fluke.
< >
Showing 1-8 of 8 comments
sansee Jan 22, 2021 @ 5:14am 
The reason I asked is because you can run the game with -dx12 on the normal branch. Did this also shortly after I bought the game on Steam, but back then I seem to recal the game either crashed or ran with only Dx11.

c:\steamlibrary\steamapps\common\Satisfactory\FactoryGame.exe -dx12 -NoMultiplayer

[2021.01.22-10.54.15:049][ 0]LogD3D12RHI: Found D3D12 adapter 0: Radeon (TM) RX 480 Graphics (Max supported Feature Level 12_0)
[2021.01.22-10.54.15:049][ 0]LogD3D12RHI: Adapter has 4075MB of dedicated video memory, 0MB of dedicated system memory, and 8157MB of shared system memory, 1 output[s]
[2021.01.22-10.54.15:060][ 0]LogD3D12RHI: Found D3D12 adapter 1: Microsoft Basic Render Driver (Max supported Feature Level 12_1)
[2021.01.22-10.54.15:060][ 0]LogD3D12RHI: Adapter has 0MB of dedicated video memory, 0MB of dedicated system memory, and 8157MB of shared system memory, 0 output[s]
[2021.01.22-10.54.15:060][ 0]LogD3D12RHI: Chosen D3D12 Adapter Id = 0
[2021.01.22-10.54.15:173][ 0]LogD3D12RHI: The system supports ID3D12Device1.
[2021.01.22-10.54.15:173][ 0]LogD3D12RHI: The system supports ID3D12Device2.

If not, it would've shown D3D11RHI instead. Don't know how far back the -d12 switch have been supported on the Unreal Engine.

Actually, I loaded it up with several mods and it seems to work great.
Last edited by sansee; Jan 22, 2021 @ 5:22am
sansee Jan 22, 2021 @ 5:33am 
Might be a fluke on mine. Restarted the game and it crashes as soon as I load a save or start fresh (and I get different error messages each time it crashes...).
Last edited by sansee; Jan 22, 2021 @ 5:39am
sansee Jan 22, 2021 @ 6:13am 
Here's the log if anyone is interested:
On Mega, append these together
https://
mega
.nz
/file/
IB0UnKzC#7rmbaVbRlgj2QVZkybmAwHFHdWM7MWeJE658yzVYGv0

Or: https://www111.zippyshare.com/v/1ATRZXSe/file.html
Last edited by sansee; Jan 22, 2021 @ 6:18am
Ravno [DPCK] Rath Jan 24, 2021 @ 7:29pm 
Where do you find that log so I can verify that it's running in 12 or 11? I've posted on Coffee Stain's Q&A / Bug tracker just trying to pow-wow with different people about the different errors we're getting.

Obviously, Coffee Stain isn't ready to start addressing this stuff directly (they're not supporting DX12 yet, I think they just put it out to get some early feedback), but figured as the devs start working on it it may give some insight into the different issues they need to tackle.
sansee Jan 25, 2021 @ 2:26am 
Originally posted by Ravno DPCK Rath:
Where do you find that log so I can verify that it's running in 12 or 11?

%localappdata%\FactoryGame\Saved

Also, I managed to run it again depending on the save.
Last edited by sansee; Jan 25, 2021 @ 2:27am
Finik Nov 9, 2022 @ 11:34am 
try to do undervolting. It worked for me:
https://www.youtube.com/watch?v=4NJsEzMkdWo
Lil Puppy Nov 9, 2022 @ 6:31pm 
What a necro. This thread was over 1.5 years old.

For those that find this thread: This error occurs because the GPU is doing something for too long and can't report back to the driver that it's still doing stuff and so the driver tells the operating system that the GPU has been disconnected.

There are a lot of fixes for this. Google the error and you'll find the first couple pages full of fixes.
There's a registry fix to adjust the TDR time, it works almost all the time. Other fixes include clean reinstall of your graphics drivers and system file checking and uninstalling nvidia's game optimizer software geforce experience.
Ravno [DPCK] Rath Nov 12, 2022 @ 6:05am 
Whoa, look-it that zombie! :)

Well, hopefully you weren't working on this issue since January of 2021. That's some persistence, if so!

Regardless, thanks for the follow up!! :steamthumbsup:
Last edited by Ravno [DPCK] Rath; Nov 12, 2022 @ 6:08am
< >
Showing 1-8 of 8 comments
Per page: 1530 50

Date Posted: Jan 22, 2021 @ 4:53am
Posts: 8