Надо будет посмотреть может вот это поможет:
Hit Registration Improvements
Sharing the answer provided in the AMA earlier this month, with an update about server tick rate:
The hit registration issues are actually multiple issues that we will be working on. Some of them are being addressed in this title update, while others require development time and be addressed later (as soon as possible).
Fixed bugs on replication and kill cam:
Fixed: Pawn rotation latency: the difference between a player’s action, the server’s perception and another player seeing said action had an extra delay due to a bug. This had even more impact on shield wielding Operators since sometimes players using those would think they were protected while they were not because of the additional delay caused by the pawn rotation bug.
Fixed: Shield positioning while rappelling: certain shield angles were not being replicated properly, this caused the shield wielding player to be overprotected in certain cases. This caused hit detection issues for the player shooting at the shield wielding player.
Fixed: Shooting and moving while rappelling: when moving and shooting while in rappel, the hits were sometimes not registered properly by the server.
Improved: Kill cam replication issues: the kill cam was not displaying an accurate representation of hit positions. The point of view seen after death was not the exact point of view of the killer. Moreover, we have instances in which the kill cam shows body parts sticking through walls while they actually weren’t being seen from the killer’s perspective. This has been improved for the next title update, but we still need additional work on this. It is still considered under development.
Updated the server tick rate for PC (intermittent & temporary)
With the goal of improving positioning and shooting replication, we will be deploying a first update on PC in which the player position update rate is set to 60 times per second (vs. the previous 30). Having had conclusive tests internally, we have decided to share this update on PC first because it has a faster deployment speed compared to consoles. Note that these PC tests will be intermittent as we will be trying various configurations until we are satisfied with the outcome. When this feature has been validated with various external tests on PC, we will be deploying this update on consoles as soon as possible.
Connection to wrong data center
Another issue we will be working on is that right now, some players connect to the wrong data centers. If you are not connected to the nearest data center, your gameplay experience will likely not be ideal. We believe that the best solution for this will be to allow the players to select their data centers and that is what we will be working on.
General issues we are aware of:
Although we do have a high ping kick in place, one thing to note is that there are some edge cases in which some players have high ping due to poor internet connection spikes. This affects replication quality for the other players within that person’s match.
We hope that this addresses your concerns and we will make sure to keep you updated as we keep monitoring and improving on this and progress within our plans.