Axloss

Nvidia couldn’t see any reason why it get stuck either. You could see if removing the check makes the game continue instead of crashing. In this case you timeout due to the engine being stuck here for 2 min.

in game files, lookup this file win32_settings.ini and change value of deadlock_detector_enabled to false

I was able to launch the game somewhat consistently by reinstalling my graphics drivers (Nvidia) before launching the game, after which the game would run almost perfectly. However, I would ...

FYI in your case the game is stuck in ntmarta.dll never seen that one before.

edit: after further inspection it looks like its’ stuck in a sl dll. I will send this to Nvidia and ask if they can see anything

ive been working on improving the deadlock reporting when it happens early.

My suspicion is that it’s an issue with game overlay in steam. Try disable it from steam menu and see if that helps. If this is an issue, this is nothing we can fix since it’s on valve.

great

you can also try to rename the folder

%appdata%\Fatshark\Darktide

this contains your user config but also the file it looks like it stuck on. By renaming it you will create new user config and new .pso files. You can move your old config to the new folder if this works.

with it enabled, please upload your latest crash as well. Might see something new.

Will take another look, but since the game doesn’t go anywere it is not a false positive

im curious does it work with the controller connected now without the game crashing? we have not managed to reproduce this issue.

However the ps4/ps5 controller support seems to be broken regardless due to some other unknowns.

Sadly I can’t answer that but it’s worth a try. But in this case I would say that any driver that nvidia experiance gives you should be fine.

What’s happening in your case (what we could see before atleast) was that bink crashed when generating d3d12 shaders, these shaders are inbuilt in the exe and same for all users meaning that I expect same behaviour for all users unless something is wrong on the user side.

Since this code is likely not HW related but perhaps more linked to your OS a driver update might not help here.

Also pretty sure all of the crashes above has all been in d3d12 dlls

m...

@Seb_Cz just because it’s after shader cache doesnt mean it’s the same issue. We always launch the shader cache first so that’s what ppl remember.

In many cases shader cache succeded and we can clearly see in the crash that it’s the game process that failed. They are 2 seperate processes so in theory we should be fine running the game regardless of shader cache status.

can you upload any new crash with this turned to false?

for example: GUID: f9c66f17-4264-4c7a-a401-dfd1ac7f5bc0

I pushed a change that should fix this with the next patch, but if you still get it at that point please let us know.

Basically we will pause the deadlock detection while reading this file cache since if wait on reads we might block the game for more than 15 s and thus triggering this crash.

This is most likely only an issue with HDD that might have issues with Darktide having alot of small files.

application_settings\win32_settings.ini

you should find this in your game files. set variable deadlock_detector_enabled to false instead of true

so it says
deadlock_detector_enabled = false

we will make sure it works with it connected in the future.

I think some ps4/ps5 controller support sneaked into the release which is why this issue started for you.

We will likely disable it in next patch until it works properly

was this another hang? I could not debug it since the crash info was not complete. If it’s an issue in the intel driver I suspect that they might exit our game, since the exit code does not belong to our game.

could you try this (another known issue for AMD, but perhaps same issue for intel here)

From another thread

i looked a bit deeper in the crashdump and found out that it’s likely stalling on creating ray tracing objects (regardless if you have it on or not).

To force it off you can try in game files open win32_settings.ini and set ray_tracing, to false.
Meaning it should say
ray_tracing = false
instead of
ray_tracing = true

we are looking into how we can fix this in the future. Since modifying the ini file is not a good solution since it will be restored if you verify game files

I’ve forward this issue to Nvidia and see if they have any ideas. Next step would be to check if there is any updates for bink that could fix this.

we added deadlock detection early ingame to catch other errors and this is a false positive result due to this.

i think this is a false positive of a deadlock due to slow reads (running the game on a HDD).

We will try make an exception while reading the pso libs from appdata since it’s a blocking operation.

edit: mixing two different crashes.

You likely have a ps4/ps5 controller connect. Try disconnect it and see how it works.

I will see if we changed anything regarding that in the code base

if this doesn’t help I can re-build binaries locally and we can try with that