Forum Discussion
Turn on your network status box in options. Watch for either large spikes in the ALAT time or a very high consistent ALAT time (compared to your latency). Also watch for noticeable spikes in the TN around the time of an XP event or your death in game. If you see either of these, it’s a thing nefarious players are doing (that we can’t talk about) that's causing it to happen.
It’s so brazen right now, they even have had audaciousness to post links back to their cloud hosted site on the EA official forums. The post in question had been up for over 5 hours and I don’t know how long after that it took a forum mod to take it down. The amount of organization being put into ruining the gameplay and griefing players is far beyond what anyone might think.
EA needs to step up the deployment of the kernel-level anti-cheat for this title as well as what they have planned for FIFA 23. Nothing in game will get better until they do. You simply can’t balance weapons or vehicles properly on the developer side that are not being used as intended because they are being manipulated by a 3rd party interaction. Most complaints on a new kernel-level anti-cheat won’t be from players seeking fair and balanced legitimate gameplay, but from nefarious users seeking to secure the easiest route to continue griefing, cheating, and breaking the gameplay.
@SeriousJuJu wrote:Turn on your network status box in options. Watch for either large spikes in the ALAT time or a very high consistent ALAT time (compared to your latency). Also watch for noticeable spikes in the TN around the time of an XP event or your death in game. If you see either of these, it’s a thing nefarious players are doing (that we can’t talk about) that's causing it to happen.
I've been testing and recording net stats while playing, and getting close to figuring out exactly what game server will be smooth and fair and what game server will be a nightmare by simply watching the network stats before and right after a game begins.
You are correct that ALAT is the main ingredient to the equation. Yet other variables play into the ALAT, as your own LAT (latency) creates issues if either too low OR too high, and it is tied back into ALAT ranges. Any chance you could PM me the "nefarious" info as the spiking ALAT one of the variables I can't seem to figure out, so knowing why it is happening will help solve the BF net code enigma.
I plan to post my findings when I'm confident I've figured out with a higher confidence what is going on and why...