Why is no one fixing it??
Its been in game for like 7-8 months already, its literally impossible to find a survivor with that sound bug(Specially on this map!), and also this bug can appear while survivor is injured too, thats bs. Its not like a latency bug, so why devs can't fix it? Or its not ruining games? Literally one free perk for survivor.
Comments
-
Judging by the time in the game you have provided you are new to how sound bugs work so ill inform you i have played since 2018 meaning i was around for the dreaded 6 months with literally no sound at all and back when stridor or deerstalker was actually a needed perk point being sound bugs are very hard to pin point and once you pin point it you can fix it and then break other things perfect example the killers heartbeat which actually got jacked up from them trying to fix the no sound issue for killer.
I Imagine this is likely a priority bug but its not as easy as you believe it is this will take time in the mean time deerstalker is not a terrible perk if you are having trouble finding slugs.
0 -
not trying to be salty, but do I really need to run a perk to prevent the game bug? Sounds like "run iron will to counter the spirit". I mean, deer stalker is 10/10 perk on killers like oni, nurse, billy... But what if I'm playing doctor or trapper for example, I don't need deer stalker on them, so it would be just 1 perk slot wasted.
1 -
I mean with doctor survivors scream on the ground if im correct also you have his illusions that appear which give you a good indication of location.
Also take it from someone who was around when things like this happen you have to adapt its all you can do i can tell you right now i have no issue finding slugs and its mostly due to i adapted to when there is no sound this is nothing new to me those 6 months with no sound in my opinion made me a better killer i learned to use visual queues more to locate survivors like crows flying etc.
Also the thing about trapper is there really is no set build to him you can play him how you want to play him and thats really with any killer deerstalker is not a bad perk if you combine something with it like knock out for example and as far as stridor goes its good on any killer if you struggle to hear sound.
0 -
only with an addon. Why should I adapt to this bug??Btw , its only not this, sometimes survivor can run you on the title and there is no sound too, I think "ok, iron will" but when I'm looking on their perks I see 0 iron wills, and I can see this bug while I'm playing survivor, literally no moans. I want to be able to mindgame them, but I can't because this bug. It can be compared to the fact that the killer would not have a red glow in a chase without huntress perk. And one more thing, this bug completely counters the stridor, you can't hear their moans.
0 -
I dont believe this bug effect's stridor i could be wrong on that i know stridor was bugged im not sure if it is still bugged or not i dont play spirit anyway point being the reason you have to adapt to this bug is because it's how the game works when things like this happen you have to learn to play around them and again what you just mentioned is exactly how the old sound bug was except it was way worse and when i say way worse i mean way worse right now i can still hear grass move back then you couldn't hear anything a survivor could follow you around and you couldn't even hear them right behind you.
The reason im saying try to adapt is because it's what players like myself had to endure and i for one still believe it made me a better killer i got better at seeing survivors in a far distance(Keep in mind this was also in thick fog) i got better at watching for visual queues and honestly it made me a better killer player bugs like this happen there's no way to prevent them but you can be ready for when they happen and learn how to focus on visual queues over the normal audio ones.
0 -
Once one man said: "If it doesn't hurt the survivors, why should they fix that?". Sometimes I think there is something true about that.
1 -
It's suprising that this bug has been around for a long time and devs just don't give a damn. (IT'S BEEN OVER A YEAR) Is it really that hard to fix? Especially when new killers get like every 3 months.
0 -
If you took the time and read my comment it is not easy to fix touching sound files can lead to even bigger issues which take even longer to fix i imagine they are still trying to find what is conflicting and or causing the issue it can take some time considering how many sound files there probably are.
0 -
Seriously? You think a year is not enough time to fix one bug? Especially when the game is 4 years old and the team is probably experienced now?
1 -
Again im assuming you dont understand how sensitive audio files are and how touching one thing can lead to hundreds of other issues the last time this happened it took 6 months and that was due to how serious the issue was they pretty much had to drop a lot to focus on it how things are right now it's no where near as bad as the 2018 incident which was actually game breaking but i can tell you it's a priority that's for sure they could have already fixed it but ran into another issue for all we know bhvr is very secretive as of late to whats going on behind the scenes but im sure there is a handful of people trying to fix it if not more.
0 -
Never seen a person who defend bugs so much.
1 -
Im not defending them i just understand how it works if you believe in your mind that its so easy to fix behavior has open job applications go and apply and then come back here once you have seen the process of fixing audio files we would all love to hear how fast it took you to fix them :P
1 -
Pretty sure anyone including you and me could fix this bug in a year by ASKING around or GOOGLING or TAKING a closer look at the audio code.😅 It doesn't make any sense why this takes so long. And don't tell me sound related code is more complex than gameplay code that they have no problem fixing.
0 -
It's really up to you. You don't have to, but if you're having trouble with it then you might want to consider it. We kind of just have to do what we can with the product BHVR gives us.
0 -
Hey my guy since you seem to think you can fix audio files so quickly you can gladly apply and show the veteran sound guy how its done since you believe its so easy you should have no problem fixing it for him even though he's done this for a hot minute what might seem easy in your brain can shock you to a new extreme when it comes to reality audio files are a risky thing to touch but since you know how to fix them you would have no problem doing the sound designers job for him. Point being unless you know what you are talking about or have an idea of how sound files work its best not to say you could do it because we both know the answer is you wouldn't be able to ingame code and audio files are two different beasts both present challenges instead of trying to tell the developers how to do their job you could gladly learn how to do it so you can gain a better understanding of the process involved.
2 -
Oh my god. You're an actual dumbass.
Story time.
I don't work with coding, programming, or audio, but my cousin does. It's all low tier stuff, indie games and the like. But he ends up with a small issue in one of his games. At one point, the sound of a foghorn was meant to play and it wouldn't. So he goes in and tries to fix it. Bear in mind, he's been doing this for 4 years and he's currently in college for it at this point in time.
He manages to find out what was wrong. According to him, he'd put the sound file in the wrong pathway. No major thing, just needs to move it to the right one. Right? Wrong. He does that, and it says there's already a file with that name. He figures it's the bad one that won't work. Maybe he copied it before and something went wrong. So he overwrites. That turned out to overwrite the file for a totally different sound. So now the game is still missing a sound. He tries to restore, and he's ecstatic when it works. But when he finally gets it fixed, there's an issue causing both files to play at the same time, EVERY time that ONE of them is meant to play.
He goes through some crazy long process to fix it, and the result was both files getting corrupted. Totally useless. Restoring them does nothing. So he goes to delete them and use his backups, only to find out his backups were saved AFTER the originals corrupted. Meaning he has no working versions of these sounds.
He had to start from scratch with those files, and after a few weeks of fixing that issue (it took him forever to convert them properly, put them where they belonged, and get the game to recognize them properly) it still played both at the same time whenever one was meant to play. To this day, he can't figure out why, and that was six years ago. He's started treating it as his "true graduation" saying that he isn't TRULY finished with his college assignments until he figures out why it's messing up. He's corrupted the files again and again, lost weeks of progress, broken dozens of other things in the game, and has had to fix each and every issue as it comes, JUST to get those two files to work properly. All to no avail. They just won't work.
All of this is very simplified. He explained it to me in detail and it threw me for several loops, so he explained it to me this way so I'd understand it. So there's a lot to this I didn't cover, simply because I couldn't. I'm no good with this stuff, and the technical terms confuse me.
And the point of this is: if my cousin, who has 10 years of experience working on this sort of thing can't fix two little files in that time because they just WON'T work together properly, I can understand DBD having to take a lot of time to fix this. We never know what's up behind the scenes, and they may have other high priority bugs that makes the game much worse than a little sound issue, or maybe the file or files for this event are set up perfectly and just WON'T work for some reason.
Don't say "it's easy". Go make a video game as big as DBD from scratch and then tell us how easy it was. Until then, buzz off and take your arrogance with you.
5 -
Was she slugged for so long that she had crows, because all I heard was wings flapping. What a waste of that person's time. What are you afraid of ? Hook her, and move on.
0 -
she is just like to eat grass, why don't you think about it?
0 -
Not sure how about 4 years ago the sound was actually pretty good, a year after the fact it was kind of okay. But the last 2 years it's been utter garbage. Flip-flopping around, to quiet, can't hear at distance/have to be VERY very close, killer footsteps loud as hell, and the works.
Sound was back during the Clown Chapter, at lest for me, then they "fixed it" and now it's been gone ever since. Nice...
I get some sound on occasion, but there is no consistency. One match is fine-ish, the next I can't them crunching the damn grass.
1 -
Why did you have to hit the survivor on the hook?😂
0 -
I think whenever there was a bug with sound, it wasnt fixed back to 100% ( or the way it was before the bug). As far i know it noticeably happened atleast 3 times.
And complaints are just shut down with "witty" advise about headphones or turning sound up until the chase music tears your eardrums.
0 -
Nothing to think about. Killer up.
0 -
Don't worry she is getting a rework soon 😎
0 -
what??
0 -
When there injured not downed the might have iron will
0 -
already answered on that question.
0 -
Fair enough. I wasn't trying to be arrogant or anything. It's just I can't get my head around one bug taking so long to fix. And since I have played a lot of games I struggle to think of any other bug taking so long to fix considering this is an impactful bug, it's not a little sound issue.. I am not even sure they acknowledge it. If they said something about it and cleared it up it would help.
But right now it's just ridiculous. It's just your and my guesses as to why it's still not fixed while devs don't comment this. We are not a bunch of sound enginners here and we are not supposed to know whether it's hard to fix or not. But we are supposed to get some communication on that and not be ignored like that.
0 -
As someone who programs as a hobby (though I did also learn programming in college), trust me, it can be a major pain in the ass to find and fix bugs.
One time I had a bug where a variable wasn't being updated, despite me using the proper function to calculate the new value. Why was it not being updated? I forgot to assign the new value to the variable. It's a rookie mistake, but because it's a rookie mistake, it's not something you'd immediately think about when you've been doing it for over 5 years.
The most common way to find bugs in a code is via a method called "rubber duck debugging", wherein you get a rubber duck (or some other item; could even be a person - I prefer to use my BF, personally) and describe to it/them what your code does, step by step. That breaks the human mind's tendency to gloss over the finer details when it comes to something you made and helps you find bugs. It sounds ######### stupid, but it almost always works.
If the code is written improperly, though, like in the case of so-called "spaghetti code", fixing bugs becomes exponentially more complicated, because everything's connected. You change one thing to fix one bug, but the thing you changed is used in 15 different places, so now you just broke 15 other things.
0 -
While I can definitely understand and appreciate the cascading bug fix/creation cycle, this feels a bit different than that. One would assume they use different sound channels for various types of sounds in the game, and there is some type of issue with whatever channel the affected player's voice is supposed to be on not playing properly, be it through the channel being blocked, used by another sound and not freed up, or some other similar issue. IIRC the Bubba Chainsaw sound bug gets fixed if he does a normal melee attack, as playing the new sound for the swing overrides the faulty loop that the chainsaw sound was stuck in (since they presumably share a sound channel.)
Its worth noting in the example provided that the pain grunts on the ground were completely silent, but the wiggle sounds were present after being picked up: The issue could be very similar yet not being explored properly, especially considering how long the issue has persisted in that particular scenario. In that regard, issues with sound channels should only be able to impact other things that use the same channel, or similar attenuation/general volume algorithms/settings. Considering how important sound is for a lot of players (especially colorblind ones, since you might as well play blindfolded sometimes) it should be a VERY high priority fix every time a sound issue occurs.
0 -
I know I may have come off as rude, and I apologize for that. Your previous responses really didn't seem like you were the type to be open to the idea but this reply proves you are.
While you're right in that it's a SEVERE problem, it may not be impacting as many people. While, say, 1 million cases is a lot, it's not much compared to, say, 5 or 6 million. These are just example numbers, but the point stands.
If 5 million people are having issues with one thing, and only 1 million are having an issue with another thing, then typically they'll focus on the 5 million first. That said, severity can impact this, but we don't know what's going on behind the scenes. There may be an equally severe problem which more people are suffering from, or maybe there's a more minor thing that SO MANY more people are suffering from that the other issue has hit priority status.
I'm not blindly defending them, if this is the worst bug they have right now, or if this is the most impactful, then by all means they should dedicate their resources to it and be as transparent as can be about it.
But I always like to play Devil's Advocate. What if it's because X, or what if it's Y's fault instead?
If this is a low-impact bug to a majority of players, a high-impact bug to a minority of players, or even just plain hard as nails to fix, then it explains why it's taken so long to do something about it.
But I do agree with you, in all three events: the company should absolutely be open and communicative about what is being done, if anything, and how much progress has been made towards it.
Unfortunately, we won't know if they're even trying to fix it until the next patch notes come out. When they do, take a look at them and see if there's something worse that was fixed. If so, that may be why they haven't gotten to it.
0
