Warhammer: Vermintide 2

Warhammer: Vermintide 2 Dev Tracker


1

Posts today

7

Posts in the last week

579

Posts total recorded

We had to pull our release manager in for the day.

I have passed your kind words on to her!

Patch is live, shout at me if you spot any new problems.

Afternoon!

Patch 3.0.0.4 is now live. This fixes a bunch of the broken spawn points in a selection of maps widely reported to have issues since 3.0.0.x.

Thanks for your patience whilst we figured that one out!

Pleased to hear that! Best of luck. :slight_smile:

You’re right in that the results may be skewed here, but I’m not sure about adding to the launcher - I’ll have a word with Hedge on that. I don’t have access to the win/lose statistics personally, I’d like to see what the results are here before escalating it internally. :slight_smile:

I’m hearing a lot of mixed opinions on the Convocation of Decay (Legend) end event being OP. Please let us know by answering the poll below.

Keep in mind that this doesn’t necessarily promise change, but it at least allows me to pass the results on to our Game Designer for review.

  • OP
  • Nah

0 voters

Our Release Manager has kindly returned, we’re working on building and QAing a new patch. :slight_smile:

It's not so much a celebration of a bunch of Sharks going on holiday, it's just a summery keep for a summery time of the year! It does coincide with a lot of us going on annual leave to make the most of the better weather whilst it's here!
It's a limitation in how the Steam store infrastructure works, as opposed to a mistake on our part. The cosmetic upgrade has to be tied to the base career in some capacity to reduce (or remove outright) cases where players purchase the upgrade on it's own for themselves. The only way to do this at present is to bundle it, and not give it it's own specific store front where it can be purchased in isolation. The result is that it can't be gifted, which is hugely unfortunate, but saves a totally more unpleasant wave of confusion from players who mistakingly purchase an upgrade to a product they do not own.

The last player to experience this issue had it as a result of a manual proxy they had set up. They needed to remove both http and https proxies.

Found another respawn bug. This happened in Empire in Flames. The slayer died past this point of no return, and respawned behind it.
The point of no return is after the first tome, before the first grim.

552500_20200707193642_11920×1080 1010 KB 552500_20200707193559_11920×1080 999 KB

Yesterday


Do you have a log file you can append?

Are you normally using a proxy for browsing?

The main problem is that our Release Manager is on vacation. Patching would likely mean having to bring her back to work, which would be unfortunate as she works so incredibly hard and deserves a break.

Another concern of ours is that patching now risks introducing new, potentially even worse issues.

Our Producer is working on seeing if anybody else is experienced and comfortable enough to wear the Release Manager crown for the day - I’ll keep you posted.

06 Jul


I hear you all. I have a call with our producer tomorrow to explore any potential options to speed this up.

It’s evident that respawn points are, unfortunately, very broken at the moment.

This issue seems to be most prevalent in Skittergate, Festering Ground, and Fort Brachsenbrücke but may be observed in other maps too.

Unfortunately, I have been informed that this is unlikely to be resolved until August due to resource availability - the Swedes like to vacation in July, you see… I appreciate this is a disappointment - I’m equally saddened that we weren’t able to resolve this prior to the vacationing period.

From this point onward, please report any issues relating to broken respawn points here, in the comments.

Thank you for your understanding and apologies for the inconvenience.

Please provide us with a crash report, which will allow us to look in to this.

To do this, after the crash occurs, a window should be displayed prompting you to enter what you were doing prior to the crash occurring. Once submitted, another window containing a long ‘GUID’ string and an option to ‘Copy to Clipboard’ should be displayed.

Please click the ‘Copy to Clipboard’ button and paste it in here. Thank you in advance.

To start with, please try lowering your ‘Worker Thread’ count within the launcher’s ‘Settings’ menu down to 6, and see if there’s any improvement.

Thank you for reporting, I’ve popped this into our database.

Have you tried the Verify the Integrity of Game Files option?

  1. Right-click Vermintide 2 in your Steam library sidebar
  2. Select ‘Properties’
  3. Select the ‘Local Files’ tab
  4. Select the ‘Verify the Integrity of Game Files’ button. This may take several minutes
  5. When complete, close and reopen Steam
  6. Launch Vermintide 2

The error being produced is DXGI_ERROR_DRIVER_INTERNAL_ERROR.

Please try a clean re-installation of your GPU drivers: https://support.fatshark.se/hc/en-us/articles/360021233554--PC-How-to-perform-a-clean-re-installation-of-your-NVIDIA-GPU-drivers