ArcT
ArcT
About
- Username
- ArcT
- Joined
- Visits
- 0
- Last Active
- —
Comments
-
Twice in a row this afternoon again.
The one time I was playing with someone streaming, every person in the lobby's ping suddenly went red and two people dropped within 5 seconds of each other, but I got the "Dedicated server not responding" message, which is clearly completely incorrect because the server was still up and fine, despite at at least two people having over 500 ping for a moment.
I do NOT have this issue with any other online game I play, and did not have it with DBD until the Alan Wake patch. This is an actual, genuine NEW issue, as the multiple posts about it every week indicate. Whatever was changed in the connection code in January is causing clients to disconnect on far too much of a hair trigger, and the error message gives both an incorrect and unhelpful indication of what the issue is.
-
Two out of three matches had dedicated server not responding tonight.
This is at least the fifth one of these threads that I have personally remarked on this.
Ever since the Alan Wake patch, servers have been horrific. No rhyme or reason to it. Sometimes survivor, sometimes killer. Sometimes a penalty for supposedly DCing, sometimes not. Just always extremely unstable.
West coast, US, if that makes any difference. This was exceedingly rare until a couple months ago, and is now unbearable.
Fix it already, or create better error messages so we all have at least some goddamned idea what's going on.
-
They'll just close this with a link to their technical help page as they have every single other thread about their servers crashing or being down since the Alan Wake patch.
Like, come on here, BHVR. Something has been completely broken on your servers since this patch and gaslighting people about it isn't the way.
-
Two out of three tonight, and DC penalties back in full force.
Both times it crashed were mid-hook.
This is getting incredibly old.
-
It would be helpful if BHVR could provide what exactly we could give them to actually report/diagnose this.
Since the Alan Wake patch, I've had dedicated server crashes somewhere between 33-50% of my games. Steam. West coast. 6-9pm.
I've mostly been playing killer, Wraith, Slinger, Dredge, Hag, and seen crashes on all of them. Slinger seems most common, but not so much so that I wouldn't chalk it up to randomness. No consistently used perk or add-ons among them. The worst was a full Hex build on Slinger for a rift challenge (Retribution, Ruin, Devour, Undying), which crashed 3 times across two days before I was finally able to finish a match with it.
Sometimes the crash is 3-4 minutes in. Sometimes it's when the game is essentially over. Sometimes in chase, sometimes just roaming the map. There's always a 4-5 second period where the server has clearly lagged out (unable to interact with anything, survivors continue moving in a straight line, etc), but zero latency indicators, and then the server dies with a "Dedicated Server Not Responding" message. I'm still gaining experience from the games though, bizarrely, and the last couple days, have not seen a DC penalty from it, so that's nice at least, though that seems to me to indicate that the existence of an issue here is known.
-
Crashed three games in a row for me.
One time while I was goddamned closing the hatch.
BHVR is going to close this again with "Sounds like you're having technical difficulties. Here's a link to a page that contains zero references to the error you are experiencing and offers no solution or help." Please show me where on your technical support page any even reference to "Dedicated server not responding" is. It does not exist.
https://support.deadbydaylight.com/hc/en-us/search?utf8=%E2%9C%93&query=dedicated
This is past ridiculous.
Fix your damn servers.
-
I mean, they gave multiple major baseline buffs to regression, a ridiculously powerful new (effectively) gen stall perk that cannot be played around and synergizes with every other regression perk AND both camping/tunnelling, and the 'nerf' that's supposed to make things less miserable is supposed to affect less than 1% of games.
What was anybody expecting?
-
+1
The server has crashed in 4/10 games over the last two days. This would be unacceptable on its own, but being hit with penalties because BHVR's own servers keep ######### themselves is insulting.
-
If the goal is that the limit on regression events is supposed to affect only a tiny percentage of games, then why is regression getting such a significant overall buff, both in kicking and in removing gen tapping? Those changes affect essentially 100% of games. Are devs seeing regression right now as too weak? Seriously?
-
@Seraphor said:
https://forums.bhvr.com/dead-by-daylight/discussion/comment/3635382#Comment_3635382
This is my take as well. DMS and PR is already a godawful combo to be on the pointy end of, but it's not game-breaking, and neither will this be.
If anything this will be less problematic. DMS + PR blocks YOUR gen and only your gen, meaning the killer also knows where to go to get the maximum gen pressure.
GE + DMS will block all gens for 12 seconds, that means YOUR gen gets the same DMS treatment, while all the gens with zero progress also get 12 seconds of block. Killer has no idea which gen to go for. You can safely wait it out or aid your team mates.
DSM + PR is also unaffected by the new regression limit, as it can only activate 4 times per match, let alone per gen. DMS + PR is still going to be the superior option, and using all three perks together won't offer any additional benefit.
I'm not understanding the melodrama here.
Let's not even look at DMS. Let's just look at Grim Embrace on its own.
Pain Res works with it, and forces someone off the gen, and then blocks it before they can stop the regression due to gen tapping being removed
Pop works with it with zero issues.
It is strong as ######### for camping because it is a free 36 seconds of Grim Embrace alone worth of time that survivors can't work on generators at all. The only real way to punish camping is to slam gens, which Grim Embrace does not allow survivors to do.
So you have a perk that empowers and strengthens every other S tier regression perk currently in the meta and used on every single killer, along with the most uninteresting, unfun, and overpowered killer strategy that exists in the game.
And then we add DMS, which more than doubles every single one of those strengths. Even Pop, because DMS will show you which gens were being worked on when Grim Embrace triggered because they'll be locked for longer.
-
Did you seriously put a majorly bugged perk in the Shrine this week?
Is this not going to cause an uptick in its usage and therefore by the stated logic, mean that it needs to be killswitched? You could save yourself the next week of closing duplicate reports about this after... over a month of doing it... by just killswitching the perk already.
-
Survivors ARE punished as ######### for 'forcing their objective' by getting ######### BP and depipping in those games. Which is also what they get when killers hard tunnel one out immediately.
Killers are 'punished' by people calling them dicks and hurting their feelings.
That you see these things as equivalent should spark some introspection.
-
This has been the modus operandi of BHVR since 6.1.0. A tiny band-aid to some extremely specific uncounterable killer strategy, usually facecamping, that doesn't actually address the issue, a baseline buff to killers, a couple killers get an add-on pass, and some miniscule number tweaks on perks. No followup to verify that their band-aid actually addressed the issue. Is the rework terrible or not? PTB probably won't help because they're going to make a massive change between it and live anyway.
Meanwhile, the new survivor content is being told to be happy they're getting camped by a Bubba/Huntress/Trickster/Slinger/Ghostface/Myers from 15m instead of 2, and 3 gen hostage situations will only last 20 minutes instead of 40. This 3 gen 'fix' doesn't do ######### when gens are so close they can touch, or in a recent Hens video, is actually a 2 gen because the third is unreachable/inescapable without going through the other two. And even if it did truly mitigate just one of the many, many "unfun situations" (to use BHVR's own vernacular) that killers put survivors in, which none of these have in the slightest, that's not the same as getting anything new or decent.
Making "unfun situations" suck SLIGHTLY less is very far from providing fun situations. It's like they're not even looking at survivor perks or gameplay at all for the last year and a half, except to nerf a random meta perk or item into oblivion every six months.
-
Here's a video of it in action.
This is pretty damn gamebreaking.
-
-
If I'm understanding this correctly:
Kindred was incorrectly revealing the killer's aura to the survivor when they were on the hook because it said "all other survivors." This incorrect behavior has been in place for years. This was fixed in the early October patch, but undocumented in patch notes.
People then reported this as a bug, and it acting in a different way than previously was acknowledged here as a bug.
The wording was then changed to instead say "you and all other survivors," again undocumented in patch notes, but the October change was not reverted, and there are discussions to go through with the original 'fix', revert the wording back to what it was previously, and keep the current behavior (not revealing the killer's aura to the hooked survivor with Kindred).
-
I don't understand what the issue with the second paragraph is. Everything in the situation where a survivor other than you is hooked is working as the wording there indicates as far as I'm aware. Is that being changed? Or discussed being changed?
The first paragraph is where the bug is. You say:
"the aura of the killer being shown to the hooked survivor is under discussion"
Why is this under discussion? In every instance where the killer's aura is being revealed, it says that it is being revealed to you, whether you are on the hook (first paragraph) or someone else is on the hook (second paragraph). You said:
" the wording of the perk does state that the killer aura should be shown to OTHER survivors (not the hooked survivor)"
Can you quote to me specifically where it is ambiguous about who the killer's aura is revealed to? What is the situation where the killer's aura should be revealed by Kindred, but not to you?
-
I'm sorry, Mandy, but that response is very confusing to me. The wording on the perk explicitly says "the killer's aura is revealed to you and all other survivors."
The wording clearly says that the killer's aura should be revealed to you.
All instances where the killer's aura revealed explicitly say "to you."
-
Please. It's been two months. Kindred keeps breaking and it's one of the few things that makes solo queue even half bearable.
-
That's not how it has ever worked, and is consistent with its implementation. It recovers at the same rate that it drains. For every one second spent healing, you're losing one second of it because you're still injured. And if it paused while being healed, it could be used with Bite the Bullet and a Medkit/Self-Care to preserve it essentially forever.
-
I suspect that this isn't unique to the Xenomorph as I ran into a Singularity doing this too and nobody was able to unhook. The area where you're able to unhook or the size of the killer hitbox may have changed.
-
It's probably fine to just override Deja Vu's highlighting with a more important one. That already happens for Scourge Hooks, and whatnot. But the priority should be Yellow over Red, not the other way around, same as it is for killers.
Though it would be nice on both sides to differentiate gen perks a little better. Especially Surveillance with perks like Eruption or Call of Brine. When a gen is highlighted yellow, it's difficult to tell which perk is the one causing that.
-
This bug still exists in 7.2.0 and I've noticed it also includes generators with Blast Mine, Wiretap, etc on them.
-
I've been getting weird frame drops with this patch too. It's way more noticeable on killer (moving around a lot more), but I've seen it on both.
-
Demogorgon also got a new bug this patch where if you cancel portaling, his POV gets yanked downward for some reason.
-
@Bommelkopf said:
https://forums.bhvr.com/dead-by-daylight/discussion/379063/pallet-phazing
Was the Blight using Compound 33 by any chance? If yes then I think we solved the mystery
It can happen just randomly too.
-
It's not DS specific, nor singularity. It's any time the killer drops someone, whether from DS, flashlight, flashbang, pallet save, or simply wiggling off. It's functionally impossible for a killer to not confirm a down by just immediately picking you up right now because even if someone gets a 'save,' the camera is broken and it's unplayable until they're hooked.
-
How on earth is this not killswitched yet? This is utterly gamebreaking and listed as a known issue.
-
Confirmed here as well.
BHVR, please. Some unit tests. Spend an hour before release just running through every perk to make sure they're all baseline functional.
And killswitch this ######### yesterday.
-
Confirmed it in my game against him as well. Happened twice while chasing me. Once in Nightfall. And with no red stain because Nightfall, and the ambient noises, just literally ######### impossible to do anything.
How is this not killswitched?
-
It wasn't that way previously, and doesn't make sense in almost any usecase. It's trivial for killers AND survivors to move 16 meters in the time it takes the bubble to disappear, and at both close and far distances, that completely obviates the aura reading near it, making perks like Bitter Murmur almost totally useless. At the same time, it obscures even when you have direct line of sight.
For example:
Or a video example here:
477 votes and 31 comments so far on RedditThis is different and inconsistent with how other notification bubbles (eg loud noise) work. Additionally, some auras are revealed through the bubble. Hooks and generators, for example. Survivor and killer auras should likewise not be placed behind the bubble, as they were for years before this unannounced, unexplained change.
-
6.6.0 and this bug is still present.
-
6.5.2 and still acknowledged but not fixed.
-
What exactly is the use case of this add-on if the omnidirectional audio changes when you approach survivors or it doesn't mask the phasing while affected by Oblivious/Undetectable? Sure seems like it's all downsides, zero upsides.
-
It's patch 6.5.1 and this still hasn't been fixed.
-
Using it to pseudo-vault activates Bamboozle on that vault, so that's a way you can abuse it.
If your timing is good, you can also use it to teleport to interactables.
https://www.youtube.com/watch?v=j8dB6gWd0_YDemogorgon also has a similar bug with using his portals, but the number of things you can interact with is much lower because of portal placement limitations.
-
@Thalonius said:
Version: Steam, Windows 10
The knight has the ability to interact with objects and players while using his guards.
https://www.youtube.com/watch?v=VJATrGZkgdM
1. Can vault window location to block it with bamboozle from a distance
2. Kick doors and pallets from a distance.
3. Can teleport to pallets pending on how fast the button is pressed.
4. Apply gen regression perks from a distance.
5. Open lockers from a distance. If a player is in the locker they teleport to the knight.
6. Teleport down players to you while you pick them up. This will allow players to reach hooks they normally could not reach.
7. Can mori players on the floor from a distance.
8. Can teleport inside a snowman using the guard as well.
9. The exit gates can be opened from a distance
10. Can grab players off of gens, vaults, exit doors, and unhooks attempts.