Warhammer: Vermintide 2

Warhammer: Vermintide 2 Dev Tracker




19 Nov

Comment
    Satoru on Forums - Thread - Direct

Can you please upload your console logs and launcher logs as well please.

Comment

We’ll keep an eye out for this - thank you for the report!

Comment

We’ll investigate - thank you for the detailed report!

Comment

Hi @Arkuzian,

Are you able to resolve this crash by 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 the Integrity of Game Files’ button
  5. When complete, close and reopen Steam
Post

Can anyone test if the Penance progresses correctly when attempted at difficulty 4 (one above Malice)? Could be related to an issue affecting another Penance.

Comment

Hi @TerriLou,

We’ll need a crash report or console log to take a look this please!

Read more
Post

We are aware of and investigating an issue where some players are not able to sign in correctly, and are stuck in Queue Position 1. Existing reports may be merged here, to help us keep track of the issues being reported.

Comment

We’re investigating - apologies for the inconvenience!

Comment

You’re running into a Deadlock type crash each time now. Which we’re unable to troubleshoot from crash data alone unfortunately. Usually, we suggest our general crash solutions in these cases and some trial and error to determine the cause. My hunch is that lowering your Worker Threads may have shifted one issue to another.

Apologies for any inconvenience, and thank you for your patience and support whilst we iron these early issues out!

Comment

Unfortunately, with a Deadlock crash, it’ll require a little trial and error, as we can’t troubleshoot it from the crash data alone.

Glad to hear that some improvement has been made, and fingers crossed you can identify the underlying cause!

Comment

Could you please post a console log of the crash, as well as your user_settings.config file? These may be found in AppData\Roaming\Fatshark\Darktide

Edit: Also, when you get a crash, you should be able to copy the crash message to clip board. Please paste it here when you can.


18 Nov

Comment

@carloseli0280, should be fixed for you now!

Comment

Hi @NoroelleSaeth,

Based on the information within your logs, it appears that you are encountering a GPU-related crash.

We’re working with our hardware partners to identify and solve underlying issues. However, it’s possible that these crashes may be the result of a localised driver-related issue and the like.

You can find information on how to solve localised GPU crashes here:

Read more
Comment

I’m merely the communicator, nothing will change if I head to bed. The smart people are still working. :wink:

They are also working on the current downtime as we speak.

Comment

Servers are stabilising after a second downtime within the space of a couple of hours, hang in there.

Comment

We’re battling some (new) downtime at the moment - please check back in shortly!

Comment
    Satoru on Forums - Thread - Direct

Note that task manager isnt a great tool to measure GPU utilization. It would be better if you used a more widely used overlay such as the Afterburner overlay which tends to give more accurate results. Alternatively you can use HWmonitor

For example here is a screenshot of me running the Hitman3 benchmark which is obliterating my GTX1080. But windows GPU utilizaiton is extremely low. HWMonitor more accurately shows the GPU usage.

Screenshot 2022-11-18 1627351339×767 124 KB

Comment

I’ve said something similar in the Backend Error post, but I also want to make it known here that we are aware of how serious and widespread this issue is. Our developers are actively investigating.

I appreciate everybody wants information and as soon as I have it, I’ll share it with you.

We initially suspected this was isolated to those using IPv6 but that doesn’t seem to be the case based on your responses, and there is not much consistency between ISPs either.

Some players have been able to resolve their issues by changing their DNS or using a VPN (similarly to the Backend Error issue) but I appreciate using a VPN is not a viable long-term solution.