FatsharkLev

I queried Shimmer Strike with dual weapons 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’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.

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!

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.

Thanks @BelgiasVT,

I’ve passed this on internally - we’ll have more crash fixes coming soon!

Apologies for the inconvenience.

Hi @Kertious,

Sorry about that! This specific crash is on our radar, but the fix didn’t make it into the 4.6.2 hotfix. It should hopefully be addressed in the next one!

Apologies for the inconvenience in the meantime.

A new hotfix 4.6.2 is live which should address the common crashes - once you’ve downloaded the hotfix please let us know if you run into any further issues. Thanks!

A new hotfix 4.6.2 is live which should address the common crashes - once you’ve downloaded the hotfix please let us know if you run into any further issues. Thanks!

Hotfix 4.6.2 is now live which should address the most common crashes occurring. Please ensure you have the hotfix installed and let us know if you run into any further issues. Thank you!

I’ve queried this internally, and we believe all of the crashes here are linked to one notorious one that is very much on our radar. We’ve got a fix in the works - hoping to have this resolved soon!

Hi @Mfer_since98,

Please check you have the hotfix installed, otherwise please bear with us whilst we work to address the remaining crashes. Apologies for the inconvenience.