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!
Does there need to be a Dead by Daylight 2?
Before reading this, 2 notes!
1 Please go watch this video by Scott Jund who explains loosely how DBD has been coded
2 I am not a coder. I do not have experience with coding at all, or computer science in any fashion. This is just my opinion and an idea I built off of Scott Jund's video
I think it's a widely known issue that Dead by Daylight has not been coded to its maximum potential. I am not blaming the developers when I say this. I don't think anyone expected DBD to blow up the way it did, and that is not something we as a community should blame the devs for. However, at this stage in Dead by Daylight's history, the game is probably more buggy than it has ever been. What causes the bugs and why does it take so long to fix some of them? It's because of the way DBD has been coded. Scott Jund goes into way more detail, but essentially DBD was originally coded using blueprints. This isn't an opinion or a theory: it is a fact. A while ago, the developers said they were making the transition from blueprinting to C++, but I don't know if they actually ever followed through with that. Blueprinting is not meant for large games like DBD, and it is even worse for games that have content added every so often. With new killers and survivors (and before the map reworks maps) being added every 3 months, the blueprinting system is just simply too chaotic and messy to keep up with new content. This is where bugs arise from, and this is why it takes so long to fix them. Finding the problem in a pile of spaghetti, as Scott calls it, can take a LONG time. Not only that, when you mess with something that is unintentionally connected to 15 other things, then you run the risk of creating a new bug. At this point, Dead by Daylight has generated mass revenue for BHVR. Is it unreasonable to consider a new Dead by Daylight game with an updated engine to allow for better and more efficient coding to reduce the number of bugs we see in the game? Again, I do not have experience coding, and I do not know how long or how complex it is. If anyone has any input on why a new DBD would be good or bad, please share your thoughts!
Comments
-
This is McLean's response to that video
8 -
Then they have a hell of a lot of explaining to do about the issues with Console Optimization and the enormous amount of bugs.
7 -
This content has been removed.
-
I agree with that. It definitely opens up more questions of ######### are they doing wrong. I've said before - when it comes to console, they've shown they lack basic knowledge of consoles (at least with playstation) which is probably why there's so many console issues.
2 -
They've completely overhauled the game multiple times. From I've played in the past, what I've seen from older videos, and what we have today; I'd say we're at least on Dead By Daylight 3.
7 -
No, I've spent too much time in this game, I don't want another one doing the same but worse. This game still grows and gets better, there is 0 reason for a sequel.
3 -
Sequels are usually made to add content and plot, not fix and overhaul outdated mechanics. Those are a little bonus to the main goal of creating a brand new experience. This is usually more geared towards story-oriented games, like Dark Souls, Resident Evil, etc. DBD gets their new content via DLCs, similarly to Overwatch with heroes.
The reason Overwatch is getting a sequel is because Overwatch 1 hit its peak already. They need not only new content, but a whole makeover of the original. DBD, meanwhile, is still growing.
The issue with DBD's optimization isn't even necessarily in how it's programmed. Unreal's blueprint is no different, in terms of bug-finding and unintended consequences, than writing out actual code. All coding does is give you more agency and more choices about how your game should run, which is unrelated to bug-fixing. It's just that BHVR is really, really inexperienced with big games that compete with other huge games. DBD is their first successful game, and they're a relatively small company.
It's not even just bugs. VfX are incredibly inefficient. Ever had the misfortune of playing console?
2 -
If they no longer use blueprinting for a majority of their coding, I wonder where all the bugs come from then? MacLean said from a manageability standpoint, their blueprinting and C++ are perfectly fine.
0 -
It would have twice as many bugs
0 -
True i don't think there will be a "dead by daylight 2" ever. This one of those games that gets updated constantly as long as its profitable for the devs and splitting their playerbase isn't a wise choice. They already hit a wall trying that with deathgarden.
Also theres no need to do that when you can upgrade your game indefinitely just like WoW.
1 -
Naw game can be upgrade with updates.
0 -
we dont need it
u wanna wait 10 years for them to release all the killers we have on DBD 1?
0 -
I've been getting the impressions from listening to the war stories of the few coders I do know that optimization is not as cut and dry as us outsiders would like it to be. Sometimes you look into it and quickly find something that gives you a couple dozen milliseconds back per cycle. Sometimes you dig for hours and hours and can only find a way to shave maybe 10 milliseconds off your cycles.
I'm not saying BE is perfect - we have plenty to roast them for. But let's not pretend that some content creator knows more than the devs.
2 -
No modern game needs a sequel because you can always Live Update your game. Unless the experience is meant to be a departure from the original, starting from scratch just in an attempt to be better than what you started with is a fools errand.
0 -
I'm legit quitting DBD if for some reason this happens and my cosmetics and character unlocks don't carry over.
0 -
So how can they explain the Twins patch?
Remember that list of over 100 bugs that came with it?
0 -
That would be something to ask McLean either on his stream/discord or ask in next dev Q&A as I'm sure it'd get plenty of up votes to atleast be addressed. As I said in previous comment it does open up questions of what are they doing wrong because there is no denying there are plenty of issues in the game.
0 -
It's sad how basically all statements about the game from the devs and community managers boil down to 'go ######### yourself'
Be it this, the 'we could change the UI but it would mean undoing months of work'-guilt-tripping attempt, the list of exploits etc that are NOT bannable but don't get fixed, the statement that camping, tunneling and slugging are 'sometimes necessary', trickster, the lack of worthwhile events, mindboggling decisions in terms of perk and map changes, the general ignorance towards community feedback....
1 -
I've already invested too much time and money into Dead by Daylight. There's no way that I'd consider moving to a sequel unless all of my progress is transferred.
I think they'd be able to keep new content and updates coming from this one rather than making a second game.
1 -
Time spent playing DBD is the reason why many still play it. Those players will not start over again with a new grind.
There's no reason to create a sequel with this game as a service model. You just continualy update it.
0 -
This is my response, AQA Computer Science, to that video: Change the code. It may take a year but making a whole new game just to optimise code is a laughable waste of time.
1 -
Around the Blight patch ps4 had a ridiculous amount of performance issues, basically unplayable for weeks. The first "solution" devs gave after about a week and a half was to update the system - but it's basic ps4 knowledge that you can't play online games if your system is not up to date, so players wouldn't have even been able to log in to DBD to play and see the performance issues. Players had to point this basic fact out for devs to go back and take another couple weeks to make the game playable on ps4. There's still a list of old triggers for both killer and survivor that cause FPS drops on console (@Pulsar and @OniWantsYourMacaroni have shared multiple videos showing these drops) and new ones have popped up in recent patches just adding to list of poor optimization. I've seen PS5 and Xbox series x players begin to mention performance issues after some of the more recent patches, it's not old hardware it's something in their coding that screws up performance.
As for controllers - Trickster PTB and Blight PTB pc players during PTB pointed out issues those using a controller would have and it was ignored. They just do not test killers playability on controller and players that use controllers spend months pointing out the issues that were pointed out in PTB.
0
