Warhammer: Vermintide 2 Dev Tracker

Hey UndyingArmy,

Thanks for the report and sorry about this frustrating issue.

If possible, could you pinpoint any particular areas or spots in each map where this tends to happen? There is a possibility that these spawns are location based - if that is the case then they will be far easier to fix if we know where they happen.

Thank you and we apologise again for the inconvenience.

Best,
Hanna

I think there has been a mistake in the patch note description, as the handgun uses the same damage profile on aimed and unaimed shots, so the damage increase vs armour has been bumped from 1.0 to 1.2 on both attacks.
The shots not piercing shields however was a bug and has been fixed internally. Will be in a patch soon.

We have a process. It won’t be immediate but it will sanitise.

There was a very brief time where the backend was throwing up, things look ok at the moment

Yeah that’s a known cheating group. There’s only 120 weaves to my knowledge.

Weird one, thanks for letting us know. We’ll check it out.

We have a fix coming for this.

You can go in to your user settings file:

1. Press Win & R
2. Type ‘%appdata%’ (minus the ') in to the input and click OK
3. Open the ‘Fatshark’ folder
4. Open the ‘Vermintide 2’ folder
5. Open the ‘user_settings.config’ file in notepad or similar
6. add the line:

deadlock_timeout = 60

to the top. This should hopefully give the game more time before crashing should something be taking longer than usual for some reason.

Did it happen just the once?

Could you try the steps in this article?

This one?

We’re in talks with our Anti-Cheat provider, sorry we have no workarounds at current. We appreciate this isn’t ideal and hope to have an answer or solution for you soon.

If you could provide a console log for a session in which this happens it would be super handy for us to use in debugging.

C:\Users\YOURNAME\AppData\Roaming\Fatshark\Vermintide 2\console_logs

Could you try the steps outlined in this article?

We’re in talks with our Anti-Cheat provider, sorry we have no workarounds at current. We appreciate this sucks.

If you are able to grab any footage of this it would be super useful (same for anyone else who experiences this and might be reading!)

Smoker is largely right, but I too am not sure if Kruber’s behaviour is expected, so this is both being raised to design and not a bug at the same time. A true paradox of tags.