Warhammer: Vermintide 2 Dev Tracker

I’ve queried Shimmer Strike with dual heavy attacks and received this response:

The attack has to kill a elite or special otherwise it’s removed - this is intended.
If you hit anything and it doesn’t kill, you will lose Stealth.

This is why Shade has these perks:

• Melee attacks out of stealth has 100% crit chance
• Charged Critical Backstabs always slays man-sized enemies. (i.e. not Monsters, Lords or Chaos Warriors)

This means you can always kill the elite if you land a Charged attack in their back, but it will also work as long as you one shot the Elites or Specials.

I have received the link and sent a request for access.

Sorry to hear this, I’ve added your report to our database for investigation. Thank you for letting us know.

It’s a code-related crash that occurs when a unit (which could be anything) does not “unload” correctly. Unfortunately there is no way to solve this from a player’s perspective, other than wait on us to patch it.

Gratz on the new rig! Nothing like the smell of new, fresh capacitors getting some juice through them!

Hotfix 4.6.3 (March 18):

• Fixed a crash that could occur when clients used emotes when a host ended a session

Hi @RichNess,

Could it possibly be a region lock issue with the stream?

Can you please try hooking into another channel.

Let me know how it goes!

Hi @RichNess,

Sorry to hear that!

So we can take a look, can you please provide your console log from a session that you’ve experienced the endless connecting?

To do so:

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Vermintide 2\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 the appropriate console log to us

If the log size is too large, you can upload it to a reputable host service (e.g. Google Drive) and link it here.

Thank you in advance!

This crash is on our radar - we’re on the case!

Sorry for the inconvenience.

scripts/managers/spawn/respawn_handler.lua:681: attempt to index local ‘respawn_data’ (a nil value)

We have a fix for this it won’t make it into today’s hotfix, but it should be coming in the one after that!

Hi @Kitten,

I’ve received the log! I’ll open an investigation in our database and we’ll monitor reports of lag spikes and see if there’s a correlation with poison.

Thank you!

It would be superb if you could upload it to Google Drive as mentioned by Rodo above, and then supply us with a link to it.

You could, alternatively, contact us via https://support.fatshark.se and attempt to upload it there.

The ‘system’ considered the posts to be spam as the same video link had been posted a couple of times, so it’s purely an automated mistake, nothing personal!

Lev then restored the posts by rejecting system’s elaborate claims.

If you haven’t already, please create a copy of the DLL, and place it somewhere memorable such as your desktop. Then, right-click it and select ‘Send to’ → ‘Compressed (zipped) folder’. Are you able to upload it as an email attachment then, with it being zipped?

We’re aiming to hotfix the current most common crash tomorrow, and if all goes to plan, to then hopefully hotfix further issues again early next week. Apologies for the inconvenience in the meantime!

Hi @Rodo

I’ve added this to our database for investigation. If you could provide your console log from this session that would be helpful!

To do so:

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Vermintide 2\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 the appropriate console log to us

If the log file size is too big, you can use a reputable hosting service (e.g. Google Drive) and link it here.

Thank you in advance!

Glad to hear you were able to resolve this

Sorry about that @conv

So we can take a look, please can you provide a crash report or your console log from the session this happened?

Hi @BullHorn,

The logs indicate a GPU-related crash. I recommend running through some potential solutions here:

Thanks for the report @BelgiasVT, we’re aware of this crash and on the case!

Apologies for any inconvenience.