Stutters since Update

Issue Type (Required):

Performance

Issue Description (Required):

Everytime starting Vermintide 2 I get stutters comparable to loading shader stutter.
Friend has the same issue.

[PC] Do You Use Mods? (Optional):

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

Steam (PC)

3 Likes

Sorry to hear this @DeLaurec

Perhaps some of the solutions in this article may be of help:

Please let me know if you and your friend have any improvement.

1 Like

Not really - the game ran great before last patch. I didnt change a thing.
Ive already installed the newest gpu driver and my Hardware (M2 SSD, 6800xt, 5800x3d) is more than enough for this game.
The stuttering and in the same moment fps drop is gone after Ive played a while. But everytime I newly start it it stutters again.

1 Like

Ill try to explain the problem more precisely:
Everytime I newly start my Pc the game stutters (short lag, like it would load shaders for the first time) when sounds (eg: weapon swing, clash, patrol or special sounds and so on) are playing. It happens only the first time a new sound is played, so the game runs fine after a while. When I shut down or restart my Pc the stuttering/lag appears again.

1 Like

WAS MEANT FOR Darktide SORRY.

@DeLaurec, thanks for the clear explanation. Hm, I partly wonder if this is a temporary shader cache issue (similar happens with Darktide), which should usually go away after a few games. That said, as the issue seems to be returning when you restart the game or your PC that’s unusual.

Does the issue persist if you try switching Direct X versions?

Otherwise, it could be worth trying a clean reinstallation of Vermintide 2 (though please note custom settings, keybindings etc. would be deleted and need to be redone)

1 Like

Hi Lev, thanks for your message and help!

The stutter/lag is gone when the game runs with dx11. Only happens with dx12.
Is there an option to get rid of the stutter/lag with dx12?

Hi @DeLaurec,

No problem! Glad to hear that DX 11 isn’t stuttering :slight_smile:

It’s a shot in the dark, but you could try deleting your shader_cache.pip_lib file.

  1. Press Windows + R
  2. Enter %appdata% and select ‘OK’
  3. Navigate to: \AppData\Roaming\Fatshark\Vermintide 2
  4. Delete your shader_cache.pip_lib file
  5. Launch Vermintide 2 as normal with DX 12 (this will create a new .pip_lib file)

Please let me know how this goes.

1 Like

Hi Lev, thank you for your answer!

Ive found a shader_cache.pipe_lib file (think you meant that). But deleting it didnt help :confused:

Ah I see :frowning: did you try a clean reinstallation of Vermintide 2 before?

Otherwise, I’m admittedly a little stumped as you seem to have exhausted our usual solutions. If that’s the case I would recommend switching and using DX 11.

Hmm no I didnt try a clean reinstallation yet. Is there a possibility to keep my settings (game and mods) when I do it?

@DeLaurec if you back up your user_settings.config file and then replace it again afterwards this should keep your settings. I’m not 100% certain about mods.

I’d also recommend booting the game up and checking to see if the stutter persists with a clean config before re-adding your old one though.

You can find your user_settings.config file here:
\AppData\Roaming\Fatshark\Vermintide 2

Hi Lev, above the weekend ive tried different things:

  • clean reinstallation (didnt work with or without keeping settings)
  • updating gpu, chipset, audio drivers and bios
  • cleaning amd, Windows (directx) and V2 shader cache
  • reinstalling windows 10

Nothing helped.

The game seems to create (its the same kind of short lag I experience the first time when loading Shaders) new dx12 shader files everytime I reboot my PC. Not if I just close and reopen the game. Then there are no stutters.
This is happening since patch 5.4.0 - in the years before I never had any comparable problem.

DirectX11 is no option for me - the performance is significantly worse than DX12.
So do you have any other suggestion I may try please?

Thanks for the update. I’ve queried this with our engine developers and they also theorised that your library file may have become corrupted and isn’t saving correctly. Just to be sure, could you try deleting your shader_cache.pipe_lib file once more?

After deleting it, please launch Vermintide 2 and if the stutters occur again, please wait for these to stop, then exit the game, and check again on subsequent game launches to see if the issue persists.

The engine developer provided this explanation:

It’s also good to know that when deleting the shader_cache.pipe_lib it will stutter the first time played, as there is nothing cached. And it will stutter each time a new shader is encountered in game, so it may take a little while until everything is seen and cached.
So if the test was to just delete the file and start the game and experienced stutter, then that is to be expected. However, if the saving of the cache works as expected when shutting down the game, they shouldn’t experience the stutters next time they plays, unless they encounters new shaders that’s not already cached.

Otherwise, our engine developers have said that library file is only saved on shutdown, so they’d like to check if there’s any hidden shutdown crash occurring that might be preventing it from saving. Could you please do the following -

  1. Launch Vermintide 2 as usual
  2. Once loaded into the Keep, wait for the stuttering/lag to occur and stop
  3. Exit Vermintide 2
  4. Provide us with your console log from this session

Thanks!

Hi Lev, thanks for your help!

Here is the console log:

console-2024-04-23-14.55.28-4bd3268d-577c-464c-bf62-89f26b2b9d0d.log (187.7 KB)

For me it looks like something is wrong with my gpu driver?!

@DeLaurec thanks!

Hm, there are some references to Hardware-Accelerated GPU Scheduling not being enabled. You can enable this by the following:

  1. Open the Start menu
  2. Search for ‘Graphics Settings’
  3. Select ‘Change default graphics settings’
  4. Set ‘Hardware-accelerated GPU Scheduling’ to On

It may also be worth a clean reinstallation of your GPU drivers:

Lastly, I also noticed your log contains an error/crash caused by the Crosshair Kill Confirmation mod - so it could be worth disabling this mod.

Please let me know if there’s any improvement!

Hi Lev, Ive an AMD 6800xt - there is no “Hardware-accelerated GPU Scheduling” option to click on. I read something about the amd 6000 series dont have/need it.

Made a clean reinstallation of gpu drivers and disabled CKC mod.
Problem still occurs (game is loading already compiled shaders again).

Here is the log of first gamestart after cleaning gpu eg.:
console-2024-04-23-16.21.35-9832016c-2dda-455b-88ad-da02861b1209.log (254.1 KB)

Here the log of the second gamestart after I rebooted my Pc:
console-2024-04-23-16.26.27-b58e7403-e85d-481e-a612-f9913d242f43.log (185.1 KB)

@DeLaurec, ah I see! Okay, I’ve passed this information and on your logs on to some of our developers for review. Hopefully they can dig into them and provide some further suggestions!

Also to mention, when GPU drivers are updated this invalidates the shaders in the cache, so it’s expected for the game to stutter for a brief while again while the process is restarted. It will stutter as you encounter new shaders that aren’t cached but this should in theory stop happening, and the cache should save when you exit the game.

I’ll keep you updated on any responses I get from the developers, and please let me know if the stuttering does ease off in any subsequent game sessions if the cache does manage to save correctly.

Hi Lev, thank you!

Ok, Ill let you know.

@DeLaurec, our engine developers have taken a look, but have found no indication a hidden shutdown crash or error. They also mentioned that before by deleting your library file, the fact the file was recreated on shutdown does verify that the cache is being written. So that part is working, at least.

Next, could you please provide your launcher log, just so we can check the Exit Code given to see if this can give us any further clues.

Thanks!