Server Error message that happens within 1 minute following character selection

Warhammer: Vermintide 2 Technical Support
1

Issue Type (Required):

Error - SERVER ERROR

Issue Description (Required):

I’m mostly unable to play this game anymore due to a server error happens around 1 minute after clicking “Start Game”. I’m able to access the lobby browser, connect to games, load into games, open boxes, and pretty much everything else within this timeframe. I’m able to sit at the “Start Game” screen without issue.

This issue has started within the past 24 hours. Sometimes resolves itself.

I don’t use mods, but have tried the onslaught mod a few days ago.

This information may be relevant; Recently, I’ve been experiencing frequent disconnects from games once the patch that added weave illusions into the base game was released.

I’ve tried flushing, releasing, and renewing DNS, clearing Steam download cache, restarting router, reinstalling NIC driver, reinstalling Vermintide 2, changing upload bandwidth within VT2, enabling and disabling small packet network, port forwarding Steam P2P and other ports, and one or two more options I cannot recall. I have not made any changes to hardware/software immediately or recently that led to this issue.

Discord does not experience any connectivity/ping issues in congruence with VT2 connection drops.

I provided a log where I connected to a game and sent a few messages while waiting for the map to load before receiving the Server Error message.

[PC] Do You Use Mods? (Optional):

No, I don’t use mods

Reproduction Rate (Required):

Often (<75%)

Platform (Required):

Steam (PC)

Player ID (Optional):

[PC] Upload Console Log & vermintide2_launcher.log (Optional):

console-2024-06-13-03.23.37-3d3d503a-90d6-4371-a718-b2ef9476172b.log (264 KB)
vermintide2_launcher.log (60.7 KB)

2

Hi @applebottombeans,

I’ve spoken with one of our backend developers about this, and they’ve informed me that this error appears to be occurring due to bad timing with backend requests. Currently, when matchmaking begins other requests to the backend e.g. changing career/loadout are paused and resume when matchmaking finishes. However, these other requests can time out when processed due to the paused matchmaking time and result in this error.

To minimise this, please avoid doing any of the following while matchmaking (or a few seconds before):

  • Creating/Deleting loadouts
  • Changing active loadout
  • Changing talents, cosmetics, weapons/gear
  • Changing selected career

Hopefully we’ll have a fix sorted for this issue soon! Apologies for the inconvenience in the meantime.

1 Like
3

Hello FatsharkLev,

I appreciate the speedy response and I’ll keep this in mind. So far, your advice has helped and I thank you for that!

Beans

1 Like
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.