Warhammer: Darktide Dev Tracker

In the logs I saw a crash in it was GPU hangs, which is very hard to debug.

But some had logs about pso creation so might be worth delete the local files for that and see if that helps. Let us know in that case.

in %APPDATA%/Fatshark/Darktide
shader_cache.hans
shader_library.pso_lib
state_stream_library.pso_lib

I’ve seen more users get stuck very early in the setup phase of the game.

We have added so we can detect such deadlocks, but not sure if this will be added to the patch we will release very soon or the one after that.

This will only help us to detect the issue since we then can trigger a crashdump during this phase which we then can analyze.

This is an issue with French (and other) 4G providers unfortunately. The ‘Free’ ISP is also impacted.

We are looking in to this, but I apologise I have no immediate solution, other than changing network which I understand isn’t an option!

I’m happy to help with a refund should you rather take that option.

This is a known crash and will be resolved in our upcoming patch, however, you should be able to work around this by deleting your AppData:

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 ‘Darktide’ directory

You may then need to use the ‘Verify Integrity of Game Files’ option via Steam:

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

This is part 3 of the provisional Patch Notes for Patch #14 for Part 1 click ...

This is part 2 of the provisional Patch Notes for Patch #14 for Part 1 click ...

Devoted Rejects,

Today we are sharing with you the provisional notes for our next patch - Patch #14. This update will mainly be comprised of needed balance changes and bug fixes from the Class Rework in Patch #13.

Just to make you aware these notes and changes are not final, and may still be changed before the release.

...

Could you try disabling ‘Portrait Rendering’ via the ‘Settings’ → ‘Interface’ menu please, and see if there’s a reduction in the rate at which you crash?

As you’ve already noticed here, the error produced is DXGI_ERROR_DRIVER_INTERNAL_ERROR. This is ultimately a driver or GPU-related issue, but it sounds like you’ve exhausted many solutions already. Could your GPU be overheating?

Try a clean driver re-installation instead of simply updating

Do you happen to have the same Curio equipped in separate slots?

Hi @OngoNasty,

The error in the logs indicate a conflict with the Overwolf overlay.

Could you please try disabling this overlay and check to see if the issue resolves?

Yes, it’s so if it’s something account related, we can look into it.

You can submit reports to our support portal: https://support.fatshark.se/hc
Please provide as much information and evidence as possible

Hello! Do you have a Wacom tablet? If so, could you try disconnecting it?

Unfortunately, crashes like this which are specific to your GPU and all of your system variables aren’t all straightforward with a catch-all fix Your logs show a GPU hang, where it stalls and results in the crashes you’re experiencing.

I understand you’ve exhausted all of our usual solutions. If you can provide additional recent crash reports/console logs I can try escalating this with our Engine Developers; though I can’t guarantee they will have further suggestions; or alternatively I can assist with a refund. Please let me know if this is something you’d wish to do.

I’ve discussed this with our Engine Developers and I’ve been informed this is a particularly complicated issue.

Some players have been able to work around this by editing a registry key, but this isn’t something I’d recommend for the sake of making Darktide work.

With that in mind, would you like me to help you with a refund?

Sorry about this - I’ve raised your issue with our Engine Developers.

Hi @Kiba_Mar-Glas

This specific crash should be resolved in our next update. The current cause is a specific sound device being set, then this device being removed/disconnected with Darktide closed. Then upon relaunching it isn’t recognising the sound device and is subsequently crashing.

In the meantime, you should be able to resolve this by removing your Darktide Appdata directory (please note, by doing so you will lose any custom settings/configurations e.g. keybindings).

To do so:

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. Restart Darktide as normal

Please let me know how it goes.

We are working on Error Code: 2014. Could you tell me which ISP you’re with please?