FatsharkLev

Of course! Feel free to shoot me a message

Hi @RedBeardedGiant,

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

I’ve queried this with one of our Gameplay Developers, and it’s intended for weapons with shields to have a shorter range than the weapons alone.

Hi @Kitten,

What is your ‘Sound Quality’ and ‘Sound Channel Configuration’ setting under the Audio tab in Settings set to?

If you happen to catch a video of this occurring that would also be helpful to see.

Thank you!

Hi @ziyiqingyu,

Can you please provide us with your Steam profile URL (e.g. https://steamcommunity.com/id/FatsharkLev/) so we can take a look at this for you?

Thanks!

Thanks @Xadramare , we’ll take a look!

Hi @Kitten,

What is your upload speed? and do you have any issues if somebody else hosts?

Hi @Xadramare,

Can you please provide your console log from the session this issue 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!

Super, thank you! I’ll pass this on for investigation.

Hi @chapparal1973,

Sorry to hear that

So we can take a look at this, can you please provide your Steam Profile URL?
(e.g. https://steamcommunity.com/id/FatsharkLev/ )

Thank you!

Hi @itz_F3lix,

Sorry to hear that

I’m wondering if a background application could be interfering and resulting in your issue.

Could you please try performing a Selective Startup by:

1. Press the Windows key
2. Type ‘msconfig’ and select ‘System Configuration’
3. On the ‘General’ tab, select ‘Selective Startup’
4. Deselect ‘Load startup Items’
5. Reboot your PC
6. Launch Vermintide 2 as normal

If the error no longer persists after having performed the Selective Startup, you will need to re-enable each of your usual background applications one-by-one until the error reoccur...

Hi @Featherstomp.

The crash appears to be GPU-related. I can see that your GPU drivers are outdated, so I recommend to try installing the latest GPU drivers and see if the issue persists.

Thanks @cedric.d.schmidtke , I’ve added this information and the log to the entry in our database for investigation. Sorry for the inconvenience!

Hm, we have an existing bug in our database for this, but we had trouble reproducing the issue. Can you please provide your console log from a session that you try to cancel matchmaking as host? That way we can see if anything is going on under the hood or not.

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

Hi @cedric.d.schmidtke apologies for the slow response, this one slipped by!

Are you still having this issue?

Hi @Malignity, we’ll look out for this - though, the next time you encounter this can you please provide some specific details such as the level name and location description (a screenshot or video would be great!)

If you could also please provide your console log from the session that would be very 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

Thank you in advance!

Thank you @N1Lowbob - we’ll investigate!

I’ve passed this on for investigation - thank you!

As I mentioned before, if your friend can provide their console log too from a session this happens, that would be very helpful.

Hi @OenKrad,

Ohh that’s strange - we’ll keep an eye out for this!

If your friend runs into the issue again and they (or you on their behalf) can provide their console log from the session that would be great for us to take a look at.

Glad to hear that!