10 days ago - FatsharkJulia - Direct link

We are aware of and looking in to the internal_errors being reported.

Please help us out by including the information listed below in your report:


Issue Description:

Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

  1. Play Chasm Logistratum as Ogryn (Skullbreaker)
  2. Attempt to pick up the second Grimoire
  3. Observe Backend Error

Platform:
[Steam/Microsoft Store]

Player ID:
[Steam ID/Steam Profile URL/GamerTag]

Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]

Upload Console Log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. Upload here

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

9 days ago - Satoru - Direct link

Note many mobile ISP block Steam due to its bandwidth usage. Do you have an alternate connection to test with?

9 days ago - FatsharkJulia - Direct link

Could everybody share the name of their ISP and the country they’re playing from, please?

9 days ago - FatsharkJulia - Direct link

Does anybody happen to know if they’re running IPv4 or IPv6?

9 days ago - FatsharkJulia - Direct link

I’ve said something similar in the Backend Error post, but I also want to make it known here that we are aware of how serious and widespread this issue is. Our developers are actively investigating.

I appreciate everybody wants information and as soon as I have it, I’ll share it with you.

We initially suspected this was isolated to those using IPv6 but that doesn’t seem to be the case based on your responses, and there is not much consistency between ISPs either.

Some players have been able to resolve their issues by changing their DNS or using a VPN (similarly to the Backend Error issue) but I appreciate using a VPN is not a viable long-term solution.