KNOWN ISSUE: internal_error / Error Code: 2007

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.

Experimental branch 3 worked pretty well for me, not perfect but way better.

Will the experimental branch be included in the release version, still work or will there be a new one available ?

Good luck for your launch !

2 Likes

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. :slight_smile:

Thank you!

3 Likes

The experimental branch sadly didn’t fix anything for me, don’t want to be rude but the fact that this is an issue on launch is embarrassing, it seems like people were ignored for a month or so, then the devs decided to try and get a quick fix out for it ready for release. I paid money for a game that, as far as I’m concerned isn’t even remotely playable.

console-2022-11-29-14.35.48-67a1335e-7532-45ea-b897-2df54c41e122.log (19.4 KB)
console-2022-11-29-03.05.27-f05a20de-3139-43c1-9ec6-d32f07918d87.log (57.7 KB)

3 Likes

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

what about those of us that it didnt work for? are we only allowed to play for 20 seconds at a time? Should probably slap that on your game description so people dont expect to be able to play.

Im happy it worked for lots of people. Im happy that you guys were on the right track to getting it fixed. but your going to leave it half done? I know there was still a bunch of people who couldnt play still but bought your game and stuck with it in support of a fix. because the game at its core is great. because its even better than Vermintide and probably the best 40k game out there. Point is you need to fix it for everyone. not just some and then call it a fix.

errors 2003 & 2007 are now error 4001 but still in the same boat as before

I am still getting 2003. I can finally join the server without VPN, but after for about 15-30m I get the 2003 error DCing me from the game. Not as bad, can finally play and just rejoin from time to time.

I get ten or more disconnect error 2007 after launch. game is practically unplayable. I tried exp branch 7 late in beta and that “seemed” to help but I was unable to test further.
console-2022-11-30-18.10.59-28b40eb8-8a4d-4842-bfb4-3ddcfbef80da.log (675.5 KB)
Steam player.
No, you cannot have my steam id on an open channel.

If there’s a fix or info on error 4001 at any point, can someone post the i fo here, please? Could only play the prologue in both the beta and full game…

VPN never helped me either.

Thx

It seems to have fixed the issue for me, thank you all so much.

Hopefully you find out what’s causing the problems for other players.

1 Like

dc’s are starting to vex me greatly

super unplayable but I am on IPv6 which seems to be unsupported

Actually, it works for me now, seems these new servers fixed it for me. So currently its fixed FOR ME as I said.

1 Like

How are we here again after an experimental branch that actually worked on Steam? Is there a different build for the Game Pass version? The last experimental branch worked great and now with the GP version I’m back to where I was before the experimental branches from the beta. So frustrating.

PLEASE POST CRASHES AND ERRORS IN THE ‘TECHNICAL SUPPORT’ CATEGORY INSTEAD

We kindly ask that you complete the questions below. With this information, we can add it to our database for investigation.


Issue Description:
Once again receiving Error 2007 disconnects after selecting character in the Game Pass version.

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

  1. Literally just select my character and am hit with Error 2007 upon trying to load. I can do nothing else.

Mission Name (If Applicable):

Platform:
GamePass

Player ID:
rabbit221

Reproduction Rate:
Constant (100%)

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

There are no logs from 11/30 in the above directory, the only logs are from when I had the game on Steam.

console-2022-11-30-21.06.45-38c12527-c0ca-45ab-bd29-002050e50957.log (513.0 KB)

Steps to reproduce:
Try to join the Mourningstar.

Worth noting that the pre-release branch worked for me without getting this issue at all.

It’s also the same as 4008 and 9999 error codes.

1 Like

console-2022-11-30-21.49.05-f13a5685-4ec5-4d92-bb47-992bcfbe8ea1.log (199.0 KB)

This is funny … couldn’t connect a single time (always internal_error / error 2007 when I tried to load into the game from char select), so could not really play pre release beta at all but now after release I can suddenly enter with those chars. Well, hope it stays this way.
Only thing I had now is crashes with a new char on the first cutscene … that’s all very, very strange.

console-2022-11-30-23.45.30-5ac0549e-7207-41b8-b2b4-e34be86cedca.log (331.4 KB)
11/30/22 7:20 PM.

When trying to load into a mission the screen will remain black, then it will immediately boot me back to the operative select screen with Error Code 2007. Trying to reconnect does not work.

2 Likes