Warhammer: Vermintide 2 Dev Tracker

Hi @CasualKrieger,

Can you please provide us with a crash report or console log so we can take a look? Thank you!

Hi @Tricksterm,

Please can you post the full console log so we can take a look? Thank you!

Hi @GrubbyMcGee,

Sorry to hear that.

I’ve credited the Aquilas back to your balance for you

Hi @Bornnemissis,

Sorry to hear this. Could you please provide your console log from a session this issue occurs?

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Darktide\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!

Thank you for the report - we’re looking into this!

Apologies for the inconvenience.

Hi @GreenLegRyu,

One crash appears to be a code-related Access Violation crash, which I’ve added to our database for investigation.

The other two appear to be GPU hangs. Please see -

Hi @ConorOepkes,

Are you still encountering Error Code: 9999?

I believe this error is usually caused by a temporary local network issue and resolves itself. Let me know if this isn’t the case!

Hi @ADHDoug,

Sorry to hear that.

It is possible to purchase individual cosmetic items from a bundle. Though, I appreciate the purchase journey isn’t the clearest.

To do so, you need to press V to inspect the individual cosmetic piece, and from the Inspect screen it is then possible to purchase the item alone. Please be assured that we’re collecting feedback and aim to improve the shop UI/UX over time.

I’ve also credited the Aquilas spent in error back to your balance for you

Hi @Aedoky,

Sorry to hear this. Are you still missing the weapon skins?

If so, please can you drop a Support ticket to us, here:
https://support.fatshark.se/hc/en-us

If you can include your Steam profile URL / Gamertag and details of the weapon skin names then we can take a look at this for you.

Thanks!

@Abriel
Just sharing some developer feedback regarding this -

For users modifying the rtxgi_scale or any of the rt settings manually to the tech priest note in the community update for patch 1.0.14. The guide they are following isn’t really a good one as it will make some levels pitch black without turning off raytracing any more than turning it off in the menu does.

The early community guide to disable Raytracing is no longer valid since the 1.0.14 update.

The capping of the framerate is probably what is helping them by either rearranging the timings so that the issue doesn’t happen or with fewer frames they likely get fewer gpu hangs.

@Abriel, oh wow, nice one!

Thank you for the detailed write up here! I’ve shared this with the development team.

Hi @Forman,

Sorry to hear that - we’re actively monitoring connectivity reports and I’ll pass your report on to the team.

I appreciate you’ve already tried a few things, but it’s worth ensuring you’ve tried all of our potential solutions, here:

This is devolving into a thread of insults. Be constructive or move on.

Due to the ridiculous number of flags here, I think it’s run its course

Hi @Boarcas,

Looking at your logs it appears that your default GPU is set to Radeon HD 7800 Series.

This is unfortunately below the minimum requirements for Vermintide 2, and is likely resulting in your crashes as it cannot handle the demand.

Vermintide 2 Minimum Requirements:

• Requires a 64-bit processor and operating system
• OS: 64-bit Windows 7, 64-bit Windows 8 (8.1) or 64-bit Windows 10
• Processor: Intel Core i5-2300 @ 2.80 GHz / AMD FX-4350 @ 4.2 GHz
• Memory: 6 GB RAM
• Graphics: NVIDIA GeForce GTX 460 or AMD Radeon HD 5870
• DirectX: Version 11
• Network: Broadband Internet connection
...

Just to update here - we identified and resolved the issue.

We’re now looking into the best way to get missed rewards out to everyone. Please bear with us whilst we figure something out - we’re on it!

The queue has been checked and is now empty - please shout at me if anyone else becomes stuck. Thanks!

Hi @BoBo,

Sorry to hear that. It looks like you ran into the Deadlock crash again.

Have you tried the suggestions above already?

Thanks @tamalero. The data from these crashes show that you’re running into a GPU Hang, and not specifically an issue with your GPU being Out of Memory. We’re working to resolve generic GPU crashes as a top priority still and continuous improvements should be seen with each update!

Your crash error -
HRESULT: 2289696773 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DEVICE_HUNG

orvis25’s error -
HRESULT: 2147942414 = E_OUTOFMEMORY

It seems that the fix wasn’t effective I’ve had to reopen the issue for us to take another pass at it.

Apologies all that this is taking longer than we all want. Really hoping we can quash this one soon!

I’ll post any further updates here as soon as I know anything.