I completely understand.
Our Console Developers are aware of the connectivity issues being reported, and are working on a patch.
Apologies for the inconvenience.
I completely understand.
Our Console Developers are aware of the connectivity issues being reported, and are working on a patch.
Apologies for the inconvenience.
Ok so, you don’t need to worry about the eac_launcher executable. Let’s take that out of the equation and ignore any errors produced by that.
Let’s start clean by:
Then, please launch Vermintide 2 and screenshot any errors displayed.
This appears to be caused by one of your UI mods.
It looks like you were eventually able to log in last night, is that right?
We’ll check it out!
After rebooting the PC, and without closing Vermintide 2, can you play uninterrupted? But as soon as you close and subsequently re-launch Vermintide 2, the error re-occurs?
I know you’ve mentioned you’re not using BullGuard, but I’m interested to know - which Anti-Virus are you using?
Just to add to Smoker’s comment above, I’d recommend having a look at this article: https://support.fatshark.se/hc/en-us/articles/360038965013--PC-PC-crashing-losing-responsiveness-or-Blue-Screening-BSOD-
Pop me a PM and we can sort that out for you.
It’s my understanding that this is as expected. I did raise this internally previously and was informed that it was ‘Working as Designed’.
Pop me a PM and we can sort that out for you.
Could you please upload the console log associated with this session?:
Timestamps within the log names should help identify which is needed.
Thank you!
I must ask - have you tried re-launching Vermintide 2?
This appears to be unrelated to the previous crashes, try lowering your ‘Worker Thread’ count within the launcher’s ‘Settings’ menu down to 6 and see if there’s any improvement.
Apologies for the delayed response. Would you be able to provide several additional console logs, please? (Assuming this is still an issue for you)
Sorry about your crashes - I’ve passed your console logs on to our Backend Engineer for review.
We’re working on it, I’ll see if we can speed it up.
You’re very welcome, I’m pleased to hear that!
This appears to be a memory-related crash.
Could you please ensure your ‘Virtual Memory’ is set to ‘Automatically manage paging file size for all drives’ by:
Any particular Difficulty you’ve noticed this on?