Thank you for reporting and apologies for the inconvenience, I’ve raised this particular crash with development.
Thank you for reporting and apologies for the inconvenience, I’ve raised this particular crash with development.
Sorry no, I have nothing new to recommend at this time.
Our developers aren’t using a Linux-based OS.
As Reshade was only recently updated, I’m sure Easy Anti-Cheat are in the process of whitelisting the latest update - it can take some time.
The beta is an entirely seperate app and will require additional space.
There may be a beta for console at a later date, as the console release comes after the PC release.
As I understand (and subject to change or alteration), the Beastmen can be found in the Helmgart levels (where it fits) should a player in the group (perhaps the host, this hasn’t been fully defined yet) own the expansion. They might not show up on thematic levels - such as Skittergate, Into The Nest and such.
The first expansion to Warhammer: Vermintide 2, Winds of Magic, will be coming out in August 2019!
Can’t wait for August?
Sign up on our website for your chance to participate in the Beta!
Read moreLooks like the Skip Intro mod resulted in the startup crash, so worth keeping in mind if it becomes a more persistent issue. I’ll assume it’s an unlucky one-off.
The other issue you’ve described is on our radar.
Thank you for reporting.
I’ve spoken with development who have confirmed this is working as intended. Gibbing has been disabled except for on critical hits due to performance reasons. However, there is a potentially related issue where if the host Gibs an enemy, clients cannot see nor will be able to Gib it themselves. This will be addressed in an upcoming patch. Hope this helps!
Thank you @Exanimia, we’ll do our best to make this right.
I’m delighted to hear that! Thank you.
Firstly let me express how appreciative we are of your support and I love hearing that your wife and sons are involved too.
We apologise profusely for what our console players have had to put up with - unfortunately there’s been a lot of roadblocks along the way and patching on the console is notoriously complicated in comparison to patching on the PC. I won’t bore you with the details!
Last patch we introduced some additional debugging code which has enabled us to pin down and address a whole bunch of issues. This is in QA at current and will hopefully be with you soon, and will undoubtedly improve your experience as a Vermintide 2 player on the PS4.
@tonyvermintide2 My colleague has responded to your query via the Support Portal. I’ll be closing this post.
Would you mind providing a recording?
Hey @omitten. We hear you bud, and we’re truly sorry. The last patch did include some debugging which has allowed us to track the cause of a whole bunch the crashes (which are often the cause of the disconnects as well) and a fix is in test now.
Assuming you’re on PC, please upload the most recent console log or paste the crash report in here. Thank you.
Also - I’d recommend that you lower your ‘Worker Thread’ count within the launcher’s ‘Settings’ menu down to 6, and disable any RAM overclocks if you have any.
This most recent crash appears to be an issue with our code, so I’ve popped that over to development. Apologies.
Unfortunately it’s still unclear as to what could be causing this. I’d recommend that you run through the solutions listed here.
We’re looking in to this, apologies for the inconvenience.