FatsharkLev

FatsharkLev



20 Jun

Comment

Hi @irrellephant,

Are you using any Mods? e.g. Loudout Manager Mod?

If so, perhaps disabling this may resolve the issue.

Comment

Hi @CallMeCC, thanks! I’ve passed this on to the Engine Devs also. Still waiting for someone to be available to pick this up and take a proper look. I’ll continue to chase this!


19 Jun

Comment

Hi @Mango,

Unfortunately there are known memory-related crashes on console for both Trail of Treachery and Tower of Treachery maps (You can find our Known Issues here). Regrettably, I don’t have an immediate solution to this, but please rest assured we’re working to resolve these crashes as soon as possible.

Apologies for the inconvenience in the meantime.

Comment

Hi @Edmondclemons,

Sorry to hear this. For the COULDNT_RESOLVE_HOST error, please try running through our connetivity solutions here:

Read more
Comment

Hi @Eirin_The_Medic,

Sorry to hear this.

I recommend to try two things, firstly please check out this article in case it’s related to players connecting or push-to-talk:

Read more
Comment

Glad to hear the issue resolved!


15 Jun

Comment

Hi @CallMeCC,

We still need to investigate further, but on an initial look one of our Engine Developers has said that there are some strange things in the log. User settings are being used by another process, and there is a constant “trigger level complete” spam.

Initial suspicion is that this is mod-related. Though I’m still waiting on another Engine Developer to pick this up and delve deeper into the issue.

I’ll keep you updated.

Comment

Ah okay :frowning: sorry to hear that!

Thanks for the console log - I’ve passed this on to our Engine Developers and have asked if someone can take a look. I can’t guarantee when someone will get to this, but I’ll be in touch when I have an update :slight_smile:

Comment

Hi @CallMeCC,

Just reviewing your previous post, and you mentioned by switching to DX 12 that the issue was resolved - to confirm, is this issue now occurring with DX 12 also?

If so, can you please provide us with your recent console logs so we can take a look?

Read more
Comment

No problem! I’m glad to hear the issue is resolved :slight_smile: happy rat bashing!


14 Jun

Comment

Hi @SleepyDrakken,

Sorry to hear this.

The issue here is with your save file - it’s very likely corrupted and causing the crashes. A data corruption message should show in this scenario, but it may not be for some reason. It’s something we’ll need to look into.

Importantly, do you play in Online mode or Offline mode?

If you play in Online mode, then you will be fine to delete your save file (this only includes settings and offline data) as your progress is stored on our servers.

If you play in Offline mode, then regrettably we would be unable to resolve this issue, and your progress would sadly be unrecoverable :frowning:...

Read more
Comment

Sorry to hear this @BtheLee

We haven’t received widespread connectivity reports, and as far as I’m aware no network changes have been made by us.

You may have had some unfortunate luck with hosts disconnecting or quitting - though 2 in 3 games seems quite excessive. I recommend running through our connectivity error solutions here:

Read more

12 Jun

Comment

Hi @checking27,

Sorry to hear this.

Your crashes logs are truncated and unfortunately due to being cut off are missing data to help with troubleshooting.

I can see an Exit Code produced (0xC0000409), which can possibly indicate an issue with corrupted files. So, a couple of things worth trying first:

  • Verify Integrity of Game Files
  1. Right-click Vermintide 2 in your Steam library sidebar
  2. Select ‘Properties’
  3. Select the ‘Local Files’ tab
  4. Select the ‘Verify the Integrity of Game Files’ button
  5. When complete, close and reopen Steam
  • Failing this, a clean re-installation may be helpful
    ...
Read more

09 Jun

Comment

@Geltern, oh that’s interesting!

The last update for EAC (v2305.2) was put live on 1st June, which included a single crash fix for games that don’t use DirectX 11 & 12. So, this update shouldn’t have changed anything for Vermintide 2.

Though perhaps their crash fix doesn’t get on with your specific anti-virus software.

Unfortunately I don’t have any access to any further detail than this - but it may be worth reaching out to EAC directly, here:
...

Read more
Comment

It’s genuinely very strange. I queried this with our console developers and was told there shouldn’t be any criteria needed to access Cinematics. We tested this internally for both Xbox and PS and could not reproduce the issue :thinking:

Our console developers are going to continue to look into this, although sadly I don’t have an immediate solution to this for you.

The only suggestion I can give for now would be to try a clean reinstallation of Vermintide 2, but I can’t guarantee if this will resolve the issue.

Please let me know how it goes if you try this!

Comment

No problem - I’m glad to hear that! :slight_smile: thank you both for the update.


08 Jun

Comment

Hm okay! :frowning: That’s interesting that Modded realm doesn’t work either.

So it may not be purely EAC-related. Though the exception to add for EAC I posted above - underneath the link.

If adding the exceptions above doesn’t work, can you please try reinstalling your Anti-Virus software?

Please let me know how it goes!


07 Jun

Comment

To add, which Anti-Virus software do you use?

I’ve noticed the Exit Code 0xFA718003 produced in your launcher log.

In the past, this error code has usually indicated a conflict with Anti-Virus software. Please see:

Read more
Comment

Hi @Geltern,

Sorry to hear this.

Are you able to launch the game successfully in Modded realm? (chosen from the launcher options)

I ask this, because Easy Anti-Cheat is only applied to Official realm, so this can help to determine if the issue is EAC-related here.

Also, are any other specific messages shown on screen when the crash occurs?

Thanks!

Comment

Thanks I’ve dropped you a message :slight_smile: