Warhammer: Darktide Dev Tracker

No one in this thread is multiboxing accounts to report (it’s super easy for us to see).

If multiple people are reporting posts, then look at the posts. Not those reporting them

Anything that isn’t on topic of ‘what is depth’ is off topic.

Anything that’s just combative is inappropriate.

Anything unrelated to anything is spam.

Please stay on topic. It’s an interesting discussion being mired by folks fighting each other.

I apologise for the delayed responses but I’m sure you can understand we’ve been incredibly busy.

To make sure you receive responses in a timely manner I recommend contacting us via the Support Portal which I understand you say you’ve already done, but looking up your email address produces no results.

I was also under the impression you wanted a refund based on your previous response.

This is a very niche issue that I don’t have the answers for but I can continue to press this with development for potential solutions.

Thank you for the report Chris. Would it be possible for you to locate and upload the console log from that session for us to take a look at?

How to upload a Console Log:

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
5. Upload here

We have released a new update on the experimental branch in Steam with potential stability improvements for those experiencing GPU-related crashes.

Please be aware that PLAYER PORTRAITS are disabled in this build, and will appear blank.

PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.

1. Open the Steam client
2. Right-click Darktide in your Steam library
3. Select ‘Properties’
4. Select ‘Betas’
5. Enter the password cTYPtKTsfMDsLHAV
6. Select ‘Check Code’
7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
8. Sele...

New build deployed where only portraits are disabled. Weapons and cosmetics should be back on this one.

The current experimental have no portraits. It’s part of the experiment. I should have probably mentioned this. But this is the nature of the experimental build. I experiment and see what works. Since this GPU hang can’t be reliably reproduced in a controlled environment I need to go wide and block out parts of the engine which we suspect. Currently it has lead us to the portrait rendering system and I want to verify that it helps by disabling this system completely. Currently only one part of it is disabled, which is why I still can see some hangs comming in. But I’m planning on disabling the other part as well and see if that does it. Then we know where to dig in and figure out what is going wrong.

This article here should help with your issue:

Fix for bluetooth headphones or speaker using hands-free audio when you only want normal audio output, not hands free

Also please hop over to the experimental branch! This is a rare one, and there’s a lot of new debugging info added to shine more light on the issue when this happens.

Beta password: cTYPtKTsfMDsLHAV

I missed this initially, but your GPU drivers are outdated by more than a year.

Rejects,

We are establishing these Comm-Links, which we will use to keep you all updated on news and changes you can expect to see in the short term.

Last week we saw the release of Patch 1.0.22, shortly followed by...

We have released a new update on the experimental branch in Steam which contains new logging to support our investigation. To crash whilst using this branch would actually be very helpful for us!

PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.

1. Open the Steam client
2. Right-click Darktide in your Steam library
3. Select ‘Properties’
4. Select ‘Betas’
5. Enter the password cTYPtKTsfMDsLHAV
6. Select ‘Check Code’
7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
8. Select experimental - Experimental Builds
9. Clos...

This might not solve it, but our developers suggest trying to disable your gore settings. You could start by disabling Ragdoll Interaction, then if that doesn’t solve it try turning off Gibbing, and so on until all gore settings are off or you find the one that was causing your crashes.

It looks like you’re experiencing our notorious GPU-related crashes, unfortunately. Our developers are on the case.

For anybody missing this option, could you make sure ‘Hardware Accelerated GPU Scheduling’ is enabled?

Did you use the same email address as the one used here to submit your ticket? On looking it up in our Support Portal, it returns no results. If you created your ticket using another email address, please DM it to me