Warhammer: Vermintide 2 Dev Tracker

Thanks for confirming. We’ve received other similar reports from players based in Korea. We’re looking into it!

Apologies for the inconvenience in the mean time.

This is an issue we’re battling and it should be resolved in the coming weeks, apologies.

We’re working on both of these, apologies.

So, it’s my understanding this issue pertains to outdated AMD BIOS versions.

Is anybody able to pull up their BIOS version and let me know what it is, please?

You might be able to do this via ‘System Information’ → ‘System Summary’ → ‘BIOS Version/Date’

Thread locked on request of the OP.

Hi @winzer102h,

Which region are you playing from?

I’ve passed this information to our Console Development team. We’ll investigate - thank you for the report!

For anyone stuck, the queue has been cleared again!

haha, no problem, happens to the best of us!

We never stated we were delivering a patch at the end of last week. Our latest patch was 1.0.14. As mentioned in the community update:

In today’s update, we want to address a few questions from the community, as well as talk about what’s to come in our next community update on Wednesday, December 14.

Our biggest update yet will land next week and will include further improvements, additional weapons, fixes, private sessions, and more.

There are a number of connectivity issues we’re impacted by and we’re looking in to them all. I hope you’ll notice an improvement with subsequent updates.

We’ll look in to this. Thank you for letting us know.

Thank you for sharing, much appreciated!

It’s most likely there is a driver or hardware instability at play in this situation. Please see:

We’ll look in to this. Thank you for your report.

I’ve shared this with our developers. Thank you for your report.

I apologise but I’m not able to restore your rewards, as much as I wish I could. I’ll pass this on to development in case anything can be done to prevent such situations occurring. I appreciate this is a disappointment.

Thank you for sharing!

I believe the incorrect GPU is being detected here. Please see the solutions listed in the bullet points here: