Visit the Kill Switch Master List for more information on these and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
We encourage you to be as honest as possible in letting us know how you feel about the game. The information and answers provided are anonymous, not shared with any third-party, and will not be used for purposes other than survey analysis.
Access the survey HERE!
So are the public test builds not actually for testing?
Or rather, is it like test driving a car? Just a bit of fun for the playerbase? Isn't the whole point of test builds to NOT launch with a bunch of crazy bugs like being unable to hook people, super short stuns, performance losses, etc?
We literally had no idea what fixed Blight would play like because it was an "old build." Why are you having the players do a public test build with an old build?? What a complete waste of everyone's time and thousands of hours worth of literally free QA testing.
Comments
-
They do fix bugs from the ptb, but fixing those bugs tends to make more bugs.
0 -
I have to agree. The only notable changes were add-ons and many bugs from the PTB are still here along with new ones; dragon's grip is bugged to the point that it's almost useless.
0 -
Its there to generate hype. Make people more interested in spending money for new content.
1 -
LOL at thinking the ptb would actually be used in a smart way. These devs got their coding certification from inside a Cheerios box. The sheer number of bugs existing and newly introduced can’t be explained any other way.
0 -
I'm just wondering how all of the other bugs just suddenly popped up when moving PTB to live.. no terror radius? Hooking bug? crashes? DS bug? footstep audio?
seriously? These would've been noticed in PTB but yet they pop up after the fact.. every single time
"well that means they made code changes to PTB" -- i guess that means no regression testing happened? TR / hooks / audio seems pretty obvious and widespread so..
1 -
It just seems like this project was rushed out just because they need to hit that new killer new survivor quota. There was no real testing going on and the PTB was just to see if he's playable. How can we give QA on a build that's not the final build, how did this get pushed out despite all the bugs happening. Were they just not seen during dev internal testing or something? What sucks is that right now, on release, this is the QA phase where he gets tested by the community and then changed after.
0 -
PTBs have always been a bit weird for this game. I remember Kate Denson having an absurdly loud actual scream when getting hooked to the point it was scaring people. (Can't have this in a horror game) so they changed it to something more silly.
Auras are the most blatant "wat" that should have been on the PTB first, but I get it, their offices are closed. I could make a joke about working remotely, but I see how finishing your batch of code without being able to communicate with your team members in real time might lead to some hiccups.
0