Heroes,

Welcome to another Developer Update. As a studio this past week has been taxing beyond belief. Sending home around 100 people on short notice presents a unique set of challenges that we’ve never had to face until now.

The first challenge is one of ‘understanding’. Having the sharks understand why these changes are happening gives the process of shipping them home a head start and thankfully this wasn’t a problem....

Could you PM me yours and Tim’s Steam profile URLs, please?

Looks like the GPU is essentially disconnecting here, but we have seen other components (such as an overheating CPU) produce the same GPU-related error in the past. As this recently occurred after reinstalling on to the SSD, it may be worth performing some health checks on that.

Otherwise, please see: https://support.fatshark.se/hc/en-us/articles/360034654593--PC-How-to-resolve-GPU-crashes

Our Backend Engineer is looking in to this instead now.

He’s asked if you could potentially connect to a mobile hotspot (or any other connection for that matter) to see if the errors persist?

I appreciate this isn’t always an option.

Please see: https://support.fatshark.se/hc/en-us/articles/360021235014-Are-you-playing-from-Turkey-and-experiencing-Server-Errors-

A console log (not a crash report, confusing I know) should be produced for every session.

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Vermintide 2\console_logs

Nah, console logs please! Console logs are produced regardless of whether a crash occurs.

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Vermintide 2\console_logs

We’re looking in to this - but it would really help us out if you could upload the associated console logs.

We’re looking in to this - but it would really help us out if you could upload the associated console logs.

This will be resolved in patch 2.3.

Sorry, I see we must’ve missed your last post.

Could you please PM me your PSN ID? I can then pass this on to one of our Console Developers to look in to.

The year’s just starting, mate!

Unfortunately we appear to be in the midst of a connectivity hiccup - I’m looking in to it.

I’ll ask our QA department to check it out!

Hmmm! Timer begins within the Bell area, smash the chains up and drop down to where the Rat Ogre spawns but skip him - keep running, the achievement may not pop immediately.

Thank you for reporting, I’ve raised this in our database.

If a report has been acknowledged, it’s in our database and awaiting resolution.

There is no need to repost crashes that have already been acknowledged. Crashes are a high priority by default, and I cannot make development work any quicker.

Ya first we heard (haha?) Of it specifically mentioning running attacks. At least first I’ve heard.

I don’t think it’s a design choice at all. Most likely a bug, one that is more likely to get fixed now that this has been pinpointed?

No no haha, why is it that way? Kept this in mind during my games last night and seems to be true, just seems somewhat of a strange design choice.