Audio and Hit registration
So I jumped back on BF2042 after a few months to play on the new exposure map and I guess the game is still flowing with the same problems. Firstly the audio: the background audio of the game is dec...
Forum Discussion
@Adamonic wrote:...
For hit reg, I have no clue what is going on. It feels like a huge desync. If we could choose the servers we play on, we could at least guarantee we have a good ping to the server. I wonder what tick rate the servers are?
Just before Christmas some tests were run, where we determined the server tick rate was at 45Hz.
This was done as we at that time also suffered from severe server lag and hit registration issues.
Don't know if the server tick rate has been changed since then, but the issues with substantial server lag and lack of hit registration continues. Think though this is root caused by the closure of servers in some regions. Causing us now also to have more far out of region players with high pings in the mix... Hit registration is always going to suffer under such circumstances.
@CyberDyme Lower tick-rate makes sense with more players, another thing that suffers from increasing player-count.
But BFV has severe netcode issues with 60hz ticks (TTD/insta-death) and BF4 is really bad running 60hz ticks (insta-death, killed around corners etc).
Dice have never had perfect netcode, but for me the netcode of 2042 feels like playing BF4, which is an 10 year old game.
But BFV has severe netcode issues with 60hz ticks (TTD/insta-death) and BF4 is really bad running 60hz ticks (insta-death, killed around corners etc).
Dice have never had perfect netcode, but for me the netcode of 2042 feels like playing BF4, which is an 10 year old game.
- @cso7777 The insta deaths from previous battlefield games was down to the shooting player having high jitter or packet loss and the server had know idea how to interpret inconsistent information being sent so it sent multiple hits in one packet.
It’s probably doing the same in 2042
