FatsharkLev

I hear you! Don’t get me wrong, we won’t just look away and I’ve passed all of this info on to our developers to discuss and investigate. I can’t speak to sanctioned mod decisions, but if the issue requires a code fix our end then we’ll do it.

Ahhh. I believe this is something that would need to be solved by the mod author. I recommend communicating with the author via the mods Steam Workshop page.

We do have a ticket logged in our database though, which needs a discussion. So, I’ll update it with the info provided here, just in case anything needs to happen our end.

@Wulrik, do you use the Scoreboard Tweaks mod?

Could you please provide any details of what exactly is misrepresented and incorrect in the Chaos Wastes scoreboard?

Hi @fantcehr,

Oh, strange! One solution you could try is to delete your config file, and when you next restart the game it will create a new one. Please be aware though, that by doing so, you will lose all of your settings and keybindings etc.

I’ve nudged and updated this issue in our database - hopefully it’ll gain traction soon.

@Faolan Our Developers have taken another sweep and the amulet crash should now be fixed

@Faolan Ah right when you crash are you directed to the Xbox dashboard or to the game Start Menu?

Also, is any error popup shown? If so, what does it say?

@Faolan This should now be fixed

Hi @Faolan,

I can see an error is occurring in the backend, so I’ve asked a Backend Developer to take a look at this for you. I’ll update you when I hear back.

Sorry for the inconvenience.

Hi @McLovinMcCheese,

We’ve not received any recent widespread reports of PS4 matchmaking issues, so I’m inclined to say this could be network-related.

I recommend running through some possible solutions here:

Unfortunately with a GPU so below the minimum requirements we are somewhat limited in the support we can provide. Though, I recommend running through possible solutions here:

Hi @Ruper1407,

That is… rather strange. If possible, could you please provide a console log from a session that you try to start this specific mission and encounter this behaviour? It would be very useful for us to look at.

You can locate your console logs via the following:

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 @Frimaire

I can see from your log that your GPU’s dectected are Intel(R) UHD Graphics 620 and Microsoft Basic Render Driver which are below minimum requirements, and consequently resulting in crashing as they cannot handle the demand.

Do you have another GPU that is not being detected?

Hi @Lutheren,

It looks like the ‘Crosshair Kill Confirmation’ mod could be the cause here. Could you try disabling this?

Hi @Five,

Sorry to hear that. If possible, so we can take a look under the hood, could you please provide your console logs and crash dump files from this session?

You can locate your console logs via the following:

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

Your crash dump files can be found within the same parent directory:
AppData\Roaming\Fatshark\Vermintide 2\crash_dumps

Thanks in advance ...

Hi @SgtSmith95,

Sorry to hear that. We’re currently investigating a known issue with daily spikes of backend errors occuring between 12am - 1am BST. We hope to have this resolved as soon as possible.

I’ve also asked one of our Backend Developers to take a look at your logs, in case anything else is at play.

Hi @hollerbach, I don’t have any details off the bat, but I’ve added this to our database so we can take a better look.

If you could also provide your console log from this session it would be very helpful.

You can locate your console logs via the following:

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!

@Gorius1990, we’ve received quite a few reports of players having some trouble since the latest NVIDIA GPU driver release. Could you try rolling back to an older driver version?
https://www.nvidia.co.uk/Download/index.aspx?lang=en-uk

Hi @dedalo944,

Sorry to hear that. I can see you’re encountering an Access Violation crash and have a Ryzen 5 CPU, if you haven’t already I recommend lowering your ‘Worker Threads’ count. Please check out:

Hi @Struhadlo, I’ve responded to your support ticket.