Warhammer: Darktide Dev Tracker

Could you see if deleting your AppData works to resolve this?:

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

Do you have the same Curio equipped in separate slots?

Try completing another mission - sometimes the connection simply needs to be reestablished!

Sorry to hear that. I’ll raise your darktide_launcher.log with our Launcher Developers in case they can spot any issues.

It sounds like it could relate to this:

(I understand the device is Bluetooth but with the receiver being USB-connected it could be the culprit!)

I’ve raised this to our database for investigation, apologies.

Thank you for the update!

Could you let us know if the issue continues after the changes you’ve made please?

Please use the ‘Verify Integrity of Game Files’ option, which is accessible via the Steam client using the instructions below:

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

Could you share the URL to your Steam profile with me please?

I have responded to your query via the Support Portal.

I believe this is tied to the Intel GPU driver. Our Engine Developers are in discussion with Intel about this.

I have sent you a DM.

It looks like the Aquilas were eventually added, so I suspect there was a bit of a delay!

Restored!

Could you share the URL to your Steam profile?

| |dxilconv.dll!hlsl::DxbcConverter::DxbcConverter(void)|Unknown|Non-user code. Symbols loaded.|
|---|---|---|---|
| |dxilconv.dll!hlsl::DxbcConverter::Alloc<>(struct IMalloc *)|Unknown|Non-user code. Symbols loaded.|
| |dxilconv.dll!CreateDxbcConverter(struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |dxilconv.dll!DxcCreateInstance(struct _GUID const &,struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |D3D12Core.dll!CShaderBytecode::FinalConstruct(struct CShaderBytecode::TConstructorArgs const &)|Unknown|Non-user code. Symbols loaded.|
| |D3D12Core.dll!CLayeredObject::CreateInstance(struct CShaderBytecode::TConstructorArgs const &,void *,void *,struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |D3D12Core.dll!CDevice::CreateLayeredChild(unsigned int,void const *,unsigned __int64,struct ID3D12LayeredUseCounted *,struct _GUID const &,void * *)|Unknown|Non-user code. Symbols loaded.|
| |D3D1...

all but one of the hangs is in a dll called tier0_s64.dll which is managed by steam. The last one was in a steam api call but from my perspective it doesn’t look like it’s deadlock in that case, just really slow (15s update, which we cutoff as a deadlock).

Sadly we can’t investigate further than this. Try update your steam client. In the next patch we plan to improve deadlock reporting to find info from our exe if possible. But it’s not 100% we will get any more info with that update.

We also have better tools to debug hangs in the gameplay code with the same update or before that. Since the last hang indicated that it could be something else.

Hmmm - I’ll query this with our Engine Developers.

Your console logs would be appreciated. Please see: