Warhammer: Vermintide 2 Dev Tracker

@SOULLESS, thanks again for your patience. The challenges for Zealot and Mercenary should now be completed and claimable for you.

We’re unsure why these kills weren’t tracking correctly, but we’ll look into it to see if there’s an underlying issue we need to fix.

Ah okay! I’ve passed this log on to our backend developer also.

Update to this! We’ve looked into it further, and found that the explosion doesn’t deal FF damage. However, the projectile itself does. This is intended!

I queried this and have been told that it should work for Trollhamer Torpedo. We’ll look into it!

Hi @SOULLESS,

Apologies - it’s been a busy period and I’m stil awaiting a response from our backend developers. I’ve given them another nudge and I hope they’ll be able to take a look at this soon.

Thank you for your patience.

As you can launch in Modded realm this indicates the issue is Easy Anti-Cheat related. As this only applies to Official realm.

Are any specific error messages displayed on screen?

In any case, I recommend to try the following first -
Ensure you have appropriate Anti-Virus and Firewall exceptions in place for both Vermintide 2 and Easy Anti-Cheat.

You’ll need to add the following exceptions:

• vermintide2.exe in \Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\binaries
• vermintide2_dx12.exe in \Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\binaries_dx12
• EasyAntiCheat.exe in \Program Files (x86)\EasyAntiCheat

If the issue persists, next please try a ‘Selective Startup’ which can help determine if a background application is conflicting. To do this, please:

1. Press the Windows...

Hi @llnOrmll,

Just to clarify, when you press ‘Play’ in Steam, is the launcher not opening correctly?

If so, please try our launcher solutions here:

Perfect, thanks!

I’ve requested for one of our backend developers to take a look at your console log and account.

I’ll be back in touch as soon as I have any updates!

No problem! You should be able to attach and upload the single log file from the relevant session to a comment here.

Ah okay! I can ask one of our backend developers to take a look in case something is awry.

Could you please provide me with your Steam profile URL (e.g. https://steamcommunity.com/id/FatsharkLev/) and your console log from the recent session that you defeated the 2 chaos spawns?

You should be able to identify the correct log via the time/date stamps in the filename. You can find your console logs 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\c...

Hmm, were you possibly downed when the Grudge Marked monsters were defeated?

Also, did you successfully complete the level?

Being downed, or not beating the level could cause the progress not to count.

I have responded to your support ticket. Speak there!

I’ve passed this on internally and we’ll investigate.

For now, to circumvent this you should still be able to change the setting in the options menu in the Keep.

Hello again, my name is Karl and I’m back to provide some commentary about our upcoming balance changes that were hinted at in the last dev blog.

These changes intend to target clear outliers in both strength and weakness and attempt to bring them in line with the rest of the game while keeping their intended design.

Hi @Yellowraven,

I recommend running through our data corruption solutions, here:

Hi @ZinStonehead,

Sorry to hear this.

For Adventure mode, if you QP into a map, you get QP rewards. It doesn’t matter if QP made you host a new lobby or if you join an in-progress Custom game lobby.

Though, if you QP into the Keep and then the host starts a Custom map this then won’t count as QP.

I believe Chaos Wastes should work in a similar way.

I’ve raised this with our QA team and we’ll check things out, as it’s possible that there may be an underlying bug.

Thank you for the report!

Hi @RZN_FatShart,

Sorry to hear this. Unfortunately, your logs are truncated and where they cut off abruptly (likely at the time of CTD) they are missing helpful information for troubleshooting.

It’s a shot in the dark, but can you please try the following and see if the crashing resolves?

• Perform a Selective Startup, which can help to identify if a background application is interfering

1. Press the Windows key
2. Type ‘msconfig’ and select ‘System Configuration’
3. On the ‘General’ tab, select ‘Selective Startup’
4. Deselect ‘Load Startup Items’
5. Reboot your PC
6. Launch as normal, and see if the issue persists

If the crashing no longer occurs, you can try reintroducing your programs one-by-one...

The second crash appears to still be under investigation since you last reported on it. Sorry about that! Be wary of those Twitch orbs for now.

The first crash, however, may be something you can remedy with your GPU. I suggest running through our steps in this article:

Hedge is no longer working at Fatshark, I’m afraid!

Regarding support for Linux (and the Steam deck) I’m afraid that our stance so far is that we have no official support and that we can’t afford to focus resources on adding that support. It’s possible that we revisit this stance in the future, but we can’t make any promises.

@Fatshark_Hedge Want to have a look at above?