Netcode Problem - Incorrectly Shuttering Players

Since Halo 5 has launched, I’ve spent an insane amount of time investigating why I get inconsistently shuttered in games causing shots not to register. This problem doesn’t impact the entire community but it’s also not uncommon. Some people are impacted more frequently than others.

I understand the theory behind shuttering players. It makes it useless to be a lag switcher or cheater. Problem is by not correctly identifying the problem children, 343 has lots of collateral damage within their community.

After switching between 2 ISPs 4 times, using 3 different router and modem combinations, using ping plotter, netduma, getting both ISPs to monitor ping issues within network and conversing with a lot of networking people online, the issue isn’t with my ISPs, the equipment or network. Same goes for much of the community. Halo 5 either has issues with some of the Microsoft servers or netcode. 343 continues to deny it on these forums but through process of elimination, there are no other answers. 343 aggressively shutters players where other AAA online games do not. I think much of the community would agree that it would be better to deal with the occasional rubber bander or lag switcher than consistently deal with getting shuttered in most games.

If 343 is not re-writing netcode for Halo 6, gamers who don’t understand online performance are going to once again assume there’s issues with the aiming or controls. It’s past time to engage with the community and look into this issue. For the past 2.5 years, the canned response is to have us call our ISPs knowing that the major ISPs cannot do anything outside their network. Will 343 ever take their online performance issues seriously? You guys aren’t some small Indie team. This is Microsoft’s biggest IP. Making mistakes is one thing but your insincere responses to your mistakes are not going to help bring Halo’s brand back.