FatsharkJulia

FatsharkJulia



19 Aug

Comment

Unfortunately it’s not clear what could be causing this. Are any other errors displayed when this occurs?

To start with I’d recommend that you repair your anti-cheat service, Easy Anti-Cheat, using the EasyAntiCheat_Setup executable located here:

C:\Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\installers\EasyAntiCheat

Comment

Thank you. You appear to be experiencing a lot of Access Violations which, unfortunately, can occur for a variety of reasons. A common culprit is an interfering background application.

Please run through the solutions listed here.

Comment

Could you please switch to DirectX 11 within the launcher’s ‘Settings’ menu and see if the crashes persist?


18 Aug

Comment
  1. Press the Windows key + R
  2. Enter %appdata% and select the ‘OK’ button
  3. Navigate to AppData\Roaming\Fatshark\Vermintide 2
  4. Right-click user_settings.config and select ‘Properties’

Under ‘Attributes’, is the ‘Read-only’ checkbox selected?

If so, please deselect it and apply the changes.

Comment

I believe you may need to remove your AppData directory by:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark
  4. Delete the entire ‘Vermintide 2’ directory

Please be aware that by clearing your AppData, you may be prompted to re-run the prologue - none of your progress will be lost, as all progress is stored on our servers.

Comment

I believe you may need to remove your AppData directory by:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark
  4. Delete the entire ‘Vermintide 2’ directory

Please be aware that by clearing your AppData, you may be prompted to re-run the prologue - none of your progress will be lost, as all progress is stored on our servers.

Comment

For anybody experiencing Backend Error 1002, please reach out to us at http://fatshark.se/support.

Comment

For anybody experiencing Backend Error 1002, please reach out to us at http://fatshark.se/support.

Comment

All I can see is a GPU crash unfortunately, could you try performing a clean re-installation of your GPU drivers using the instructions here, if you haven’t already?

Comment

I know you don’t believe this is a FPS issue but could you see if there’s any improvement on a lower video quality?

Comment

Sorry to hear this. We’ll look in to it.

Comment

Please be sure to raise this and include your DxDiag here: FPS drops, stutters and your DXDiags

Our Engine Developers are monitoring the post.

Comment

Sounds like you’re accidentally playing on the ‘Modded’ realm, as opposed to the ‘Official’ realm. Your realm can be changed using the checkboxes above the ‘Play’ button within the launcher.

Comment

Please be sure to raise this and include your DxDiag here: FPS drops, stutters and your DXDiags

Our Engine Developers are monitoring the post.

Comment

Apologies for the delayed response. This crash has since been addressed, please let me know if you have any problems.

Comment

Apologies for the delayed response, I’ll ping this over to the developer that handles the Chroma integration.

Comment

Hmmm, I apologise but admittedly I’m not sure what to recommend here. I think the best option would be to reach out to Easy Anti-Cheat directly: https://www.easy.ac/en-us/support/game/contact/tech/

Comment

Sorry to hear this Verizal, should this occur again please include the crash report produced.

Comment

Is this still an issue for you? Could you upload a console log that corresponds with a session where this has occurred, please? Your console logs can be located using the instructions below:

  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
Comment

The Connection Timeout error is unfortunately often router or ISP-related. For debugging purposes, could you hook your PC up to a mobile data connection to see if the error persists?