Halo 5 has a lag compensation problem. The closer you are to the server, the worse off you may be depending on how the netcode effects you.
Just to clarify, I’ve eliminated potential issues being:
- modem - router - port forwarding - buffer bloat - DNS - ISPMy ISP is Comcast and I’ve recently had them send people out to test everything from my equipment to the cables. Cannot find an issue.
Ran multiple trace routes and no major ping spikes along the route.
Recently I was trying out Battlefront II and decided to track ping while playing. Minimal variance in the ping in the couple hours I’ve given it. I played Halo 5 before and right after with the usual extremely high ping spikes and shots not registering. So it is a Halo thing. Not only is it a Halo thing, when I’m paired with friends from the West Coast and get on a server 3 times further than the ones I normally play on, the ping spikes are minimal and the gameplay is more consistent. I’m in the Detroit area and the gameplay experience is significantly worse playing on a Chicago server than a California server. When I’m playing people that don’t speak English on a East Coast server, it feels like I’m hitting a server on the moon.
So by the mounting evidence, the people furthest from the server tend to be having better performance meaning…343’s lag compensation is far too aggressive. This is why as the population has decreased, more people have complained about the aiming.
This doesn’t seem to effect everyone evenly which is the mystery. If 343 isn’t planning on re-writing the netcode for Halo 6, we need to solve the issue. I’ve been saying for a long time that many of the people who quit not believing in the matchmaking or controls were really having inconsistent performance issues and didn’t understand latency. Maybe there is something some ISPs are doing that is throwing 343’s netcode out of whack but it’s not an issue of the ISP getting crowded.