4 months ago - FatsharkJulia - Direct link

Sorry to hear this. Could you please try the solution below, and let me know whether or not this helps with your issue?:

  1. Navigate to: Steam\steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings
  2. Open win32_settings using Notepad or similar
  3. Change deadlock_detector_enabled = true to deadlock_detector_enabled = false
  4. Save your changes
  5. Launch Darktide as normal
4 months ago - FatsharkJulia - Direct link

Please could you try disabling the Steam Overlay, and see if there’s any improvement?

4 months ago - FatsharkJulia - Direct link

As this was unsuccessful, you can undo the changes. Simply change false back to true :slight_smile:

I’ve been discussing this with one of our Engine Developers, and he recommends this:

  1. Navigate to Steam\steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings
  2. Open settings_common.ini with Notepad or similar
  3. Change use_blocking_io to false
  4. Change use_bank_thread to false
  5. Change use_engine_thread to false
  6. Save your changes
  7. Launch Darktide as normal
4 months ago - Axloss - Direct link

Seems like your latest crash is related to use_engine_thread. Note that we never changed these values, we are only testing this to see if any of them resolves your issue.

I would start with testing use_bank_thread as false and then use_blocking_io.

Try combos with of them. Meaning one false and the other one true and vice versa. Let us know if any combo resolves your issue.

3 months ago - Axloss - Direct link

could be unrelated to the changes, I tried this on my PC with locked 60 fps. What this flag does is that it moves the reads of streamed audio to the game thread which in theory is bad. If you are on a fast SSD it might not be that slow, but on a HDD it might cause alot of issues.

Are you running the game on a SSD? (our log tells me that you do).

Could there be issues with said drive? Perhaps try move the game to another disc if possible since the original issue could be due to this.

My guess is that your perf issues might be related to the original issue.