The second iteration of 2v8 is now LIVE - find out more information here: https://forums.bhvr.com/dead-by-daylight/kb/articles/480-2v8-developer-update

ping issue

I hear you. A lot of Eastern and African regions have no servers to connect to within a sub-100ms range, and the gameplay changes significantly with that amount of latency present (actions and powers are delayed noticeably or behave inconsistently, survivors get hit in more and more ridiculous ways).

Originally when rolling out dedicated servers, BHVR said that in regions where there aren't any data centers near enough, they would keep employing the old, peer-to-peer-based system. So if paying for more servers or creating their own is not a viable option for them, the least they could do is create peer-to-peer pools where if there's enough people queueing in regions further than ~100ms from the nearest servers, they connect to each other again instead.

Another thing they said they wanted to do but didn't is make the servers the authority on hit reg, which would also go a long way to better the gameplay experience on higher ping (for the majority of players anyway).

There's little to no hope that they will do anything major about it however. They are aware of these issues, they have talked about them multiple times themselves throughout the years, but very little has happened in those years with regards to bettering things. They've implemented event-specific server hit validation for pallet stuns and Dead Hard (although that has gotten to be more unreliable with time as well), and I think there's been some undocumented extrapolation improvements, but that's about it.

Something you can do to help yourself apart from making sure your own connection is as good as it can possibly be (wired connection, real-time prioritization for your device/DbD in the router, contacting your ISP about latency improvements or trying different ISPs) is use software like ExitLag or NoPing, which improve the network routing for your game data, decreasing latency and potentially even packet loss.

Comments