FatsharkLev

Hi @Max93,

Could you please provide a crash report or console log from a session this issue occurred so we can take a look?

Hmm, we’re having some difficulty reproducing this our end.

Could you please launch the game using the bypass launcher workaround, attempt to connect to a game/friend and then provide us with your console log from the session? This would let us see what’s happening under the hood and could really help

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

Thanks in advance!

Hm okay. It’s possible for that software to have been added to your startup programs.

Next train of thought… are you currently using any mods? If so, can you try disabling them and see if the issue persists?

This is a known crash. We have a fix cookin’, sorry for any inconvenience in the meantime!

Sorry about that - we’re on it!

Hmm. Could you try repeating the Launcher Workaround steps again?

Using the bypass launcher workaround shouldn’t effect being to play with friends - they are on the same versions.

1. Right-click Vermintide 2 in your Steam library
2. Select ‘Properties’
3. Select the ‘Betas’ tab
4. In the dropdown, select ‘Temporary Launcher Workaround’
5. Restart Steam
6. Launch Vermintide 2
7. Select the ‘Bypass Launcher’ option
8. Click ‘Play’

Hm okay. I wonder if perhaps a background application is interfering.

Could you try performing a Selective Startup. This can be performed 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

I’ve added this to our database for investigation. Thank you for the report!

The log points towards a GPU-related issue again unfortunately. As your entire PC is becoming unresponsive then it could suggest that the problem may run deeper on a system level.

Please try running through potential solutions here:

Hi @TeddySpaghetti,

We’ll be releasing new launcher updates soon, and moving away from CefSharp which has caused a few hiccups. In the meantime, I believe you should be able to play by using the launcher workaround. You can check out how to do this here:

Hm, it seems you ran into a Deadlock crash which are a little notorious.

Could you try disabling any mods and see if the crashes persist?

Huzzah! glad to hear that. Happy rat-slaying!

I suspect this crash may be mod-related. Could you try disabling them if you run into this crash error again?

I’ve added the minor bug to our database - thanks!

Ah, so this one is a known issue - but the fix didn’t make it into our recent hotfix. I’m pushing for a second hotfix to address this as soon as possible, though can’t make any promises of when just yet. Apologies for any inconvenience in the meantime

Hi @chryzes,

I believe it could be a possible GPU-related issue. I recommend running through potential solutions here:

The first crash appears to have been caused by the Crosshair Kill Confirmation mod. I’d try disabling this.

The recent update hadn’t been put on the Launcher Beta, however we caught this and fixed it yesterday - so it’s possible this could be why.

Unfortunately the fix for this specific crash did not make it into the hotfix

I’m chasing this internally and really pushing for this fix to be released as soon as possible. I’m very sorry for the inconvenience this one is causing in the meantime.

Thanks for the log! I’ve added it to the report in our database.

Glad you could resolve the issue!

It’ll be some time next week at the soonest. I’ll discuss with the developer handling launcher improvements on Monday.

Hi @Arcter,

Sorry about that! So we can take a look at this, could you please provide your console log from the session this happened?

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!