I recently started playing chaos wastes again and it also happens with the skulking sorcerer specials too.
Hopefully the next patch fixes this problem which i assume will be the new necromancer class? Its unacceptable on so many different levels when game breaking nonsense like this is going on for over 4 1/2 months at that point just because of how much it baits a player into doing unnecessary things when the threat of a special does not exist because it has already been killed.
Hm, so this issue hasn’t been widely reported and we’ve been unsuccessful in reproducing it so far.
If you could capture a video the next time you encounter this, and provide your console log from the session it happens that would be very useful for us to see.
Thanks in advance!
Alright when i play next i will record it and send it to you somehow because it happens almost every single time i play a game multiple times.
Hello lev im about to send you a video and console log of the bug happening with some extra info when its finished uploading to my google drive.
maybe i should start reporting when i see this lol. they’re probably not seeing us report it because it happens in game fairly often and it’s only a minor inconvenience that you can ignore once you leave the immediate area. It’s also kinda hard to say when it happens but I do see it at least once during my play sessions
We’ve been unable to reproduce this internally. Our developer investigating this has asked if you could please try the following -
Then check to see if the issue persists.
If so, can you please provide more specifics e.g. does it happen only in hordes? on specific maps? or literally all enemies even if they’re alone?
Thanks in advance!
I tried verifying the integrity of game files and although 1 file failed to validate it did not fix the problem then i disabled all mods and that did not fix the problem either but i think i have found the cause of the bug after more testing today. It seems that when you kill any gas rats, bomber rats, leeches or skulking sorcerers with any type of dot damage they will continue to make noise after they die like in the video but if they die to normal direct non-dot damage the bug does not happen.
This is especially annoying when it happens with a leech because if they teleport away and die to a dot they blow our your ears with extremely loud ambient leech noises for the rest of the game no matter how far away you get from the source.
Thanks CC! That’s super helpful and I’ll pass this information on to the developer looking into this. Much appreciated!
No problem lev. It would explain why i seem to encounter the bug every single game a ridiculous amount of times because i am a elf main that almost exclusively uses the moonfire bow.
you say “internally” are you guys using the same internet connection when testing? Because i seem to notice it more when I’m not the host
generally as soon as i get into game and someone has killed a gas rat
Must be a new “special feature”.
I am wondering that…
…because its happening quite often in CW. Especially with Gasrats.
It is a very common bug which happens to me a lot as sienna and hagstalker player…
Please try to fix it asap, because it is damn irritating when special sounds are active even if the special is dead, or when more then 1 are up you dont hear the second one who is still alive because the dead one blows your ears.
Not only in CW also in campaign, it happens at every content.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
Hey all!
After combing through the code and some testing we’ve still been unsuccessful in reproducing this bug 
That said, we’ll be implementing some prints in our console logs with the Necromancer release that should hopefully help us track this down.
Post-Necromancer update, when anyone runs into this issue if you can please provide your console logs from the culprit sessions it would be much appreciated!
This thread will likely auto-lock again by then, but feel free to DM me directly, or post up a new thread at the time 
thanks!
Alright then when the new necromancer class is released i will make time during the first or second day to get a fresh console log for you and i will ask other players that i usually play with to do the same.
In Twitch mode, at least in Chaos Wastes, the “(Critically) Unstable Breed” explosive rats will play their screaming sound in the spot they exploded / died in forever.
It’s kind of funny, I have been calling it “the screams of the damned,” but it is very loud and happens every time you get the vote.
Not sure if this is exactly the topic issue but it should be a reproducible example.
I’ll pass this info on internally, thanks!
Not sure if this is exactly the topic issue but it should be a reproducible example.
You are describing exactly the same audio bug as i am in my threads. Its any gas rats, bomber rats, skulking sorcerers and leeches but only if the leeches teleport away then die.
Its all dot damage kill related all far as i know so even if it looks like you killed them with direct damage it could have ended up being a dot kill which causes the audio bug to happen because of how fast dots tick in vermintide 2.
If you want to help me and the devs get rid of this audio bug then when the necromancer class is released if you hear the audio bug happening close the game 10-20 seconds after hearing it or after you are finished playing the game you are in so your console log updates. It helps reduce the file size so it does not have too much unrelated nonsense in it and then post that console log either here or in a private message to lev like i am planning too.
+1 this has been annoying the sh!t out of our party of regular players for a long time. Lingering special sound effects after dying. Frustrating at cata, as you ‘react’ thinking there is still a special stalking you somewhere, but its not really, and now you’ve invested time and strategy, positioning, etc. dealing with something that isn’t even there – when you could/should have been dealing with other priorities.
I will download the necromancer update patch, and we’ll also keep an eye on this thread / assist with troubleshooting if the issue persists!