Heroes,

Thanks for checking out this week’s developer post. We don’t have a huge deal to share this week. We’ve been thrilled with your reactions to the latest and last Chapter in the Curse of Drachenfels adventure for Vermintide 2, and hope that Nurgloth isn’t being too mean to the Quickplay PUB runs out there!

Given most of us are being told to stay inside right now and limit physical interactions with society, we have ...

Could you try briefly disabling any Anti-Virus on the PC, and see if it continues to crash on launch?

This is an error produced by our anti-cheat service, Easy Anti-Cheat.

I have queried this particular error with them in the past; please see their response below:

This error is usually triggered by these softwares: ByteFence, Reason Core Security, Webroot SecureAnywhere.
Only disabling it will not be enough, it is necessary to uninstall it, cold reboot the PC and repair the service.

Looking in to this now - will update as soon as possible.

Please see our update here: https://support.fatshark.se/hc/en-us/articles/360021232734--PC-How-to-resolve-Sign-In-Timeout-errors

Please see our update here: https://support.fatshark.se/hc/en-us/articles/360021232734--PC-How-to-resolve-Sign-In-Timeout-errors

Please contact your ISP, it may be due to network disruption or port blocking. Please see #7 here: https://support.fatshark.se/hc/en-us/articles/360021232734--PC-How-to-resolve-Sign-In-Timeout-errors

Thank you - it’s in our database now.

Heroes,

This is the new performance complaints post. We have archived the previous post to collate information from it.

Use this post to describe any performance-related issues you’re experiencing in Vermintide 2, such as FPS drops and stutters.

Please include the information below in your post:

• A description of your issue, including when it started
• Your PC’s specifications
• A recent console log*
• Your user_settings.config**

*Your console logs can be located here:

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

**Your user_settings.config can be located here:

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

For issues that are not per...

For Vermintide 2 - FAQ, Common Problems & Solutions, please see: https://support.fatshark.se/hc/en-us/sections/360002936593-Vermintide-2-Common-Questions-Problems-Solutions

For Vermintide 2: Winds of Magic - FAQ, Common Problems & Solutions, please see: https://support.fatshark.se/hc/en-us/sections/3...

For Vermintide 2 - FAQ, Common Problems & Solutions, please see: https://support.fatshark.se/hc/en-us/sections/360002936593-Vermintide-2-Common-Questions-Problems-Solutions

For Vermintide 2: Winds of Magic - FAQ, Common Problems & Solutions, please see: https://support.fatshark.se/hc/en-us/sections/3...

No, this has been a problem starting maybe about…three weeks ago?

Thank you for reporting this Exan, did this start with the latest patch?

Apologies for the overly-long title. Apparently the forum won’t let me use, “Crash on Startup Using DX12.”

I will crash sometimes (maybe about 75% of the time?) when starting up the game in official or modded when using DX12. If I switch to DX11, the problem resolves.

Attached you’ll find the log (this particular log is modded realm):

console-2020-03-25-21.03.38-90b9499d-3550-4106-a812-78f678f4d6f9.log (9.6 KB)

Current world events have increased the demand on ISPs and Steam, resulting in some network disruption yesterday. Try logging in now, as this should’ve resolved on it’s own.

There was some network disruption yesterday, likely due to current events increasing the demand on ISPs and Steam. This should have resolved on it’s own - see if it’s still occurring today.

Hello! Please see my response to your previous post:

We’ll continue the conversation there.

Please see: https://support.fatshark.se/hc/en-us/articles/360021232794--PC-How-to-resolve-Untrusted-System-File-errors

We are seeing an increase in these errors due to the increased demand on ISPs and Steam. It may well resolve on its own. Have you tried logging in today?

Gotta beat Old Haunts.