Apex Netcode Is Awful

It is pretty bad, yes.

My guess it's that they haven't accounted for the game to blow up this much. So, I am hoping they would address this ASAP.

Tick rate is around whopping TWENTY TICKS. That's insane. That's enough for plethora of problems to occur, but that's not the whole story. The actual delay between two players with normal pings is as if they had higher pings - ie, a 20 ping players battling another 20 ping player in Apex Legends results in more travel time between them than in other games.

This combo is insanely bad. But, as I said, it's impossible for them to not know that, they made the game. Now, perhaps they did think the game wouldn't be so popular, so they didn't pay attention to these structures. Now, however, it would be completely baffling if they don't treat this as a priority.

60 ticks should be a bare minimum and everything above that should be common sense target (even the "I got shot behind the wall" Overwatch has 60) and whatever infrastructure is making these huge communication times between players should be overhauled.

I am having lots of fun with the game, but this does taint the experience, regardless of whether someone REALIZES they are affected by it.

@SugoiBuruSera My biggest issue isn't even the delay in game, its the constant DC's. I haven't been able to connect and stay connected to a game all morning. Quite a few times I've had really good games going with a solid team and decent loot and the game just disconnects and crashes to the desktop. It is literally unplayable some days.

I think that's a different issue, the game is crashing for everyone, the no error crash is prevalent, for example.

Results of netcode being bad is hits not registering, enemies and teammates rubberbanding, high ping favoring etc. And yes, disconnects can be the result as well. But, I don't think crashes have anything to do with it.

letss hope they do something fast