Fix lag in the Latin America region
The game stays with Lag most of the time, the joystick feels slow and heavy , players are slow and collide with each other , they miss passes, balls bounce off them , defenders just run after the opp...
Forum Discussion
I understand your point of view and you are 100% right but they are not selling an exclusivist product like I don't know, Adobe Premier, that is only for professionals. Its supposed to run on a phone. So how much is our fault or EAs fault I don't know. All I know is that if they don't do something they will start loosing customers. And I think it got worse since the release of beta version. I also saw they try to implement a new anti-cheating system. I don't know how is that affecting the servers. Do you have any ideea what are the network requirements to play the game. I see you have a lot of knowledge about network. I currently have a 150 mbs download, 30 mbs upload and latency 13.
It doesn’t matter whether it’s a game like FCM or professional software like Adobe Premiere—there are always two sides to the code. EA is responsible for the game itself (logic, design, code, AI, etc.), while OS-level issues fall to the platform developers like Apple or Android. On top of that, developers also have to account for a massive range of hardware configurations, which adds yet another layer of complexity.
The same logic applies to network issues. Some problems are on EA’s side, others on the ISP, but a significant chunk comes down to the end user's own setup. Many of the complaints seen here come from unrealistic expectations—someone buys a $200 budget phone, connects it through a cheap modem and basic Wi-Fi, and expects flawless, high-end performance. That’s just not how things work. Lower-end hardware means mid to low graphics settings, and network performance will reflect the quality of both the gear and the service. In IT and networking, better performance generally comes with better specs—and those don’t come cheap.
If actual progress is the goal, the feedback needs to be focused and actionable. Technical issues should be separated: one thread for bugs and design flaws, another for network or performance concerns. And most importantly, that feedback should be structured, backed by evidence, and include concrete examples. Throwing out blanket complaints without first ruling out issues on the user's own end doesn’t help—and it only makes it easier for the real problems to get ignored.
