Warhammer: Vermintide 2

Warhammer: Vermintide 2 Dev Tracker




18 Nov

Comment
    Satoru on Forums - Thread - Direct

Most anti-cheats don’t allow to be run in a VM. Its unlikely EAC will ever change that

Comment

Bit of a hiccup. The smart people are looking in to it!

Comment

Hi @ChaosMarine,

There a brief period of server disruption after the game update. This appears to be stabilising now :slight_smile:

Comment

D’oh, I’ve now renamed it as darktide_launcher in the FAQ!

Comment

Thank you! I’ve added the logs to our database to aid in our investigation. We’re on it!

Comment

It’s odd you would experience this 3h ago, long before we put a patch live! As that’s the only time you should really see this error.

Could you see if it occurs now that we have put a new patch live?

Comment

This will likely be the result of some bizarre buffer overflow issue. It sounds wild, but do you have another Ethernet cable you can try?

Post

We’re looking in to this, apologies.

Comment

Thank you for your report - we’re looking in to it.

Comment

Sorry about this. I can see the crash you’re experiencing is in our database and pending investigation.

Comment

I’ve sent this over to development. Thank you for your report.

Comment

As we release a new patch, you may observe the The strike team you are trying to join is running another version of the game. error even if you have the latest patch installed.

Even if only one member of the Strike Team is running an outdated version, the error will be shown to everybody . We are working on this.

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

Comment
    Satoru on Forums - Thread - Direct

I would go through the fixes to address issues with the launcher

Read more
Comment

I’ve raised this to our database. Thank you for your report!

Comment

This is a Steam hiccup. You might want to check out: How to Fix the Steam Disk Write Error

Comment

I’ve added this to our database. Could you also provide a console log, please? :slight_smile:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. Upload here
Comment

I’ve added this to the database. Thank you!

Post

We’re looking in to this. Thank you for your report!

Comment

This is on our radar. Thank you!