Warhammer: Darktide

Warhammer: Darktide Dev Tracker




23 Nov

Comment

Details on how to provide a crash report or console logs are supplied in the link. Sometimes, a crash report isn’t produced, and that’s where the console logs come in handy.

Read more
Comment
    Axloss on Forums - Thread - Direct

Sadly I can’t answer that but it’s worth a try. But in this case I would say that any driver that nvidia experiance gives you should be fine.

What’s happening in your case (what we could see before atleast) was that bink crashed when generating d3d12 shaders, these shaders are inbuilt in the exe and same for all users meaning that I expect same behaviour for all users unless something is wrong on the user side.

Since this code is likely not HW related but perhaps more linked to your OS a driver update might not help here.

Also pretty sure all of the crashes above has all been in d3d12 dlls

> dxilconv.dll!00007ff80f9a09c8() Unknown
dxilconv.dll!00007ff80f9bb74e() Unknown
dxilconv.dll!00007ff80f9b80e1() Unknown
dxilconv.dll!00007ff80f9918db() Unknown

m...

Read more
Comment
    Axloss on Forums - Thread - Direct

@Seb_Cz just because it’s after shader cache doesnt mean it’s the same issue. We always launch the shader cache first so that’s what ppl remember.

In many cases shader cache succeded and we can clearly see in the crash that it’s the game process that failed. They are 2 seperate processes so in theory we should be fine running the game regardless of shader cache status.


22 Nov

Comment

Could you reach out to us at https://fatshark.se/support instead please? We’ll try to help.

Comment

I would need the purchase to be made within the past 30 days, unfortunately.

I can see the purchase was made on the 5th of October.


21 Nov

Post
    /u/ on Steam - Thread - Direct
A lil somethin somethin: You can find the details for this event on the announcement page here.
Comment

I’ve raised this to our database for investigation. Thank you for letting me know.

Comment

When there are mods enabled it can muddy the crash data and make it particularly hard to work with - we don’t do it out of spite. :slight_smile:

I can see in the second console log there are no mods, which is super - using that I’ve been able to look up the crash and I can see it’s already in our database and awaiting resolution.

Comment

@Ophion I’ve been informed that you should be able to work around this by doing the following -

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 ...
Read more
Comment

Apologies for the wait @Ophion, I’ve chased this up and can see that we have a fix internally which is currently in code review. Once this passes review this should hopefully then make it into our next update.

Thank you for your patience.

Post

We are aware of an issue that sometimes causes Penance rewards (cosmetics) to not unlock accordingly.

Sometimes, the connection to our servers simply needs to be re-established.

Please try completing another mission, and the reward should unlock as expected.


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


20 Nov

Comment

I’ve shared these with our Backend Engineer. Thank you!

Comment

It doesn’t seem like there was any Aquilas on the account at any point in time. I should add that the Aquila bonus is for owners of the Imperial Edition - the Pre-Order bonus instead includes a Portrait Frame and Weapon Trinket.

Comment

As this is a persistent issue for you, I recommend looking here. We see this problem often when a RAM issue is involved, or if you’re running inconsistent RAM speeds:

Read more
Comment

Am I right in saying you’ve tried everything here already?:

Read more
Comment

Thank you all for your contributions above! @SSL-Elite159, outside of converting the drive, your C: drive may be a better candidate for Darktide.

Comment

Sorry to hear that. You should be able to work around this by:

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 conseque...

Read more
Comment

I think this was resolved in our most recent hotfix, released earlier in the day. Could you try playing now?

Edit: If the hotfix hasn’t helped, you should be able to work around this by:

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
... Read more