Warhammer: Vermintide 2 Dev Tracker

Hi @Terrimore,

Sorry for the delayed reply. I queried this internally with the development team and was waiting on responses

Unfortunately, this is a rather strange occurrence! The error codes printed in the logs aren’t reflective of what’s happening and the game engine is outputting a generic error, or no error. This means that we aren’t able to determine the root of the problem.

It may be worth both you and your friend trying our general connectivity solutions, to see if there’s any improvement:

Hi @Marnus,

Good question, and not to worry!

Your account progress (including beta rewards) is tied to your Steam ID. So, if you refund the game and pick it up again later, then as long as you redeem your new key on the same Steam account, you’ll be able to pick up where you left off

It’s unlikely, but if for any reason you have an issue with the beta rewards, then please reach out to me and I’ll ensure that you get them!

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!

Are you using a Bluetooth-connected headset?

I’m chasing for updates on this. In the mean time, I’ve created a new Topic for this particular error for release, which can be seen below:

FOLLOW-UP FROM:

Really promising improvements have been made in this area. We’re quite confident you will have a much better experience with our upcoming release patch.

I’m closing this and creating a new Topic for release which can be seen here:

FOLLOW-UP FROM:

We’ll investigate - thank you for the report!

Hi @Ghoward270,

I can appreciate the frustration if a disconnection happens mid-mission! We’re looking into connectivity issues and working to improve stability!

If this is a consistent issue for you, then I recommend trying potential solutions in this article, as you may see an improvement:

Servers are down for maintenance prior to launch. The incorrect error is being displayed.

We are aware of and looking in to the lost_connection and Error Code: 2003 (same error) 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 ...

We are aware of and looking in to the failed_joining_lobby and Error Code: 3001 (same error) 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. P...

We are aware of and looking in to an issue where Darktide does not always detect or utilise the GPU correctly.

In the case that Darktide is not detecting your dedicated GPU correctly, please see:

[PC] How to Resolve Darktide Using the Incorrect GPU

If you have run through the solutions linked above, or if your GPU is not being utilised correctly despite being detected, please share your experience in the Perf...

We are aware of an issue in which Darktide does not close properly.

In the mean time, you should be able to work around this by killing Darktide via the Task Manager.

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

If there’s no log then there’s likely some kind of permissions issue becaue teh launcher should still generate a log

Launch steam as an administrator and that should address permissions hopefully

We’re looking in to this. Thank you.

This is on our radar. You should no longer experience the crash on mission end.

We’re monitoring. Thank you for letting us know.

Please include the associated console log, and we’ll check it out. Thank you!