Hm okay. I wonder if there’s an issue with the installation after the recent updates. Can you please try a clean reinstallation of Vermintide 2? As this can often resolve more unusual/complex issues.
Read moreHm okay. I wonder if there’s an issue with the installation after the recent updates. Can you please try a clean reinstallation of Vermintide 2? As this can often resolve more unusual/complex issues.
Read moreThis crash is on our radar and should be resolved soon. Thanks for the report!
Ah Hmm. This is a little unusual then!
Are any specific errors shown on screen? I ask, as there are quite a few that relate to EAC. Here’s our support FAQ for EAC related errors, which I’m hoping if an error is visible to you one of these may cover!
Read moreThanks for the update! This definitely indicates an EAC-related issue.
Next, please try a ‘Selective Startup’, which can help determine if a background application is the culprit:
If the issue no longer persists after having performed the Selective Startup, you will need to re-enable each of your usual background applications one-by-one until the error reoccurs, to determine which is interfering with Easy Anti-Cheat.
Please let me know how this goes!
Would appreciate a bug report!
Sorry to hear this @M3rrick,
Based on the exit code 0xC0000005 in your logs, I suspect the issue is Easy Anti-Cheat related, and a possible conflict with your Anti-virus or Firewall.
Are you able to launch successfully in Modded realm? (chosen from the launcher options). I ask this, as EAC only applies to Official realm - so this can help us to determine if the issue is EAC-related.
If so, please try adding Anti-Virus and Firewall exceptions for both Vermintide 2 and Easy Anti-Cheat. Please see:
Read moreHi @Mushrum,
Unfortunately I don’t have an immediate solution for this, but please rest assured the crash rate for Chaos Wastes - especially for console - is very much on our radar!
This is something we’re aiming to improve in future updates.
We’re currently digging into this issue, and it’s likely going to require a fix in an upcoming hotfix. (It won’t be in the very next hotfix, but hopefully this will be resolved very soon).
Thank you for your patience.
Gotcha, thanks for the clarification! I’ll pass this on to our backend team and we’ll investigate.
I’ll let you know when I have any updates.
Hi @snf5trov,
Can I just confirm if you were attempting to apply the illusions while in the Versus Keep? or the usual Keep?
I ask, as there’s a known issue with the old deprecated UI allowing access to crafting menus while in the Versus Keep - which isn’t intended and will have issues.
Please let me know.
Originally posted by RATT: Patch Notes???https://store.steampowered.com/news/app/552500/view/4137190765277413967
Originally posted by WaykiWayki:Aye, known issue! Hotjoining results in a random hero. But joining a match when it begins should correctly let you pick your hero and career.Originally posted by Kishorn Commando:If you join mid game I'm pretty sure you're stuck with what you got.
you found out how to swap if you get put into a part-way-through game? i cant even work out if you can swap the heroes subclass let alone class itself ?
Hotfix 5.3.2 - 8th of March|
Fixes
- Fixed a number of miscellaneous crashes.
- Fixed an issue where the chat message target did not switch back correctly when changing between Adventure and Versus modes.
Read moreHotfix 5.3.1 - 7th of March
Tweaks
- Disabled quickplay play button for modded realm.
Fixes
- Fix crash when hotjoining while another pact sworn is very close to spawn
- Fixed crash when starting the game and getting a backend disconnect
- Fixed client crash when being hoisted at the same time as picking up a barrel
- Fixed music crash when joining a game
- Fixing crash when shooting with crossbows, javelins, or steam pistol while having a buff that makes it not consume ammo.
- Fixed crash when blocking with Kruber’s Spear & Shield variant Talabecland Waldguarder
- Fixed shutdown crash from leaving a lobby as h...
Patch notes for the hotfixes after this patch can be found in our Hotfix 5.3.X Megathread