Hitreg tied to latency, workaround fixed it, now causes rubberbanding

I want to report a consistent and reproducible hit registration issue, pre patch, tied to low latency,
highly stable connections, and how this situation has evolved after the latest patch.

Background
I experienced these hit registration issues for several months. During that time I assumed this would
be identified and addressed internally. However the situation did not improve and eventually
became effectively unplayable.

I was close to giving up on Battlefield entirely, despite having a long history with the franchise, and
long time friends I play with regularly.

To be clear, I would never normally spend time reconfiguring my network. The only reason I did this
was because the game stopped being playable, and I had no other option if I wanted to keep
playing with my friends.

Baseline setup
• Ping 20 to 40 ms, very stable
• High FPS
• Wired fiber connection
• No packet loss

Pre patch behavior
• Hit indicators without damage
• Ghost bullets, in some cases up to 30 to 35 confirmed hits without a kill
• Close range fights feel desynced
• Enemies reacting before being visible

Pre patch workaround
I deliberately increased latency by routing traffic through a standard router, introducing slightly
higher latency and variability.

Result
• Hit registration improved significantly
• Gunfights felt synchronized with what I saw
• Shots registered as expected

=> The game became playable again.

Post patch behavior
With the same workaround
• Severe rubberbanding
• Movement feels unstable and desynced

Returning to baseline setup
• Hit registration issues immediately return
• Same symptoms as before

Key observation
I tolerated this issue for months, found a workaround that worked, and that workaround is now no
longer viable.

There is currently no setup that provides consistent gameplay.

Hypothesis
The system may be overcompensating for higher latency players, while disadvantaging low latency
clients through rewind or validation timing.

The latest patch may also have introduced stricter movement validation, leading to rubberbanding
under higher latency conditions.

Request
Please investigate
• Lag compensation scaling across latency ranges
• Rewind window behavior / lag compensation rewind window behavior
• Interaction between latency and rubberbanding
• Why increased latency improved hit registration pre patch but is now penalized

I can provide structured test scenarios as well as screenshots showing network stability, including latency, jitter, and packet loss before and after the changes in my setup.