FatsharkLev

FatsharkLev



Comment

Hi @fangzan,

Sorry to hear this. The error is certainly EAC-related!

Please can you try repairing EAC:

  1. Navigate to: C:\Program Files\Steam\steamapps\common\Warhammer Vermintide 2\installers\EasyAntiCheat
  2. Run the EasyAntiCheat_Setup installer and proceed as instructed

Please let me know how this goes.

Comment

@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

Comment

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.

Comment

Glad to hear that this may have been resolved :crossed_fingers: Please let me know if your friend runs into any further issue.

Comment

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.


Yesterday

Comment

Hi @yunzesheng,

Sorry, could you please clarify the issue further?

Thanks!

Comment

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

Read more

17 Apr

Comment

I see! As you can play in Modded realm this does indicate an EAC-related issue, as EAC only applies to Official realm.

Are any specific error messages shown on screen? As this can help in narrowing down the appropriate solution.

If not, I would recommend to start with the following -

  • Repair Easy Anti-Cheat
  • Add Anti-Virus and Firewall exceptions for both Vermintide 2 and Easy Anti-Cheat
  • Perform a ‘Selective Startup’ which can help determine if a background application is the cause

Please see:

Read more

16 Apr

Comment

Sorry to hear this @Wyzilla

Based on the information in your launcher log, the issue is either GPU-related or to do with Easy Anti-Cheat, though it’s a little unclear as I only have access to this and no console log has been generated.

Off the bat, please try a clean reinstallation of your GPU drivers:

Read more
Comment

Sorry to hear this @DeLaurec

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

Read more

15 Apr

Comment

Hey @Lubbydubs,

I’ve been informed that this is intended, as Kruber is the main instigator for their journey - which is why he’s the one with a short briefing.

Comment

Hi @OenKrad,

We’ve had trouble reproducing this issue. If possible, could you provide a video of the issue if you can replicate it?

Also, if you could provide your console log from the session too, that would be super handy.

Read more
Comment

Hi @Cryoteer,

Sorry to hear this. I responded to your support ticket, but I’ll also drop a similar reply here.

It could be worth checking your microphone settings or disabling in-game voice chat. Please see:

Read more

12 Apr

Comment

@Revy, apologies! Our Backend Service Provider had some temporary disruption last night. This should have resolved now. Please let me know if the error persists though!

Comment

@Aenarion89, sorry to hear this.

Please run through our solutions to Error Code: 30005 (CreateFile Failed with 32.) here:

Read more
Comment

Apologies all. It appears our Backend Service Provider had another wobble last night :confused:

It should be resolved again now. Please let me know if this isn’t the case.


11 Apr

Comment

Glad to hear that!

Comment

Apologies, our Backend Service Provider experienced a temporary outage last night. Service should be back to normal now!