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.
Originally posted by 5G Brain Cancer: Maybe if they invested in real servers from the start, we would have a proper game by now. They are trying to polish this game to keep it alive, but it is severely lacking in the fundamentals.Servers or no servers, we use Steam Matchmaking to put people together.
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.
Originally posted by karn: "working with our test app with the exact same code."
Ahh how many times I have written this exact same line... ;)
We’re looking in to this, apologies for the inconvenience.
We’re looking in to this, apologies for the inconvenience.
devtrackers.gg