About the latency/routing issue in FC 27
I want to raise an issue that many players from Southern and Eastern Europe have already experienced in FC 26 — and I am concerned that we are going to see exactly the same situation in FC 27. In FC 26, players reported a significant deterioration in latency and gameplay quality after the July 29th server maintenance. The issue was particularly noticeable for players in Romania, Ukraine and other parts of Eastern/Southeastern Europe. This is not simply a case of having a “bad internet connection”. In the existing FC 26 thread, EA Community Manager Darko confirmed that the issue had been raised with the team and was being investigated. However, almost two months later, we still have no clear explanation, no technical details and, most importantly, no indication of when or how the issue will actually be resolved. The thread is still active, and players are continuing to report the same problem: https://forums.ea.com/discussions/fc-26-technical-issues-en/severe-latency-degradation-in-romania-after-july-29th-maintenance/13610423 I have also posted several times in that thread, asking a very simple question: What are players supposed to do if they live far away from the servers or are affected by poor regional routing? Are we expected to solve the problem ourselves by paying for third-party connection-routing services such as GearUP, WTFast, ExitLag, Surfshark or similar services — on top of already paying for the game and online services? In my own case, using an alternative routing service can significantly improve the route and gameplay experience. That is important evidence that the problem is not necessarily my local connection or hardware. The difference can be the route used to reach EA's infrastructure. I don't think the solution should be that players in Eastern or Southern Europe have to pay an additional monthly subscription to third-party services just to get a reasonable gameplay experience. Players who live close to EA data centers can often get 10–20 ms connections. Players who are geographically farther away obviously cannot expect identical latency. But there is a very important difference between naturally higher latency because of distance and unnecessarily poor routing to the available EA servers. This is exactly what I am asking EA to clarify for FC 27: Has the routing/matchmaking issue affecting parts of Eastern and Southern Europe actually been identified? Has anything been changed in FC 27 to prevent the same problem from happening again? How does EA handle players who are geographically distant from the available data centers? Are there plans to improve regional routing or matchmaking server selection? And most importantly: will EA provide an actual technical explanation and update to the affected community? We are not asking for impossible 10 ms ping from every country. We are asking for a fair and technically reasonable connection to the servers available to us. Please don't let FC 27 repeat the same situation we experienced in FC 26. Eastern and Southern European players deserve an answer before this becomes another year-long problem. upd: I’ve seen several threads on the forum about a similar issue from various regions, not just Europe.
SLIDERS AND VARIOUS CAREER MODE BUGS
In Career Mode, the sliders do not seem to work properly!!!! The AI is poor and does not defend properly, goalkeepers do not come off their line in one-on-one situations, and the +1 attributes earned from activities are not being added to the player's attributes. The referees also give unnecessary fouls, while the opposing team constantly commits fouls. The AI teams also seem to play in the same way and lack variety in their gameplay. Even on Ultimate difficulty, the game does not feel challenging enough. I suspect this may be related to the sliders not functioning correctly. Please investigate these issues, especially the Career Mode sliders, AI defending, goalkeeper behavior, activity-based attribute boosts, refereeing, AI gameplay variety and small mistakes we cannot count.
FC27 PC: DualShock 4 Stops Working on Bluetooth When Game Starts
Hello EA Support, I am experiencing a controller issue in EA SPORTS FC 27 on PC. I am using a genuine Sony DualShock 4 controller. Windows detects the controller as "Wireless Controller". The problem happens specifically when I use the controller over Bluetooth and start FC 27. When the controller is connected to Windows through Bluetooth, Windows detects it normally. I can use the controller in Windows settings, and joy.cpl detects it correctly. The controller status is shown as "OK". The buttons and analog controls are detected normally. However, when I launch EA SPORTS FC 27, the controller light turns off and the controller stops responding correctly in the game.The important part is that the same controller works normally when connected with a USB cable. With USB cable: The controller works normally in FC 27. All buttons and analog controls work. I can fully control the game. The controller light behaves normally. With Bluetooth: Windows detects the controller normally. joy.cpl detects the controller normally and shows "OK". FC 27 launches. When the game starts, the controller light turns off. The controller then does not work correctly in the game. I have already performed extensive troubleshooting. I tested the controller in Windows. It is detected as Wireless Controller and works normally in Windows. joy.cpl also detects it correctly. I tested the same DualShock 4 using a USB cable. FC 27 works normally with USB. I tested the same controller and the same old Bluetooth dongle on another PC. FC 27 worked correctly over Bluetooth on that other PC. I replaced my old Bluetooth dongle with a brand new TP-Link UB500 Bluetooth 5.4 USB Adapter. I installed the official TP-Link driver. Windows detects the adapter correctly and Device Manager reports that the device is working properly. I removed and re-paired the Wireless Controller through Bluetooth. The controller pairs successfully and works normally in Windows. I completely reset Windows. I selected "Remove everything" and also selected the option to clean the drive. After the reset, I set up Windows as a new PC and did not restore my previous Microsoft backup or settings. The problem still happens on the completely fresh Windows installation. I also reinstalled the necessary motherboard, chipset, network, audio and NVIDIA drivers, as well as the official TP-Link UB500 driver. I checked the Microsoft GameInput service as well. Changing its startup behavior did not solve the Bluetooth problem. I also checked the Bluetooth adapter power management settings and disabled the option that allows Windows to turn off the adapter to save power. I restarted the PC and tested FC 27 again, but the same problem remained. I checked the TP-Link adapter in Device Manager. There are no warning icons or driver errors. Its status says that the device is working properly. I also tested another controller with the previous Bluetooth adapter, and FC 27 still showed abnormal controller behavior. The most important comparison is: Same controller + Bluetooth + another PC + FC 27 = works normally. My PC + same controller + USB + FC 27 = works normally. My PC + Bluetooth + FC 27 = controller stops working when the game starts. Fresh Windows installation + new TP-Link UB500 + Bluetooth controller + FC 27 = same problem. Because the controller works correctly through USB, works correctly in Windows, works correctly in joy.cpl, and also works correctly over Bluetooth with FC 27 on another PC, I believe this may be related to how FC 27 handles the Bluetooth/HID controller connection on my PC. I would like to know if this is a known FC 27 issue with DualShock 4 controllers over Bluetooth on Windows 11. Could you please investigate DualShock 4 Bluetooth controller detection, Bluetooth HID input handling, FC 27 taking control of the Bluetooth controller when the game starts, and possible controller profile or input device issues? I would also like to know whether this is a known FC 27 bug that may be fixed in a future update or patch. I have already replaced the Bluetooth adapter, completely reset Windows, reinstalled drivers, re-paired the controller, tested USB, tested another controller, tested the same controller on another PC, and verified the controller through Windows and joy.cpl. At this point, the problem only appears when FC 27 starts while the DualShock 4 is connected through Bluetooth on my PC. Please let me know if this is a known issue and whether it is being investigated for a future update. Additional information: The controller is a genuine Sony DualShock 4 and has been working normally for a long time. The issue started after I began having problems with FC 27 and Bluetooth controller input. The controller and Bluetooth hardware were not newly purchased because of this issue; they had already been working successfully before. I am using the EA App version of FC 27, not Steam. I am not using Steam Input or any controller emulation software. The issue is reproducible: when the DualShock 4 is connected through Bluetooth before launching FC 27, the controller works normally in Windows, but when FC 27 starts, the controller light turns off and the controller stops responding correctly. USB connection continues to work normally. I would appreciate it if the technical team could investigate this specifically as a Bluetooth controller detection/input issue in FC 27. PC specifications: Operating System: Windows 11 CPU: AMD Ryzen 5 7600 Motherboard: MSI PRO A620M-E RAM: Kingston DDR5 16GB 5600MHz GPU: MSI RTX 4060 VENTUS 2X BLACK 8G GDDR6 8GB Bluetooth Adapter: TP-Link UB500 Bluetooth 5.4 USB Adapter Controller: Sony DualShock 4 Launcher: EA App IMPORTANT: I understand that for some people this may simply be a video game, but for me EA SPORTS FC has been much more than that. I have been playing the series since 2020 and I have spent many years building memories, improving my skills, following each new release and enjoying the game with friends and the community. That is why this issue is especially frustrating for me. I have been looking forward to FC 27 and I want to be able to enjoy the game normally, using the controller setup that I have used for years. I understand that FC 27 is a newly released game and that some technical issues can happen after launch. I am not expecting everything to be perfect, but I would really appreciate it if this particular issue could be investigated and, if it is a game-side bug, addressed in a future update. PLEASE HELP!! I also tested EA SPORTS FC 26 on the same PC using the same DualShock 4 controller and the same Bluetooth setup. FC 26 works perfectly over Bluetooth. The controller light stays on normally, all buttons and analog controls work correctly, and I can play the game without any issues. There are no controller or Bluetooth problems in FC 26. The problem only occurs in FC 27. This is an important comparison because I am using the same PC, the same Windows installation, the same Bluetooth adapter and the same DualShock 4 controller. FC 26: Bluetooth controller works perfectly. FC 27: Bluetooth controller stops working when the game starts and the controller light turns off. Based on all of these tests, the issue appears to be specifically related to FC 27 rather than my controller, Bluetooth adapter or Windows configuration. I have been looking forward to FC27 with great excitement and high expectations, and I even pre-ordered the game because I genuinely wanted to experience the new release from day one. That is why facing an issue like this, especially with a controller setup that has worked for years, is honestly very disappointing. I sincerely hope EA can investigate this issue and provide a solution as soon as possible. I just want to enjoy the game I was so excited to play. PLEASE !!FC 27 PC: DualShock 4 Stops Working on Bluetooth When Game Starts
Hello EA Support, I am experiencing a controller issue in EA SPORTS FC 27 on PC. I am using a Sony DualShock 4 controller. Windows detects the controller as "Wireless Controller". The problem happens specifically when I use the controller over Bluetooth and start FC 27. When the controller is connected to Windows through Bluetooth, Windows detects it normally. I can use the controller in Windows settings, and joy.cpl detects it correctly. The controller status is shown as "OK". The buttons and analog controls are detected normally. However, when I launch EA SPORTS FC 27, the controller light turns off and the controller stops responding correctly in the game. The important part is that the same controller works normally when connected with a USB cable. With USB: The controller works normally in FC 27. All buttons and analog controls work. I can fully control the game. The controller light behaves normally. With Bluetooth: Windows detects the controller normally. joy.cpl detects the controller normally and shows "OK". FC 27 launches. When the game starts, the controller light turns off. The controller then does not work correctly in the game. I have already performed extensive troubleshooting. I tested the controller in Windows. It is detected as Wireless Controller and works normally in Windows. joy.cpl also detects it correctly. I tested the same DualShock 4 using a USB cable. FC 27 works normally with USB. I tested the same controller and the same old Bluetooth dongle on another PC. FC 27 worked correctly over Bluetooth on that other PC. I replaced my old Bluetooth dongle with a brand new TP-Link UB500 Bluetooth 5.4 USB Adapter. I installed the official TP-Link driver. Windows detects the adapter correctly and Device Manager reports that the device is working properly. I removed and re-paired the Wireless Controller through Bluetooth. The controller pairs successfully and works normally in Windows. I completely reset Windows. I selected "Remove everything" and also selected the option to clean the drive. After the reset, I set up Windows as a new PC and did not restore my previous Microsoft backup or settings. The problem still happens on the completely fresh Windows installation. I also reinstalled the necessary motherboard, chipset, network, audio and NVIDIA drivers, as well as the official TP-Link UB500 driver. I checked the Microsoft GameInput service as well. Changing its startup behavior did not solve the Bluetooth problem. I also checked the Bluetooth adapter power management settings and disabled the option that allows Windows to turn off the adapter to save power. I restarted the PC and tested FC 27 again, but the same problem remained. I checked the TP-Link adapter in Device Manager. There are no warning icons or driver errors. Its status says that the device is working properly. I also tested another controller with the previous Bluetooth adapter, and FC 27 still showed abnormal controller behavior. The most important comparison is: Same controller + Bluetooth + another PC + FC 27 = works normally. My PC + same controller + USB + FC 27 = works normally. My PC + Bluetooth + FC 27 = controller stops working when the game starts. Fresh Windows installation + new TP-Link UB500 + Bluetooth controller + FC 27 = same problem. Because the controller works correctly through USB, works correctly in Windows, works correctly in joy.cpl, and also works correctly over Bluetooth with FC 27 on another PC, I believe this may be related to how FC 27 handles the Bluetooth/HID controller connection on my PC. I would like to know if this is a known FC 27 issue with DualShock 4 controllers over Bluetooth on Windows 11. Could you please investigate DualShock 4 Bluetooth controller detection, Bluetooth HID input handling, FC 27 taking control of the Bluetooth controller when the game starts, and possible controller profile or input device issues? I would also like to know whether this is a known FC 27 bug that may be fixed in a future update or patch. I have already replaced the Bluetooth adapter, completely reset Windows, reinstalled drivers, re-paired the controller, tested USB, tested another controller, tested the same controller on another PC, and verified the controller through Windows and joy.cpl. At this point, the problem only appears when FC 27 starts while the DualShock 4 is connected through Bluetooth on my PC. Please let me know if this is a known issue and whether it is being investigated for a future update. Thank you for your help.FC 27 Kuwait – Ping Increased from 25–35ms to 55–65ms | Middle East
Hello EA Support, I'm playing EA SPORTS FC 27 on PS5 from Kuwait, using Ooredoo 5G with an Ethernet connection. In FC 26, my ping was consistently 25–35ms. However, since the first day of FC 27, my ping has increased to 55–65ms across all online modes, including Ultimate Team Draft. I have tested multiple matches, and the latency remains consistently high. A friend of mine in Kuwait using Zain also experiences similar ping, despite playing separately on a different internet connection. My connection tests show that I can achieve approximately 20ms latency to Cloudflare, with no significant packet loss. However, FC 27 consistently connects at 55–65ms. Could an EA representative please clarify: 1. Which game data center are players in Kuwait currently connecting to in FC 27? 2. Are the Dammam (Saudi Arabia), Manama (Bahrain), and Dubai (UAE) game data centers currently operational and available for FC 27 matchmaking? 3. Has there been any change to Middle East matchmaking, data center availability, or server routing compared with FC 26? 4. Is EA aware of increased latency affecting players in Kuwait and other Gulf countries, and are there any planned fixes? I would appreciate a response specifically addressing the game data center availability and routing, rather than general home network troubleshooting. Thank you.Please bring back manual player-switching key customization for keyboard
I’m a keyboard player and in previous FIFA/FC games I always used custom keys for manual player switching. I would go into the settings and assign the keys myself. In FC 27 I can’t do that anymore, and I’m having a hard time getting used to the new setup. On controller, manual switching is done with the Right Stick, so for keyboard players we really need to be able to choose which keys do it. I don’t understand why this was changed.
PC FC27 BROKEN
EA_EduEA_Mai Soon as shaders loads my game black screens it’s not a pc Issue as I launch about 6 games like Rocket league FC26 Black ops 3 Black ops 7 Warzone no issues no stutters nothing just can’t launch Fc27 I got on through administrator for about a hour i have deleted Javelin and repaired about 100 times through administrator to so it’s no issue for that I don’t have any other AC downloaded how can this be a issue in 2027 I have a I7-14000k and a AMD Radeon rx 7090 XT it’s not rubbish gear or Low end everything is upto date as I have no other issues on any game it’s clearly FC27 any commentsEA_DanaBEA_DennisEA_DmitryiEA_Nazul
The player I am controlling stops running and stands still.
For years, I’ve been used to pressing the sprint button to apply pressure. But in FC27, when I press the sprint button, the player I’m controlling just freezes—standing still for 2–3 seconds—and the opponent takes advantage of it to run forward toward the goal.