FatsharkLev

Hi @CaptEpic1,

Can you please try deleting the ‘Fatshark’ folder in AppData. (Please note this will reset your custom settings/keybindings which will need to be set up again)

1. Press the Windows Key + R
2. Type ‘%appdata%’ into the search field and press ‘Ok’
3. Locate and delete the ‘Fatshark’ folder
4. Launch Darktide (deleted files should redownload)

Let me know how this goes!

Nice one, we’ll check this out. Thanks!

Hi @Ice_Cold,

Could you please provide your console log from a session that this issue occurs? It’d be great for us to take a look at.

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

Thanks in advance!

It’s not intended or part of the condition.

It appears that damage somehow activated the Daemonhost here, but it’s very strange from the video!

We’ll keep an eye out for this. Thanks!

Hi @schmierwurscht,

New skins to purchase separately haven’t been added to the shop for the weapons - you should be able to apply the existing weapon skins to the new weapons.

e.g.

Is this the case?

Hi @PhdFiasco,

I replied to your Steam forum post, but I’ll copy the reply here also.

The logs show your installation is incomplete or corrupted. Please try Verifying Integrity of Game Files:

1. Right-click Vermintide 2 in your Steam library sidebar

2. Select ‘Properties’

3. Select the ‘Local Files’ tab

4. Select the ‘Verify Integrity of Game Files’ button

5. When complete, close and reopen Steam

If that doesn’t help, then I recommend running through other potential solutions, here:

@gpkgpk, sorry to hear that! I’ve passed your feedback directly on to the team and given the ticket in our database regarding this a nudge.

Thank you for your detailed report!

@Rieven
We’ve been able to reproduce this internally - so not to worry about the video/logs. Thanks for the report!

Hi @Rieven,

That isn’t intended behaviour. If possible, could you please provide a video recording of this happening?

Also, if you can provide your console log from the session that would be very useful for us to look at

Hi @MangoSeasons,

Is this occurring only for this weapon? or for other weapons?

Also, does this issue persist after restarting Darktide?

Ah ok thanks for the update and for the log! I’ve passed this on to the development team and we’ll investigate.

Thanks for the info. If the issue persists, could you please provide us with your console log and launcher log. This would be very helpful for us to look at.

Hi @yallia,

Sorry to hear this.

Do you use a VPN? If so, could you please try disabling it.

Does the issue persist after restarting your PC?

Also, what region are you playing from? and which ISP do you use?

Ah huzzah! Glad to hear that

The issue appears to be mod-related. Can you please try disabling mods and check again?

The backend requires an additional update still which will be happening soon. We’re on it

I suspect this crash is code-related and on us. I’ve raised it in our database and we’ll investigate. Thank you for the report!

Hi @Visulth,

I’ve added this to our database and we’ll investigate.

One thing I did notice from your logs is that your GPU drivers are a little behind currently, so I recommend giving those an update.

Oh, how bizarre! I’m glad that you were able to identify the culprit though - thank you for the update and for sharing your solution

Hi @sebelas,

Can you please try the following and see if there’s any difference:

• Verify Integrity of Game Files (this is a shot in the dark, just in case!)

1. Right-click Vermintide 2 in your Steam library sidebar
2. Select ‘Properties’
3. Select the ‘Local Files’ tab
4. Select the ‘Verify the Integrity of Game Files’ button
5. When complete, close and reopen Steam

• Disable background applications

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

• Check your user_settings.config isn’t set to ‘Read-only’
...