Warhammer: Darktide Dev Tracker

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.

Hey, regarding this - i’ve been testing it this evening and can’t repro it. Do you have any specific weapons or any videos of this happening?

Hey TopShop, please could you try this?:

Delete Darktide AppData & Verify Integrity of Game Files

NOTE: This will reset any custom keybindings.

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to: AppData\Roaming\Fatshark
4. Delete the entire ‘Darktide’ directory
5. Launch Darktide as normal

You will then need to use the ‘Verify Integrity of Game Files’ option, which is accessible via the Steam client and will ensure the installation is complete.

1. Right-click Darktide in your Steam library sidebar
2. Select ‘Properties’
3. Select the ‘Local Files’ tab
4. Select the ‘Verify Integrity of Game Files’ button
5. When complete, close and reopen Steam

NOTE: If Steam Cloud saving is enabled for Darktide, this may automatically restore the AppData and consequently cause the error t...

If they are separate issues please add a bug report for each one separately - although try to check first to see if they have already been raised to avoid duplicates!

This hotfix was pushed out as a priority due to it addressing the crash.

Fixes for the surge staff and exhilarating takedown will be in the next hotfix which is currently being processed!

Not at all!

Having full body explosions occur on every kill vastly overstates the power of the weapon while reducing visibility a lot for other players with the gore and blood clouds.

We are working to fix the bug so the damage and targeting of the Surge staff and Smite returns to normal. Alongside this we will add that critical strikes will guarantee that the enemy chest will explode, adding some of the gore back in.

Assail crystals and the Melee power attacks I will have to investigate separately

This bug should be fixed with the next update!

We are investigating the reports of Out of Memory errors that have appeared with our latest update.

Existing reports may be merged here, to help us keep track of the issues being reported.

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

Devoted Rejects,

Here are the notes for Hotfix 1.2.11 which just went live on Steam.

• Fixed a crash which could happen if a player joined a mission while a projectile was traveling in the air.
• Fixed an issue where the Veteran “Onslaught” talent did not affect melee attacks.

Missed Patch Notes ...

You can disable the Headgear Voice Effect via Options → Audio.

I’ll be sure to pass it along! Thanks for referencing the mod as well, i’ll add that to the feedback.

Sorry to hear this. As a potential workaround, please try:

Delete Darktide AppData & Verify

NOTE: This will reset any custom keybindings.

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to: AppData\Roaming\Fatshark\MicrosoftStore
4. Delete the entire ‘Darktide’ directory
5. Launch Darktide as normal

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.

1. Open the Xbox App
2. In ‘My Library’, select ‘Darktide’
3. Select ‘More Options (…)’
4. Select ‘Manage’
5. Select ‘Files’
6. Select ‘Verify and Repair’

Got it - I’ve sent you a DM.

If you are observing the Account Authentication Failure. error on attempting to load in to Darktide, it means your account has been banned.

The error is not adequately localised at this time, which is why it contains exposed code.

To know when your ban expires, please contact us at https://fatshark.se/support.

If you are experiencing a crash after building the shader cache, or encountering the Something went wrong in the Shader Cache Builder process Exit code = 1 error, please see the solutions listed in the article linked below: