Crash in runnable thread RHIThread - Early Access: 176027 - Game unplayable after buildings start to run on biomass

[Kitster_2000]

I bought this game earlier this week, love the way it looks and feels. Just started to open up the first couple tiers, but was doing everything by hand. Everything...

Decided to try automating things, the way it was meant to be done, and ran into a lot of bugs... Iinitially, was very frustrated because when I reached a milestone and hit the upgrade button, (not the big red button, but the initial grey upgrade button) my game would crash more often than not. I had to try stupid things, like looking away... eventually I got to the point where the big red button appeared, and then no more crashes from -that-, but... now I have a new problem, one which makes the game unplayable if you plan on using power for your buildings...

In my original game, all my buildings (I didn't have very many) were on the other side of my biomass burners. Every time I approached them, the game would crash.

I had validated my game files over and over. Nothing was wrong with the files. Could not get the game to avoid crashing with "-dx11" launch option, and my OS does not support "-dx12" option. Tried "-vulkan", but screen was black on loading into game...

No, I am not playing with any mods.
Single player.
STEAM only, no EPIC log in, did not opt for EPIC on start.

I looked at the game's crash log. There's... a lot of failures in it. This is what was at the very end:

[2021.12.19-14.28.16:423][455]LogThreadingWindows: Error: Runnable thread RHIThread crashed.
[2021.12.19-14.28.16:423][455]LogWindows: Error: === Critical error: ===
[2021.12.19-14.28.16:423][455]LogWindows: Error:
[2021.12.19-14.28.16:423][455]LogWindows: Error: Fatal error: [File:D:/ws/SB-211116092526-440/UE4/Engine/Source/Runtime/Windows/D3D11RHI/Private/D3D11Commands.cpp] [Line: 1431]
[2021.12.19-14.28.16:423][455]LogWindows: Error: Null SRV (resource 0 bind 0) on UB Layout FInstancedStaticMeshVertexFactoryUniformShaderParameters
[2021.12.19-14.28.16:423][455]LogWindows: Error:
[2021.12.19-14.28.16:423][455]LogWindows: Error:
[2021.12.19-14.28.16:423][455]LogWindows: Error:
[2021.12.19-14.28.16:423][455]LogWindows: Error: Crash in runnable thread RHIThread
[2021.12.19-14.28.16:721][455]LogExit: Executing StaticShutdownAfterError
[2021.12.19-14.28.16:721][455]LogWindows: FPlatformMisc::RequestExit(1)
[2021.12.19-14.28.16:721][455]LogCore: Engine exit requested (reason: Win RequestExit)
[2021.12.19-14.28.16:751][455]Log file closed, 12/19/21 09:28:16

I tried a new game, new region, and skipping the tutorial because of the previous crashes i encountered just from trying to hit the grey update button when upgrading the hub... and the game ran fine - until I loaded biomass into the burners on my Hub. About a minute later, I got this:

2021.12.19-14.27.16:424][454]LogWindows: Windows GetLastError: The operation completed successfully. (0)
[2021.12.19-14.28.16:423][455]LogThreadingWindows: Error: Runnable thread RHIThread crashed.
[2021.12.19-14.28.16:423][455]LogWindows: Error: === Critical error: ===
[2021.12.19-14.28.16:423][455]LogWindows: Error:
[2021.12.19-14.28.16:423][455]LogWindows: Error: Fatal error: [File:D:/ws/SB-211116092526-440/UE4/Engine/Source/Runtime/Windows/D3D11RHI/Private/D3D11Commands.cpp] [Line: 1431]
[2021.12.19-14.28.16:423][455]LogWindows: Error: Null SRV (resource 0 bind 0) on UB Layout FInstancedStaticMeshVertexFactoryUniformShaderParameters
[2021.12.19-14.28.16:423][455]LogWindows: Error:
[2021.12.19-14.28.16:423][455]LogWindows: Error:
[2021.12.19-14.28.16:423][455]LogWindows: Error:
[2021.12.19-14.28.16:423][455]LogWindows: Error: Crash in runnable thread RHIThread
[2021.12.19-14.28.16:721][455]LogExit: Executing StaticShutdownAfterError
[2021.12.19-14.28.16:721][455]LogWindows: FPlatformMisc::RequestExit(1)
[2021.12.19-14.28.16:721][455]LogCore: Engine exit requested (reason: Win RequestExit)
[2021.12.19-14.28.16:751][455]Log file closed, 12/19/21 09:28:16

What I cannot tell is whether its related to the burners as they eat the biomass, or if it has something to do with the buildings as they take/give materials...

Edit: I cannot paste the full log here. Over 70K characters and STEAM only allows 18K. But its posted on the Satisfactory website.

[sansee]

It's most likely due to old shaders. Clean them up, reboot and verify, and then force DX11 if your system don't support DX12.

Or, you know, upgrade...

[Kitster_2000]

Sorry, I don't know what a shader is or how to clean it.
I'm assuming that you mean use the "-dx11" launch option when you say "force DX11"?
Doesn't work, as I mentioned...

I'm willing to believe this might help me, but not understanding the meaning behind what you're telling me makes it a moot point - and having you tell me to do something that I quite clearly said made no difference is... not helpful.

[sansee]

If you don't know what something is you search after it using a search engine and/or ask, it's not difficult...

https://en.wikipedia.org/wiki/Shader

These old ones can sometimes cause various graphics conflicts, and deleting these will make the game rebuild new ones.

The game uses DX12 now as standard, so yes, clean them (I don't know where they are on your system, but try under Steam, the game, Nvidia or Radeon, or under Directx) and then continue to force the game to use, or, upgrade so you can use DX12.

Really, It's a good habit to do this (and manually delete every files and folder related to the game) when the game has a major update, and especially when you get any problems like this. For some, this helps.

Also, you haven't mentioned your hardware so for all we know you play on a computer which is not even suitable to play the game, but you could try to upgrade/downgrade your drivers or lower your graphic settings. Then there's also -D3D11.

Lastly, these new APIs are still experimental so perhaps this is something CSS can patch out...

[Lil Puppy]

Nvidia shader cache cleaning:

Open the nvidia control panel app, global settings, disable directx shader cache.
RESTART your computer cause nvidia is stuck in the 90's still.
go to this location in explorer:
%localappdata%\NVIDIA\
there's a DX and a GL cache folder, delete them, they'll be recreated the next time they're needed.
Turn the global shader cache back on in the nvidia control panel app.

Additionally, Windows has a shader cache for directx as well that you should clear.
Start, type: cleanup
click the Disk Cleanup app or press enter since it'll be at the top and selected.
click ok for the C: drive
uncheck everything but the directx shader cache (unless you know what they are) and hit the OK button.

For AMD:
Global graphics settings, open the advanced section at the bottom, click the button at the bottom to clear the shader cache.
done.

[Kitster_2000]

I performed all of these steps, and have decided to purchase a new computer to see if -that- will work.

I have regrettably not been able to play the game the way it was intended...

But its important for the devs to understand that I -could- play the game, and could do so indefinitely... until I started to automate things.

Appreciate the input, but... whatever is causing it seems tied to having the machines running.

[sansee]

Automation isn't the issue, and certainly not a universal problem, or else the forum would have drowned in frantic support messages. Believe me, I've worked as a consultant for a long time now.

Problem is on your end, whether it's hardware/driver/OS related, or the save have become corrupt, which in very rare cases, can happen. The fact that you still refuses to write anything about your computer makes me believe your computer really is the problem.

Anyway, believe what you want, and have a merry christmas. :D

[pabienko]

Originally posted by sansee:

Automation isn't the issue, and certainly not a universal problem, or else the forum would have drowned in frantic support messages. Believe me, I've worked as a consultant for a long time now.

Problem is on your end, whether it's hardware/driver/OS related, or the save have become corrupt, which in very rare cases, can happen. The fact that you still refuses to write anything about your computer makes me believe your computer really is the problem.

Anyway, believe what you want, and have a merry christmas. :D

No, the computer is not a problem at all. I tested literally every aspect of the unreal engine. And no crash for 5 hours testing. Then i started Satisfactory and BOOM ... Dx12 crash on load up instantly... Okay... I tried Dx11... And BOOM, after literally doing nothing and just loaded fresh game and looking into forest, it have been like only 5-10 minutes to game just crash with the error (not exactly the same but you know... Crash for no reason is crash for no reason)... CPU on 20%... RAM 40% and GPU 68%... And the game crashed?

And still... Why is it happening only in the satisfactory?

The real answer to this problem is that satisfactory is now unplayable and we need to wait for devs to fix things up...

Really ... From the update 5, this problem occurs too much to be HW problem on the players PC... It has something to do with code of satisfactory... And that sucks

[FRANCISCO BUTICO]

Originally posted by Lil Puppy:

Nvidia shader cache cleaning:

Open the nvidia control panel app, global settings, disable directx shader cache.
RESTART your computer cause nvidia is stuck in the 90's still.
go to this location in explorer:
%localappdata%\NVIDIA\
there's a DX and a GL cache folder, delete them, they'll be recreated the next time they're needed.
Turn the global shader cache back on in the nvidia control panel app.

Additionally, Windows has a shader cache for directx as well that you should clear.
Start, type: cleanup
click the Disk Cleanup app or press enter since it'll be at the top and selected.
click ok for the C: drive
uncheck everything but the directx shader cache (unless you know what they are) and hit the OK button.

For AMD:
Global graphics settings, open the advanced section at the bottom, click the button at the bottom to clear the shader cache.
done.

I'm having this "Crash in runnable thread RHIThread" fatal error when I play eFootball. The game simply crashes during the matches. This tip aparently helped me (I've been trying to solve this for a month). Thank you!

[Hugh Mungus]

Originally posted by Lil Puppy:

Nvidia shader cache cleaning:

Open the nvidia control panel app, global settings, disable directx shader cache.
RESTART your computer cause nvidia is stuck in the 90's still.
go to this location in explorer:
%localappdata%\NVIDIA\
there's a DX and a GL cache folder, delete them, they'll be recreated the next time they're needed.
Turn the global shader cache back on in the nvidia control panel app.

Additionally, Windows has a shader cache for directx as well that you should clear.
Start, type: cleanup
click the Disk Cleanup app or press enter since it'll be at the top and selected.
click ok for the C: drive
uncheck everything but the directx shader cache (unless you know what they are) and hit the OK button.

For AMD:
Global graphics settings, open the advanced section at the bottom, click the button at the bottom to clear the shader cache.
done.

Even years later, this is proving helpful to me in fixing the Texas Chainsaw Massacre game when it shat the bed out of nowhere weeks ago and I tried ripping out everything BUT the directx to fix it. Thank you, sir, you are a scholar and a gentleman.