BonfireFodder
BonfireFodder
About
- Username
- BonfireFodder
- Joined
- Visits
- 10
- Last Active
Comments
-
@MrCookie said:
https://forum.deadbydaylight.com/en/discussion/comment/1298419#Comment_1298419
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.
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.
-
@MrCookie said:
https://forum.deadbydaylight.com/en/discussion/comment/1298300#Comment_1298300
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.
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.