FatsharkLev

FatsharkLev



25 Mar

Comment

The Steam Overlay has to remain enabled for any in-game purchases to work. Can I just confirm that you tried making a purchase with the overlay enabled at the time?

Comment

Hi @CptoI3vious,

Could it be that the Steam Overlay is disabled?

Please check out:

Read more
Comment

Hi @Hazwoper,

So we can take a look at this, can you provide your console log from a session that the illusion has failed to apply?

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

Thank you in advance!


24 Mar

Comment

Hi @N1Lowbob,

Thanks for the report! Can you please also provide us with your console log from the session this crash occurred?

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

Thank you in advance!


23 Mar

Comment

This crash should be resolved in our next hotfix - apologies for the inconvenience!

Comment

This one is on our radar - we’re on it! Apologies for the inconvenience.


21 Mar

Comment

We’re aware of issues with Peacekeeper and Tech, No Mage challenges currently - we’re on the case!

Apologies for the inconvenience in the meantime.

Comment

This specific crash is on our radar and should be resolved in our next hotfix. Apologies for the inconvenience.

Comment

Thank you for the report @justaturtle - I’ve added this to our database for investigation. Apologies for the inconvenience.

Comment

This specific crash is on our radar and should hopefully be resolved soon. Apologies for the inconvenience.


20 Mar

Comment

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.

Comment

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.


18 Mar

Comment

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!

Comment

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!

Comment

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

Sorry for the inconvenience.

Comment

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

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

Comment

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!


17 Mar

Comment

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!

Comment

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!

Comment

Glad to hear you were able to resolve this :slight_smile: