I probably should elaborate. This is why we try to not say too much, as it’s always being misinterpreted to a degree. It’s not useless to post logs and dumps for most issues. It’s useless for GPU hangs in particular, for us developers.

Our community managers are not developers, but they know how to categorize crashes based on quickly looking at the logs, so to them it’s not useless in terms of giving accurate response and referring to possible known workarounds.

Another aspect of posting logs and dumps it that the community managers can easily refer to a specific case by just linking the forum post when communicating with us.

But yes, all crashes are automatically submitted and stored in our system so it’s not strictly necessary to post it here. But it’s also mu...

Please don’t. Everytime this prompt goes up, an automatic crash report is sent to our systems along with all logs and dumps. This helps us keep track of what crashes are most critical to prioritise. If a large enough player base does this, our systems will say that everything looks good.

On that note, it’s entirely useless to post dumps and logs here, we already get all that informtaion in our system. All you need to post, if you want special assistance with a specific problem (that isn’t a GPU hang) is the GUID presented by the crash-promt. With this GUID we can look up this particular crash and get all the information available from it.

Also, GPU hangs in particular are an issue which occurs on the GPU, so crash dumps means absolutel...

Hi.

I have another thing you are welcome to try, and get back to me with wether it does any difference or not. It is to disable the mesh streamer, this will cause the game to require much more VRAM than usual, so if you have low VRAM (6Gb or so) this might not work for you.

Anyway, to disable the mesh streamer, browse to the games steam files.
Locate the file settings_common.ini in the folder bundle\application_settings
In that file, locate the section that says: mesh_streamer_settings = { … }
and change the “disable = false” to “disable = true” and save the file.

while you’re at it, or rather, if the mesh streamer hack doesn’t do anything for you, you can also try to disable the multi threaded texture streamer by changing the value
threaded_streamer = true to threaded_streamer = false in the section called feedback_streamer_settings = { … }

Disabling the threaded texture streamer will most likely degrade your performance slightly. Just so you are aware. But I am interested in seeing i...

Hi.

Have you tried to turn off DLSS, change to FSR1 or FSR2, or switched around with those settings? Just trying to see if anything in particular other than the “low”, “medium” and “high” presets could affect this.

This is very weird, but as a matter of fact, there is something you could do in order to help troubleshoot this issue. It is a bit involved, I wont lie. You would need to download pix for windows (Download - PIX on Windows). Then enable Pix to be attached to the running instance of the game by editing a settings file in the game. To do this, browse to the “Local Files” for the game, there’s a short cut to do that when right-clicking the game in steam.

image823×595 54.8 KB

This will open up a directory where you will find a bunch of directories. Go into the “bundle” and then “application_settings” directory. In there you will find a file called win32_settings.ini, open that in a text editor, and under the section named “renderer = { … }” you need to add the line:

pix ...

cTYPtKTsfMDsLHAV

Sort of looks like some sort of screen effect gone wrong. You could try to turn off various graphics settings and see if anything makes any difference.
Particularly “Lens Quality”, “Bloom”, “Depth Of Field”, “Motion Blur” comes to mind as likely candidates.

Never seen this before. I would suggest you try and verify your steam files first, to make sure eveything is correct there.
Then if that doesn’t help, delete everything in your %appdata%/Roaming/Fatshark/Darktide folder and relaunch the game.

It’s just a small (~40Mb) Binary patch, so it’s quick to toggle back and forth. And it plays against the same backend and the normal version.
I don’t want to advertise this prematurely to a bigger audience unless it actually helps.

The reality of this issue is that we really don’t know why this is happening for so many people, while not happening for yet so many others. And not being able to reproduce it myself doesn’t help at all.
But now I found something that could possibly be at least one cause, and this thred is a good place to start verifying it.

Hello all. I’m here mostly to say that yes, we are still working on this.

To that end, there is now a new experimental build live that may help with hangs. Please try it if you exerience frequent hangs. Beta password: cTYPtKTsfMDsLHAV

There is a new experimental build live which may solve some of the GPU hangs.
Please try it if you suffer from regular hangs.
Beta password: cTYPtKTsfMDsLHAV

Hi.
I looked at your crash dump file, and it seems that something goes wrong when it attempts to load the shader cache. No idea why this have happened, but I believe the files have been corrupted somehow. It should be resolvable by removing these files from your %appdata%/Roaming/Fatshark/Darktide folder:

• shader_cache.hans
• shader_library.pso_lib
• state_stream_library.pso_lib

Remove these files will cause the shader cache builder to run again and hopefully generate non corrupt files.

Hi. The build will become available in the dropdown above.

Hi.

Please try the experimental branch, beta password: cTYPtKTsfMDsLHAV

Could you also supply a screenshot of the process tree when this occurs? Like this, sorted on memory usage.

image1235×241 49.9 KB

I don’t really want to send people down some rabbithole in vain, but one thing I’ve noticed from going through all your log files is that you all seem to be running the same version of Windows11.

Have you tried to fully reinstall the drivers using DDU? (Display Driver Uninstaller Download version 18.0.5.8) (Do not attempt unless you know what you are doing! And read very carefully how it is supposed to be used!)
First run DDU to completely rid the system of every remnant of a driver, and then install the driver again from nvidia. This seem to be reported to be able to help with issues in Windows11 generally.

Another option could be to try to use the stable (studio) drivers instead of the gaming performance drivers, and see if that helps.

Meanwhile we’ll be working hard on trying to solve these issues once and for all.

That is correct. The files will be re-generated next time you launch the game. And if they for some reason contain anything broken that will be removed.

Hi!

I saw that some of you had a bunch of

21:03:17.763 [d3d12 pipeline state] creating pipeline state for #ID[50ed6411]
21:03:17.763 [d3d12 pipeline state] creating pipeline state for #ID[50ed6411]
21:03:17.853 [d3d12 pipeline state] creating pipeline state for #ID[df4fd238]
21:03:17.853 [d3d12 pipeline state] creating pipeline state for #ID[df4fd238]

in the log file right before the crash.

I’m curious if it will help to reset the shader cache.
To do that, simply delete the two .pso_lib files, and the .hans file in the same directy where user_settings.config is. I’m not saying it will help, but we need to try anything now.

Seems to be crashing from some third party thing that is being loaded by the game. RTSSHooks64.dll.
Quick google reveals that it’s something called Riva Tuner Statistics Server. It seems to be some ancient application with last stable release 2009. Try to uninstall that and try again

Well in this case it’s in that custom Dxgi.dll that it crashes. Try without reshade.

But you already have the experimental build there. It’s even selected in your screenshot? You ARE on the experimental build. If you want to go back to the normal one, select “None” in the dropdown.

Rejects! If you suffer from prominent GPU hangs, you can now opt in to try the experimental build, where it may work better for you.

Please report back

Right click the Application in steam and select “Properties”, proceed to the BETAS tab and enter this password in the text-box:

cTYPtKTsfMDsLHAV

This should unlock the “experimental” build.