Hey community,since a couple of days (it started with the launch of S22), Apex just feels...strange.For me, It takes f.e. a full Flatline-mag to down my opponents - I (on the other hand) keep getting downed with just 2 or 3 shots. Shots that shouldn't have hit me at all since I already was behind cover. I´m getting beamed again and again.In the killcam I can see that I was standing in a hail of bullets for like 2 seconds before I was finally downed - a typical netcode-problem.Apex has been reinstalled just to make sure, the prob was not on my side but: no change so far.So Respawn: Please fix your game!Anyone else?

@W3stminst3rI've also had a few no regs where you could see the hit & it made the sound effect of the hit, but no damage was done. Had it with several different guns. If I experience it again I will record it.

@W3stminst3rYeah, it's been bad. If you played Battlefield 3, this feels way too familiar. That game had infamously bad netcode and the same things happened. Shot behind cover, no regs, seeing/hearing 1 or 2 shots hit but the game telling you 9 hit you, instant death where the bullets seems to hit you after you died and the bullets seemingly caught up to you somehow. It's all happening in Apex more and more since the start of S22.

My bet is the information flow of the game simply got "overloaded" over the seasons, resulting in weird network conditions.My buddies and i worked on a Quake3 modification back in the days and it happend to us that we put in more game-info than the actual allowed packet size and as a result packets got fragmented. not ideal for a fast pace ego shooter game one could say.Afaik Apex splits that info into several packets as a "super packet" (based on Battle(non)sense video about the Apex netcode).if one "fragment" gets lost, all the info gets lost, since the super packet cannot be rebuilt in full on the server/client.

I've been noticing it mostly when shooting a players mantling. It's like they become invincible while climbing up a ledge.

S22 - Suddenly, Apex feels weird (netcode, no-regs etc.)

14 Replies

Lord_Scorpion34
Legend
2 years ago
@W3stminst3rI've also had a few no regs where you could see the hit & it made the sound effect of the hit, but no damage was done. Had it with several different guns. If I experience it again I will record it.
EPS1234
Seasoned Veteran
2 years ago
Ya it’s terrible
Ncessant
Rising Vanguard
2 years ago
I've been noticing it mostly when shooting a players mantling. It's like they become invincible while climbing up a ledge.
W3stminst3r
Seasoned Ace
2 years ago
Something is clearly wrong here: This Revival-Mode feels like a low-HP-mode.
I`m still getting one-shotted!
RaginSam
Seasoned Ace
2 years ago
@W3stminst3r It's been trash for a long time. The time it takes to receive damage, versus giving damage is not on the same timeline. There's huge desync issues, or people are cheating and found a way to manipulate the network. Or maybe some people just win the online connection lottery.

Every time I spectate a high level player, it seems like everyone is slow to react to them, like everyone is behind them on the server.

When you are fighting other people, you have to assume that you've already taken damage that hasn't registered yet. If you wait to move after you've taken damage, you have taken 3x the amount should be possible in that given time.

I've even see people standing still sometimes taking damage. The server locks you in place.

This game does anything but address the core issues.
reconzero
Seasoned Ace
2 years ago
@RaginSam

"Or maybe some people just win the online connection lottery."

This has been a working theory of mine for going on 15 years now, since Halo 3. I would love to see stats of players who live two miles away from a server vs. stats for players who live two states away. But no, we'll never see that data because it would undermine confidence in online gaming. As if that hadn't already happened decades ago. The truth is that until someone invents an actual ansible then the internet as we know it is just not capable of dealing with the 1/100th-of-a-second precision required by competitive multiplayer shooters.
W3stminst3r
Seasoned Ace
2 years ago
After having played around 5 more matches, I can now say: Something is clearly wrong with the TTK (or many players use no hacks atm).
At least in the new revival-mode it is dramatic!
I´m fully purple equipped, push a guy that was totally one-shot.
He comes out from behind his cover and beams me away within 2 seconds.
I know "my" game since I started playing Apex with Saison 1 and it has never felt this way.
Is there an official statement regarding possible TTK-issues?
HappyHourSumwur
Seasoned Ace
2 years ago
@W3stminst3rYeah, it's been bad. If you played Battlefield 3, this feels way too familiar. That game had infamously bad netcode and the same things happened. Shot behind cover, no regs, seeing/hearing 1 or 2 shots hit but the game telling you 9 hit you, instant death where the bullets seems to hit you after you died and the bullets seemingly caught up to you somehow. It's all happening in Apex more and more since the start of S22.
W3stminst3r
Seasoned Ace
2 years ago
Do we get an offcial statement on this?
Something is not right with the TTK in the revival-mode! I´m pretty sure they * something up here.
r1ggedgame
Seasoned Ace
2 years ago
My bet is the information flow of the game simply got "overloaded" over the seasons, resulting in weird network conditions.
My buddies and i worked on a Quake3 modification back in the days and it happend to us that we put in more game-info than the actual allowed packet size and as a result packets got fragmented. not ideal for a fast pace ego shooter game one could say.
Afaik Apex splits that info into several packets as a "super packet" (based on Battle(non)sense video about the Apex netcode).
if one "fragment" gets lost, all the info gets lost, since the super packet cannot be rebuilt in full on the server/client.