It looks like I mixed this up! It’s actually Ration Pack referenced immediately before the crash - my bad.
In order of reference:
- Ration Pack
- True Level
- True Peril
and so on.
It looks like I mixed this up! It’s actually Ration Pack referenced immediately before the crash - my bad.
In order of reference:
and so on.
You’ll want to look at the events above this line:
11:44:12.941 <>Deadlock detected. Update was not called for 15 seconds.<>
The last mod mentioned prior to this crash appears to be True Level:
11:43:34.613 [Lua] [MOD][true_level][INFO] (hooks): Enabling all hooks for mod: true_level
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
This is interesting - it shouldn’t have been there, so it’s something we’re looking in to!
The rewards are added at the end of November. ...
Read moreCould you share the latest darktide_launcher.log with us please?
Sorry, I should have clarified, please check in the Task Manager → Details tab
Could you please:
GPUDetection.exe
Afterwards, a new darktide_launcher.log should be produced. Could you upload it here please?
Thank you for letting us know - we are investigating!
I suspect it’s the result of a privacy option as you say. You can access this menu using the instructions below:
[PC] Microsoft Store
Xbox
I’ll raise this to our database for investigation! Could you share your console logs with us please?
Ideally those that correspond with a session where you’ve attempted to load with the VPN enabled (and consequently errored)!
Read moreI’ve shared this with our Launcher Developers as it seems to stall prior to the launcher being displayed. I hope to have an answer for you soon.
We are monitoring these errors and have recently added telemetry to help pin them down!
In the mean time, to rule out any localised issue, it may be worth exploring the solutions here:
Read moreCould you share the URL to your Steam profile with me please?
Sorry to hear that. Have you tried this already?:
Please note that this will reset any custom keybindings.
You will then need to use the ‘Verify and Repair’ option, which is accessible via the Xbox App and will ensure the installation is complete.
You should be able to work around this particular issue by:
Please note that this will reset any custom keybindings.
You will then need to use the ‘Verify and Repair’ option, which is accessible via the Xbox App and will ensure the installation is complete.
No problem! Glad to hear the issue is resolved
Apologies for the inconvenience caused.
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