Visit the Kill Switch Master List for more information on this and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
Which killer did they broke in the 3.3.0 patch that they had to delay it?
It could be another like one of those Legions stacking situations or where the perks has a bug that made them more powerful than intended, and instead of banning people this time they actually took the time to fix them.
Comments
-
we will get update abot event tommorow
3 -
Whichever one was not meant to be changed in any way whatsoever but ended up being broken anyways. :p
1 -
I see flaws in your logic.
Imo, either one of the consoles wouldn't certify the update or the rift has bugs.
2 -
personali i think its a consol matter that why they keep being quaiet about this bug they dont wont us to start some sort of "hate train" to consols players and i get that lets be reall it would probably happend
1 -
Most likely something went wrong with archives or the event, after so many broken perks and addons with every patch I honestly don’t believe devs can figure that some perk or addon got busted.
0 -
Oh yeah I forgot, they started holding back launches on pc or other systems if one of the consoles didn't pass cert. Even if its possible to hotfix it on pc day one. 😭
0 -
Nurse.
She was completely broken in the PTB. She would turn invisible sometimes, had weird laggy movements other times and even if the right addons were used, couldn't hook anyone, or just crash the game. Also sound was somehow off again..... Every patch breaks audio some way, I really don't understand how.
5 -
It was almost definitely something to do with the archives, because as far as I know the event is the same as last year.
I bet the challenges you have to choose in the archives are affected by the same bug that is changing players' daily rituals. You go into a game with one daily and when the game is over it is a completely different daily.
0 -
It has nothing to do with console. Find it quite funny how pc users MUST think it HAS to do with console if something goes wrong. Maybe it has to do with the rift and maybe they were fixing it to be more doable.
3 -
We say console because they have to go through a certification process that may get rejected whereas Steam doesn't care if your game breaks.
Rift issues is possible especially if it deals with the paid side.
2 -
They've known about cert for years. Not budgeting their time for that is 100% a bhvr issue, not consoles.
They don't still get a pass on that, its not their first rodeo.
1 -
All of them.
0 -
It's a huge patch considering it comes with archives, rift, nurse changes etc. There are many things which can go wrong and become literally gamebracking/crashing etc. Doesn't make sense to speculate.
1 -
I mean it wouldn't be the first time a pc patch got held back because consoles failed their cert.
0 -
... Are we all forgetting the fact that they never said the patch was delayed? The event was postponed, that was all.
(Not saying the patch hasn't been delayed, just that there's no evidence for it so it's a bit of a leap to make.)
0 -
I do think Peanits was quoted as saying it was a major bug in the patch and engine update that did it.
1 -
Could you link me to the quote? All I've seen him say was that something big went wrong that they had to fix.
0 -
okay, I found a few. Sorry if they are not pictures but you can find them on his Profile.
"You pretty much answered your own question. We ran the PTB, collecting info on some of the known issues (and found some new ones), and we're now trying to get those fixed. Fixing issues takes time, it's not always as simple as changing a few lines of code. Beyond that, you need to figure out what is causing the issue in the first place (the PTB helps narrow this down greatly).
Again, it's unfortunate, we don't like to be in this position either, but this is what the PTB is for. Had we released the update with those bugs still in the game, you'd have people asking why we bothered with the PTB if we weren't going to fix the bugs that were reported."
"There are bugs that we need to fix before the update can go live. Bugs that would ruin your games and make you not want to play. Bugs that would turn a fun event into a miserable time. I get that it's disappointing to have it delayed, I really do, I'm looking forward to playing it as much as the next guy, but forcing it out before it's ready isn't a good idea. We'll let you know as soon as we have more info."
"Some issues came up when we were getting the update ready- bugs that would not be acceptable if the update went live right now. That's all there really is to it, it's not as interesting as you might think. We just want to make sure it's solid first.
We're hoping to have it out as soon as possible, but I can't give you an exact time yet. We definitely want to make sure it's out before Halloween, though."
"I don't see how the rudeness is necessary. Everyone here is working hard to get it ready as soon as possible. This is one of the biggest updates in a long time combined with an engine update. Some things went wrong and we wouldn't feel comfortable putting the update out in the state it's in. I'm sorry if this is disappointing to you, but shoving the update out the door right now isn't a better option.
As far as the event goes, everything will still be happening according to plan, just slightly after it was originally planned. You won't lose any days, the end date will be shifted back to match."
1 -
Interesting, so that does make it sound like the event and update are intrinsically connected, not only mechanically but also in terms of planned release schedule. I got a different impression from the original tweet. Thanks for going out of your way to find those, it was very helpful!
0 -
No problem! I want to make sure that everyone understands the situation as well as we can right now. No need to get upset with them for things they can't help after all! I'm just glad they are fixing it instead of pushing it out!
0 -
Why is it killer?
1
