devtrackers.gg
[deleted]
[deleted]
Status is that it's in progress. It's unfortunately a complex issue that is, thankfully, on track to being resolved, but takes time. We know it's one of the biggest areas of frustration for players and the team is tackling as quickly as possible. We'll try and dig into more of the technical details and background after the break.
halo reach has inverse flinch where being shot will draw your crosshair towards the opponent
this directly helps controller users and kept f**king up the aim of kbm who keep overcompensating when the game moves ur crosshair
hopefully this is actually fixed
Definitley a strange mechanic that was present in the OG Reach and something our internal Pro Team really honed in on during pre-release testing. Initial reports are positive, but we'd love to hear feedback from M+KB users on how this change feels.
I think so, yeah. I never even knew it existed until someone shared a video a few days ago.
Same here and this is legacy code from 2010. It became much more egregious and noticeable on M+KB I think. Our internal pro team brought this to light a few weeks back and the community at large seems to have just picked up on this earlier this week - just in time for this patch to address it. :)
Is it worse than OG Reach? OG Reach was notoriously bad and 343 mentioned that there wasn’t much they were going to do about it.
It's a pretty hard problem to solve given the underlying campaign networking architecture is very old. Re-doing all of that is a signficant undertaking (much more complex that the work that was done for MP, dedicated server support for Firefight, etc.). Not sure there's _nothing_ the team can do, they've heard the feedback and would like to find opportunities to improve, but real talk there's no magic solution and anything would be a massive reworking of the entire netcode for a 9 year old game.