Hi both,

Sorry about that - our recent patch introduced a matchmaking crash for PlayStation players that own the Back to Ubsersreik DLC.

We’ve released a hotfix this morning to address this issue. Please download the latest update which should resolve this

Heroes!

Thank you for your patience with some of the recent issues with the console patch. This patch was originally meant to help prepare our backend systems for the anniversary event in March, but caused some conflicts with certain DLCs, resulting in crashes for players.

Today we are releasing a hotfix for these conflicts on both console platforms. This patch solves conflicts with these DLCs on the following systems:

XBOX:

• Acolyte of Sea & Storm
• Absent Friends Collection

PLAYSTATION:

• Acolyte of Sea & Storm
• Back to Ubersreik

These hotfixes for Xbox and Playstation are 3.1GB and 1.5GB in size respectively.

Thank you again for your patience ...

We’ve collected data of all connectivity errors (timeouts etc.) and provided this to our Backend Service Provider. They are currently reviewing this, and we’re waiting to hear back from them.

Hopefully we’ll get some good news soon I’ll share any further updates as soon as I hear anything.

We’re aiming for submission of the hotfix today, and from there, it should be a fast cert turnaround. I’ll keep you all updated on where we are in this process.

yup, let us know what it is!

Heroes!

Playstation players will notice an update that is approximately 3.2 GB. This patch contains a handful of localization fixes for Russian players, but the bulk of it is preparing our backend systems for the upcoming anniversary event. More information on what this contains when we launch the anniversary March 8.

[ISSUE ACTIVE]

We are aware of an issue that is causing console players to crash with the latest patch. Please note that owning the following will result in a crash:

ON XBOX:
Acolyte of Sea & Storm
Absent Friends Collection

ON PLAYSTATION:
Acolyte of Sea & Storm
Back to Ubersreik

This issue has been resolved internally and a hotfix will be rolling out sh...

Heroes!

Make sure to join us for Fight the Tide’s shoutcast and coverage of the Onslaught Captains Series hosted by the community-run Onslaught Series!

The Captains Series is an event designed to help people try out modded and higher difficulties, help them grow by being paired with a coach from their region, welcome them to the modded community, and introduce them to the various Onslaught Series events and formats.

...

Hi @errant

Sorry to hear this.

Based on the information within your logs it appears that your GPU is crashing.

Please try running through our potential solutions for this, here:

@all, sorry for the delayed update - I’ve been waiting on news to share.

This Server Error issue remains a top priority for us for Vermintide 2.

Our Backend Developers have been able to dig into this, and we’ve identified that the issue isn’t something we can fix solely on our end, and that it runs further up the chain with our Backend Service Provider. We’ve reached out to them and will be working with them to hopefully resolve this as soon as possible.

I can completely understand frustrations as this is taking some time to resolve - we genuinely share the same frustrations

Please bear with us whilst we get to the bottom of this - thank you for your continued patience.

Heroes!

Xbox players will notice an update that is approximately 4.6 GB. This patch contains a handful of localization fixes for Russian players, but the bulk of it is preparing our backend systems for the upcoming anniversary event. More information on what this contains when we launch the anniversary March 8.

Noted, thanks so far all. I’ve passed this on and the investigation continues…

I’ll check back here regularly and keep feeding information to the clever people looking into this

Unfortunately nothing to update with currently

We’re trying to determine any common factors or trends -

@everyone

• Which region are you playing from?
• What ISP do you use?

Thanks!

@wufo @hollerbach

Just to update ya - this should be fixed now

Hi all,

Just an update - this is still very much under investigation.

We’ve indentified an issue, but not the root cause yet.

Console logs are greatly helpful in this case, so if anyone can provide a log after experiencing the ‘Server Error’ that would be much appreciated!