[2022] KNOWN ISSUE: internal_error / Error Code: 2007

Yep, it is the same as internal_error merging in to the other post to keep tabs.

I understand communication is lacking and I’ve pressed for an update. I’ve also stressed that this is our most concerning issue at current.

It’s no secret that we’re having a hard time with this.

There are some potential remedies in the upcoming patch but we don’t know exactly how this will interact with the internal_error (Error Code: 2007). Failing that, additional logging has been added to help our developers pin it down.

I promise, once I have more to share, I will - please believe me when I say I’m not purposely withholding any information.

IMPORTANT! We have released an experimental branch in Steam, which includes:

• POTENTIAL Backend Error FIX. We understand this hasn’t worked for everybody, and are continuing to investigate
• Additional logging for internal_error (Error Code: 2007)
• Additional logging for nonexisting_channel (Error Code: 2001)
• Additional logging for various GPU-related crashes, AND A POTENTIAL FIX!

Please note that the additional logging supports our investigation and will not necessarily solve the underlying issue for you at this time. We encourage anybody with these issues to use this branch, so we can continue work on addressing these issues as quickly as possible.

PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.

1. Open the Steam client
2. Right-click Darktide in your Steam library
3. Select ‘Properties’
4. Select ‘Betas’
5. Enter the password cTYPtKTsfMDsLHAV
6. Select ‘Check Code’
7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
8. Select experimental - Experimental Builds
9. Close the pop-up window
10. A 1.8GB download should now start
11. Play!
12. Post here to let us know the outcome

…I need to stress that the same people dropping content and activating Twitch Drops are not the same people who work on network or engine issues.

We should be able to retrieve the appropriate data without requesting console logs, but I’m asking for confirmation right now, for my own sanity!

Okay, so, I’ve confirmed that it is still helpful for us to see console logs.

Thank you!

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

Wow. Did anything change on your network or PC that could explain it suddenly working?

You won’t need to use the experimental branch in this case.

I’ve sent your logs to development too.

<3

I am merely the communication peasant, I have no say on anything deeper. Believe me, I am sick to death of this issue too! I am hounded for it on various channels without people realising I am no developer, but I’m working 12-16 hour days every day to pass relevant information on to development because I want these issues resolved as much as you do, honestly!

Thank you for the additional information.

Local servers would only be for solo play. Private lobbies (2-4 players) would still run on dedicated servers.

POTENTIAL FIX NOW LIVE on the experimental branch for internal_error ( Error Code: 2007)

PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.

1. Open the Steam client
2. Right-click Darktide in your Steam library
3. Select ‘Properties’
4. Select ‘Betas’
5. Enter the password cTYPtKTsfMDsLHAV
6. Select ‘Check Code’
7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
8. Select experimental - Experimental Builds
9. Close the pop-up window
10. A 44mb download should now start
11. Play!
12. Post here to let us know the outcome

It should auto-update. Try relaunching Steam

Scrap that. It’s broken - we’re reverting.

SECOND POTENTIAL FIX NOW LIVE on the experimental branch for internal_error (Error Code: 2007)

~~Already have the experimental branch selected? You might need to restart the Steam client for the download to initiate. ~~

### PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.

1. Open the Steam client
2. Right-click Darktide in your Steam library
3. Select ‘Properties’
4. Select ‘Betas’
5. Enter the password cTYPtKTsfMDsLHAV
6. Select ‘Check Code’
7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
9. Select experimental - Experimental Builds
10. Close the pop-up window
11. A +43mb download should now start
12. Play!
13. Post here to let us know the outcome

We’re reverting!

The latest build has been reverted due to the induced crashes.

No more new builds today, unfortunately. We’ve picked up some really valuable information, and appreciate all of you who have taken the time to try it out.

I don’t know if we’ll be pushing any new experimental builds tomorrow - I’ll keep you posted.

THIRD POTENTIAL FIX NOW LIVE on the experimental branch for players impacted by internal_error (Error Code: 2007).

Already have the experimental branch selected? You might need to restart the Steam client for the download to initiate.

PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.

1. Open the Steam client
2. Right-click Darktide in your Steam library
3. Select ‘Properties’
4. Select ‘Betas’
5. Enter the password cTYPtKTsfMDsLHAV
6. Select ‘Check Code’
7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
8. Select experimental - Experimental Builds
9. Close the pop-up window
10. A +43.4MB download should now start
11. Play!
12. Post here to let us know the outcome

This makes me so happy! Fingers crossed all around!

FOLLOW-UP FROM:

We are aware of and looking in to the internal_error and Error Code: 2007 (same error) being reported.

It should be noted that we do not support IPv6-only networks at this time.

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.

The experimental branch will mirror the release branch, and the release branch will contain everything experimental once had (minus the crashing, we hope…).

So you should be able to play as normal on either branch.

Thank you!

The rollout of new servers with launch should continue to mitigate the issue. Keep us posted.