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
Get all the details on our forums: https://forums.bhvr.com/dead-by-daylight/discussion/436478/sign-up-now-to-receive-a-recap-of-your-2024-dead-by-daylight-stats/p1?new=1
What type of servers are we getting?
It's almost as if the Trickster knew and brought that offering on purpose. I literally got hit whilst falling down from a vault and his blades were such a pain. By the way they didn't have any ping problems because there was no indication on my screen. This is literally absurd.
Game right after it...
Yet again with the offering...
Best Answers
-
You're really overthinking DBD's basement bargain servers.
2 -
Yeah because that's what it looked like on *their* client.
That's not any different from a survivor seeing in their game client that they completed a vault, ran 10 feet and then suddenly got damaged anyways.
That's what hit verification is for, to verify on the server's side which player is correct in what they see on their client. But instead they are choosing to handle it on the killer's client-side, which is a terrible way to handle networked gaming.
And the reason why the killer sees the hit and hears the scream is because that's another thing thats handled client-side for them. Even if they lost connection for 2 seconds their hit would go through.
I've actually had killers who have abused this client-sided way of handling things. They would use a lag switch to disable network for 1-2 seconds so on their end the survivor's positions don't update. Then you can hit them in your client, and once the forced lag is gone that hit state is sent to the survivor. I had one killer do this during defisive strike, which froze his drop animation on my end, and he was able to swing at me before I even took one step.
So this is the same problems on both sides due to poor net code, but like i said killers just find it more unacceptable.
0
Answers
-
This has never happened so often...
Post edited by mikewelk on0 -
idk, I've often felt like the devs prioritize the killer's hit recognition while Survivors have to deal with feeling "wow that hit was bullshit".
Like, they implemented hit validation at one point, but immediately removed it after Killers complained about their hits feeling like they should have landed but didn't. Even tho that's been an issue for survivors for years, where hits look like they should have missed but you get hurt anyways.
So I'm fairly certain the game is designed to prioritize good connection and responsive gameplay for the killer. My guess is that the reason is that survivors tend to deal with it better emotionally, while killers generally feel it's more unacceptable when their main purpose in the game (hitting survivors) doesn't register properly.
At least that's my guess. And I'd understand if a lot of killers would stop playing if it felt like their hits were missing all the time, while as a survivors it's easier to accept.. even if it still sucks.
0 -
The main issue was that killers would hit, the survivor would lost th health state in the hud and scream, before completing the vault/dropping the pallet after magically ignoring the hit that the killers game had said landed.
0 -
That's what hit verification is for, to verify on the server's side which player is correct in what they see on their client. But instead they are choosing to handle it on the killer's client-side, which is a terrible way to handle networked gaming.
That's actually not true. I can speak from experience that the killer doesn't handle it, like at all. I've had moments of a lot of lag and hit survivors who didn't take damage because the server said they weren't there, even though on my end they were
0
