Warhammer: Darktide Dev Tracker

This thread has run it’s course. Lock applied.

Sorry to hear this - I’ve shared your report with our developers.

This sounds irrelevant, but do you happen to have an Oculus or other VR headset connected to your PC? Your symptoms are similar to an old issue we had on Vermintide 2.

Thank you for your detailed report! I will raise this for investigation.

We are aware of and looking in to this error, apologies!

This is, unfortunately, the same as: KNOWN ISSUE: Crash on Launch With `AMD Radeon RX 6700/6900 XT`

AMD are aware of the issue.

That’s odd - which version of Chrome are you running please? (Help → About Google Chrome)

Hi @gargrim,

Can you please try the following (though please note that doing so will reset your game settings, so any custom settings/keybinds etc. will need to be set up again)

1. Press Windows key + R
2. Enter %appdata% within the search field and select ‘OK’
3. Delete the ‘Fatshark’ folder
4. Launch Darktide (this will recreate the deleted folder)

Let me know how it goes

From the logs you’re running into non-descript Access Violation crashes - though it seems with BSOD’s you may have a deeper system issue. Sorry to hear that

It may be worth checking out some potential solutions here, just in case:

Sure, closing as requested.

Hey. You can reach out to us at https://fatshark.se/support

I think this post has run its course. Time to move on. Thread locked.

Could you share your crash report with us, please?

Hi! Thank you for taking the time to repport bugs!

I think you might confuse Rending and Brittleness. Rending gives a bonus on the attack itself. So For this blessing the crit attacks themselves are rending and gives higher damage to armored enemies. Brittleness gives out a debuff on the minions that cases subsequent attacks to be rending for all players.

Best regards! / Guen

Looking in to what happened as I wasn’t involved in this situation, there is a fair bit more to it than this, but I don’t fancy airing this laundry in the open unless you want that to happen. Happy to take this up in DM though.

This should now be resolved - is it still occurring for you?

We are aware of looking in to this error, apologies!