Warhammer: Vermintide 2

Warhammer: Vermintide 2 Dev Tracker




22 Nov

Comment
    Satoru on Forums - Thread - Direct

Your issue looks like your anti-virus is blocking EAC

Please add whitelisting for the Darktide directories in your anti-virus, or disable your anti-virus entirely

Comment

Summoning @Ratherdone for some of the more nerdy (no disrespect intended, I’m just a bit out of my depth!) questions (and Psyker questions!)

Comment

fiiiine

Autogun

  • Increase Autogun damage range from 40-100 to 60-120
  • dmg vs armored near-far mod from 60%-40% to 60%-50%
  • dmg vs berzerker near-far mod from 75%-50% to 100%-80%
  • dmg vs resistant near-far mod from 60%-50% to 100%-80%
  • dmg vs voild shield near-far mod from 60%-50% to 100%-80%

Autopistol

  • Increase Autopistol damage range from 30-70 to 40-80
  • dmg vs berzerker near-far mod from 90%-60% to 100%-60%
  • dmg vs resistant near-far mod from 50%-40% to 100%-60%
  • dmg vs voild shield near-far mod from 60%-40% to 100%-60%
Comment

As promised, we’re providing more detail in to the balance and tweaks outlined in the 1.0.7 Patch Notes

Dodge tweak pass to remove kite-ability and edge-case slowdowns

  • Removed linger time vs. ranged attacks (was 0.2s extra after dodge finished)
  • Tuned dodge curves to maintain a slower end of curve to disallow chain-dodge move speeds above sprinting (no kiting for you)
  • Limited speed mods to only scale speeds above normal movement speed to ensure low-rolled m...
Read more
Comment

It looks like your game files may be corrupted. Please try Verifying Game File Integrity.

  1. Right-click Darktide in your Steam library sidebar
  2. Select ‘Properties’
  3. Select the ‘Local Files’ tab
  4. Select the ‘Verify Integrity of Game Files’ button
  5. When complete, close and reopen Steam
Comment

This error should only occur temporarily after we release an update, while players are on different versions of the game. Do you have the latest update from today installed?

Comment

Not at all! We appreciate you sharing your findings, and what you’ve posted here may very well help others :grin: thank you!

Comment

We’re investigating. Thank you for the report!

Comment

Ah good spot! I’m glad you were able to identify the cause of the issue. Thank you for sharing your findings!

Comment

It may be worth running through some of the suggestions here:

Read more
Comment

Thanks @Agrargorn we’ll look out for this.

Does the flickering persist after restarting Darktide, or a PC restart?

Comment

We’re looking into it - thank you for the report!

Comment

@Toraz, thanks for the report! I’ve added this crash to our database - we’re on it!

@Flafi, yours appears to be a GPU hang. We’re working to resolve these - apologies for the inconvenience. You may find some solutions here helpful, if it’s a localised issue:

Read more
Post

Hi @Adanar, are you able to provide a console log and launcher log for us to take a look at also?

Post

Thanks for the added information. I’ve raised this in our database and we’ll investigate.

Post

We are aware of and investigating the nonexisting_channel and Error Code: 2001 (same error) being reported.

Please help us out by including the information listed below in your report:


Issue Description:

Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

  1. Play Chasm Logistratum as Ogryn (Skullbreaker)
  2. Attempt to pick up the second Grimoire
  3. Observe Backend Error

Platform:
[Steam/Microsoft Store]

Player ID:
[Steam ID/Steam Profile URL/GamerTag]

Approx. Time of Issue & Timezone:
[MM/DD/YYYY, 00:00AM/PM] [TIMEZONE]

Upload Console Log:

  1. Press the Windows key + R
  2. ...
Read more
Comment

Thank you! We’ll investigate.

Comment

It looks like you’re running into a Deadlock crash. It’s difficult to determine the cause from the logs alone unfortunately. I suspect it’s a localised issue and that something isn’t playing nicely.

Does the issue persist after a PC restart?