Warhammer: Vermintide 2

Warhammer: Vermintide 2 Dev Tracker




24 Nov

Comment

Not at this time, unfortunately!

Comment

We are currently investigating reports of players crashing on mission start.

Existing reports may be merged here, to help us keep track of the issues being reported.

Comment

As per our previous comms on the beta and what to expect

Working on, but not in the beta:

  • We are working on how best to implement an end-of-screen scoreboard that rewards the cooperative behaviors we aim for in Darktide’s gameplay
Post

We are aware of and looking in to issues where progression for the ‘Abhor the Mutant’, Cliffhanger’ and ‘Up Close and Personal’ Penances is not counting as expected.

This is also because the descriptions are potentially misleading. Bear with me whilst I investigate!

Existing reports may be merged here, to help us keep track of the issues being reported.

Comment

We’re on it. :+1:

Post

We are aware the descriptions for ‘Warp Battery’ and ‘Shocking Stuff’ Penances are misleading.

These Penances list Malice or above as the requirement, but progression is only counted when on Heresy or above.

Existing reports may be merged here, to help us keep track of the issues being reported.

Post

We are aware of a number of issues where enemies - commonly the Mutant - can yeet the player outside of the map boundary or in to otherwise unreachable areas.

Existing reports may be merged here, to help us keep track of the issues being reported.

Comment

Hi @BibletHUMB,

Level 24 unlocks the next Curio slot. At level 26 is when the next cutscene is shown.

Comment

Sorry to hear that. Your crash is GPU-related but there was likely some underlying vulnerability to start with, we operate in protected memory so it should never be possible to cause physical harm to your components.

Comment

Let us know if you’ve had any luck with the above. We’re also looking in to similar issues so I’ll add this to our internal report.

Comment

Thank you for the update. We’re looking in to it.

Comment

I believe this is related to something we’re currently looking in to, so I’ve raised this to our database.

Comment

This is mentioned in your logs, and may be of help:

Hardware-accelerated GPU scheduling in Windows OS needs to be enabled - please see https://devblogs.microsoft.com/directx/hardware-accelerated-gpu-scheduling/

Comment

They are moved to the GPU-related crashes post because they are GPU-related, and we need to at least attempt to keep it organised. We are running on empty working loooong hours days every day, so we don’t have the time to respond to each and every person experiencing the same GPU-related error.

I can also see this error in your logs, which may help you:

Hardware-accelerated GPU scheduling in Windows OS needs to be enabled - please see https://devblogs.microsoft.com/directx/hardware-accelerated-gpu-scheduling/

Comment

We’re looking in to it. Thank you!

Comment

Thank you for your report. We’re on the case!

Comment

It’s coming! Not out yet. :slight_smile:

Comment

Has this since resolved itself?

Comment

Hi @ATastyBeverage,

Sorry to hear this!

It appears that your game installation has a corrupted bundle file. Usually we’d recommend to Verify Integrity of Game Files, or try a clean game reinstallation.

In cases where the errors continue after trying this, we consider it to be persistent data corruption - which can, unfortunately, occur for a number of reasons.

We have a list of potential solutions which we’ve created based on what’s worked for players in the past, here:

Read more