{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
3/19/2021 5:51:52 PM
4
Honestly, the biggest issue with 120s is just Bungie’s netcode. The .2 second TTK difference is completely mitigated by the fact that latency is so bad that you can hit the .82 TTK with a 140 but because of the awful tick rate it’s closer to 1 second, effectively removing 120’s biggest drawback. This same issue applies to snipers, as flinch will frequently apply after you’re already dead since the server doesn’t register your shots even though you shoot first. If bungie actually modernized their tick rate/net code it would fix so many glaring issues in this game
English
-
I agree. Auto's have a very fast ttk but it ALWAYS feels like an uphill battle against slower firing weapons as another example. Would a better tick rate affect the games handling at all? I don't necessarily know how that stuff works.
-
Edited by Fort: 3/19/2021 7:01:39 PMYou know when you die, even though you’re SURE you’re behind a wall? That’s because of the net code, and to a smaller extent FPS. On your opponent’s screen you haven’t moved yet, so the server registers their shots even though on your end you’re completely behind cover. This also applies to stuff like sniper flinch and weapon TTK’s. Having even 60 tick servers (which games like CS did half a decade ago) would make crucible feel leagues better than it does now
-
I have a new xbox and this happens so much more than I remember it happening.
-
Yeah, you have 2-4x the FPS now which makes the game seem faster and more responsive, but also makes server side lag more apparent
