Apex Legends input lag changes from day to day

[bleya99]

Guys pls stop with this BS. there is no magic or hidden script which makes your overall ingame performance better. like all the people in Fifa who believes on "Momentum" pls activate your human logical brain. the only thing which can change during the time or day, is it the internet. based on how many people arround your area using it in the same time. mainly when they are back from the work, or its weekend.

This is the only thing which can change or for some people the "electricity input lag" what ever.

Pls for the sake of love, stop with this rumors/theories about illuminati changing my profil settings. if you really thinking about it in a logical way, like do you really think that DEV's would make such effort to put something like this in ? Besides of matchmaking which is real, but everything else is .... yeah what do you want to call it

It's hard to think it's placebo when the change happened right before my eyes. Again, this is only 1 set of problems, which might not affect some other desync or your own agenda you have with ethernet being the problem. My main account felt like I was playing with 100 fps and the alt acc really felt like 144hz. Once I deleted the userdata files, the main account is smooth again, the normal sensitivity is back (like on my alt acc) and it's smoother like it's supposed to be. As I've mentioned in my other post, disproving ideas is 100% neccessary, but just because 1 thing does not affect you (or you think it doesn't) does not prove it's not true for everyone. Also, I would like to hear opinions on the people from the post if this particular "fix" helped them in any shape or form.

[Raphaeangelo]

I want to emphasize that this issue isn't related to a placebo effect, nor is it a network or PC problem. When I switch to different resolutions, I can see the hit registration changing right in front of me.

To those who doubt this, I urge you to try my steps in the firing range and see for yourselves. I've lost count of the number of times people have dismissed this as "BS" without actually investigating the issue. I understand that if you only play the game casually, you might not notice anything amiss, but for those who can sense that something is off and have spent countless hours testing, we know that something isn't right. This discussion is aimed at identifying the issue, not debating its existence. We already know there is a problem.

One other interesting thing I've noticed is that when I switch to a different resolution in the game, I experience lag/desync error icons in the upper right corner for a few seconds after the switch. Why would the Apex servers give me network errors when I change the resolution? Why do the servers need to know what resolution I'm using?

[Raphaeangelo]

DISCLAIMER: This is only speculation based off of tests and observations but I think I have enough evidence to support these claims.

You're not alone. I have a high-end rig (13900K, 4090 FE, DDR5 7400 tight timings, performance tweaked PC & settings) and notice significant inconsistencies in perceived (end result / all-encompassing) mouse sensitivity and feel.
It's extremely unlikely that EA is actively trying to degrade or alter performance/consistency because that actually works against them for various reasons that we don't need to discuss but can if you'd like to. The following high-level explanation is actually what's happening.

Thanks for the detailed response. I understand that different settings can produce different results, some good and some bad. This is true for all games. What I find interesting about Apex is that when I change resolutions, I get better hit registration, but only for one day. The next day, I experience bad hit registration and desynchronization on the resolution that was giving good results the previous day. Every day, I need to switch to a different resolution to achieve good results. This doesn't make sense because some days it's with a low resolution and some days with a high resolution.

[howiec]

Thanks for the detailed response. I understand that different settings can produce different results, some good and some bad. This is true for all games. What I find interesting about Apex is that when I change resolutions, I get better hit registration, but only for one day. The next day, I experience bad hit registration and desynchronization on the resolution that was giving good results the previous day.

So no offense at all but per my post, I explained from a high level view why Apex is very different (way worse) than a well-designed or well-optimized game running on a modern engine.

Changing resolutions has a major impact on on both CPU and GPU loads so obviously that will have a major impact on your perceived aim sensitivity.
However, again, you're only looking at a single input factor in the equation.
I'm explaining why that even when you keep all settings the same, something as simple as running different apps/services in the background places a different load on the PC which in turn affects your end / perceived aim sensitivity.

Don't forget about the fact that there is a serious problem when mouse and controller settings, and each individual sensitivity scalar all affect each other and affects overall sensitivities... that points to a major underlying flaw(s).

Sure, no modern game is perfect when it comes to providing consistent aim and sensitivity regardless of the "load" (within reason).
However, Apex clearly has major consistency problems regarding internal aim / sensitivity calculations because it is obvious that it is highly sensitive to even the smallest of overall performance variation even after various attempted mitigations, e.g., internally and/or externally capped frame rate(s).

We can't know for sure exactly what's going on without source code analysis done by people with expertise but anyone can do simple tests that clearly and objectively show that there is a serious problem.

I can only deduce that Apex does the following (which is 100% verifiable & 100% reproducible):
Somehow the devs (or the shitty old engine) did not adequately decouple aim/sensitivity calculations from other variations in engine processes or references such as the rendering pipeline, internal timers/clocks, etc.
The degree of angle change per unit of "real-world" time is fundamentally not aligned with some internal timing/calculation mechanism which is clearly heavily dependent on the rendering pipeline and load and/or other systems. Hence you get a ton of variation even when everything from your PC system perspective stays the same and yet different maps lead to different perceived sensitivity (e.g., firing range vs WE vs BM).

Here are just a few example settings out of many that may allude to how poorly implemented aim/sensitivity is in Apex and how easily it is affected by other poorly implemented systems in the game.
Oh and even with stuff like DVS disabled, you'd think that the relevant variables would have no effect on aim sens but due to shitty code/engine they actually do...

• dvs_gpuframetime_min
• r_dxgi_max_frame_latency
• gamepad_custom_hip_turn_delay (also affects effective MnK sens...)
• gamepad_custom_ads_turn_time (also affects effective MnK sens...)

Now here's the painful truth.
Respawn is not going to fix major underlying issues that would require major code refactoring because the game is already highly profitable, is relatively mature, and the best devs are likely working on new projects.
So unfortunately Apex is fucked forever in this regard.

The only thing you can do is know how to tweak the settings to find the best middle-ground and know for a fact that even if all of your settings, OS, and hardware remain the same, even running something like Spotify music playing in the background will change your perceived aim/sens in Apex!

[Raphaeangelo]

I spent around 5 hours playing COD MW3 yesterday, and I didn't encounter any lag or desync issues. The game felt very responsive and consistent. After this experience, I'm convinced that the issues I'm facing are specific to Apex and not related to my PC settings.

I have some questions about how client-server communications work in Apex. I don't understand why the Apex servers are concerned about the resolution I am using. Every time I change my resolution in-game or in the firing range, I experience network errors for a few seconds until the server updates the information about my resolution. This seems unnecessary, as the resolution should be a client-side setting and should not impact the server's operations. In contrast, when I change my resolution in COD, the only thing that changes is my resolution. In my opinion, Apex clients send too much unnecessary data to the servers, leading to inconsistent gameplay. It feels like most of the game's processing is done on the server, which is problematic, especially when the servers are full or if there are connectivity issues. First-person shooters are supposed to have a stable client-side experience. While I understand that there will always be some server-side variables, the game should rely less on the server. The client should handle as much of the workload as possible. At this point, I'm considering taking a break from Apex. Although I love the game, the unreliable nature of the gameplay experience is making me reconsider playing it. A competitive shooter should offer a stable and consistent experience. If Apex aims to be a leading esports title, it needs to address these issues. I believe that the issues with Apex are inherent in its design, and I'm not optimistic about a quick resolution.

[ApexLeg]

I spent around 5 hours playing COD MW3 yesterday, and I didn't encounter any lag or desync issues. The game felt very responsive and consistent. After this experience, I'm convinced that the issues I'm facing are specific to Apex and not related to my PC settings.

I have some questions about how client-server communications work in Apex. I don't understand why the Apex servers are concerned about the resolution I am using. Every time I change my resolution in-game or in the firing range, I experience network errors for a few seconds until the server updates the information about my resolution. This seems unnecessary, as the resolution should be a client-side setting and should not impact the server's operations. In contrast, when I change my resolution in COD, the only thing that changes is my resolution. In my opinion, Apex clients send too much unnecessary data to the servers, leading to inconsistent gameplay. It feels like most of the game's processing is done on the server, which is problematic, especially when the servers are full or if there are connectivity issues. First-person shooters are supposed to have a stable client-side experience. While I understand that there will always be some server-side variables, the game should rely less on the server. The client should handle as much of the workload as possible. At this point, I'm considering taking a break from Apex. Although I love the game, the unreliable nature of the gameplay experience is making me reconsider playing it. A competitive shooter should offer a stable and consistent experience. If Apex aims to be a leading esports title, it needs to address these issues. I believe that the issues with Apex are inherent in its design, and I'm not optimistic about a quick resolution.

That's what I find too - at the start of the firing range it's saying 165fps but the red icons are showing in the top right and it's stuttering, eventually goes away.

And if I change resolution too I get the same icons for a few seconds and if I hit the dummies I get hit markers but no damage.

[Raphaeangelo]

That's what I find too - at the start of the firing range it's saying 165fps but the red icons are showing in the top right and it's stuttering, eventually goes away.

And if I change resolution too I get the same icons for a few seconds and if I hit the dummies I get hit markers but no damage.

Exactly! So why does Apex's servers need to know my client's resolution? I've noticed that the game's movement is controlled by the servers too. When I lose connection to the server, Apex freezes and I can't move at all. To test this, go to the firing range and disconnect the Ethernet – you'll stand still. I believe that movement should be processed on the client, and the client should update the server on its position. The client should handle movement, shooting, and damage, while the server captures and processes this data to update other players. Currently, it feels like Apex relies too much on the server, and the client only handles rendering the graphics. This setup reminds me of streaming game services like Google Stadia, which were horribly delayed and desynced. Apex seems to be doing something similar, with the servers handling most of the game mechanics while the client is just along for the ride. I think shifting more of these processes to the client would help reduce the delays and desyncs caused by server reliance.

[ApexLeg]

That's what I find too - at the start of the firing range it's saying 165fps but the red icons are showing in the top right and it's stuttering, eventually goes away.

And if I change resolution too I get the same icons for a few seconds and if I hit the dummies I get hit markers but no damage.

Exactly! So why does Apex's servers need to know my client's resolution? I've noticed that the game's movement is controlled by the servers too. When I lose connection to the server, Apex freezes and I can't move at all. To test this, go to the firing range and disconnect the Ethernet – you'll stand still. I believe that movement should be processed on the client, and the client should update the server on its position. The client should handle movement, shooting, and damage, while the server captures and processes this data to update other players. Currently, it feels like Apex relies too much on the server, and the client only handles rendering the graphics. This setup reminds me of streaming game services like Google Stadia, which were horribly delayed and desynced. Apex seems to be doing something similar, with the servers handling most of the game mechanics while the client is just along for the ride. I think shifting more of these processes to the client would help reduce the delays and desyncs caused by server reliance.

It's odd how it handles it but I still believe ISP routing/CGnat issues are the main causes. When it's bad I can tell instantly because enemies move erratically and I can't track them, also my screen shakes like crazy when I'm getting shot because I'm receiving lots of hit markers in one go and I can barely see the enemy. On the rare days it's good, the it's like playing a different game.

[Unreazz]

I spent around 5 hours playing COD MW3 yesterday, and I didn't encounter any lag or desync issues. The game felt very responsive and consistent. After this experience, I'm convinced that the issues I'm facing are specific to Apex and not related to my PC settings.

I have some questions about how client-server communications work in Apex. I don't understand why the Apex servers are concerned about the resolution I am using. Every time I change my resolution in-game or in the firing range, I experience network errors for a few seconds until the server updates the information about my resolution. This seems unnecessary, as the resolution should be a client-side setting and should not impact the server's operations. In contrast, when I change my resolution in COD, the only thing that changes is my resolution. In my opinion, Apex clients send too much unnecessary data to the servers, leading to inconsistent gameplay. It feels like most of the game's processing is done on the server, which is problematic, especially when the servers are full or if there are connectivity issues. First-person shooters are supposed to have a stable client-side experience. While I understand that there will always be some server-side variables, the game should rely less on the server. The client should handle as much of the workload as possible. At this point, I'm considering taking a break from Apex. Although I love the game, the unreliable nature of the gameplay experience is making me reconsider playing it. A competitive shooter should offer a stable and consistent experience. If Apex aims to be a leading esports title, it needs to address these issues. I believe that the issues with Apex are inherent in its design, and I'm not optimistic about a quick resolution.

on a resoloution change its normal that the game notifies you, that you have network lag, because on that small period time, you encounter a LAG, its a system lag, cause you paused the game for a moment, while you are on a live session. its the same as, when you are on a match and the CPU is highly overloaded, you get a freeze for a second, the game will think, that you lag and you receive also a notification, till to the point where server and client are synced again and the game notices that you are back.

if you make the game stop for a moment, which you can test by yourself (Just go to the exe and deactivate some cores) i guarantee you, you also get the same error codes

so in this case, this means NOTHING. This happens in every game, if you encounter a network or even a system "Cliend sided" Lag

[Raphaeangelo]

on a resoloution change its normal that the game notifies you, that you have network lag, because on that small period time, you encounter a LAG, its a system lag, cause you paused the game for a moment, while you are on a live session. its the same as, when you are on a match and the CPU is highly overloaded, you get a freeze for a second, the game will think, that you lag and you receive also a notification, till to the point where server and client are synced again and the game notices that you are back.

if you make the game stop for a moment, which you can test by yourself (Just go to the exe and deactivate some cores) i guarantee you, you also get the same error codes

so in this case, this means NOTHING. This happens in every game, if you encounter a network or even a system "Cliend sided" Lag

I understand. still, why do I get better input lag, hit detection and aim assist on different resolutions on different days? Makes zero sense.