Can't access the grounds, saying failed to load avatar
Everytime I try to access the grounds from main menu I get a 'failed to load avatar, returning to main menu' message , I backed out of game mid customisation and now met with that message. I have deleted all data and reinstalled the game still no luck.
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.
EA FC 27 - PC - Game crash at The Grounds 2v2 with Mbappe
Every mode besides The Grounds works without an issue, as soon as I try to do The Grounds intro and I get to the 2v2 match with Mbappe the game crashes and I get returned to desktop. The latest available driver is installed. Game was uninstalled and reinstalled. Game was installed on a different SSD. Ran the game as an administrator. Repaired the game multiple times. Disabled all overlays. None of the above fixed the issue with The Grounds intro. PC Specs: CPU - AMD Ryzen 7 9800X3D GPU - AMD Radeon RX 9070XT RAM - 32GB of DDR5 at 6000MHz - No manual OC (EXPO running) SSD - installed the game on 2 different drives PSU - Gold rated 850W (not an issue) OS - Windows 11 with the latest updates to the OS, DirectX and Visual C++ Redistributable
FC27 Clubs Middle East servers
Dear EA SPORTS FC Team, I am reporting a serious and recurring server issue affecting Clubs / The Grounds players in the Middle East region. The problem is that Middle East servers are not working properly for Clubs matchmaking in EA SPORTS FC 27. Players in the Middle East are unable to consistently find or connect to Clubs matches through the appropriate regional servers. In many cases, matchmaking fails or does not find a match, while changing to another region/server allows the match to work. What makes this issue particularly frustrating is that this is not a new problem. The same issue existed in EA SPORTS FC 26, and despite players reporting it throughout the previous game, the problem has carried over into FC 27. This is extremely disappointing. Clubs is one of the major game modes in EA SPORTS FC, and players who specifically purchase and play the game for Clubs should not be forced to use servers outside their own region just to find a match. Doing so can result in significantly higher ping, worse gameplay responsiveness, and an overall inferior online experience. EA's own documentation states that The Grounds attempts to place players in an online world that best fits their region and ping location. EA also lists Middle Eastern data centers, including Dubai, Dammam, and Manama, and identifies Clubs as a mode that uses EA game data centers. So the question is very simple: Why are Middle Eastern players still unable to reliably use the appropriate regional servers for Clubs in FC 27 when this problem was already reported in FC 26? At this point, it is difficult for players to feel that Clubs is receiving the same level of attention and technical support as other major game modes. I have already reported this issue during EA SPORTS FC 26, yet the problem has now carried over into the next title. Releasing another game while leaving a known regional server problem unresolved gives the impression that feedback from Clubs players is not being taken seriously. For many players, this is not a minor inconvenience. Clubs is the main reason they play EA SPORTS FC. If the online infrastructure required to play this mode does not work properly in their region, then there is a legitimate reason for players to reconsider purchasing future EA SPORTS FC titles. I strongly request that EA: Investigate the Middle East Clubs matchmaking/data-center routing in FC 27. Verify that Clubs matchmaking is actually utilizing the appropriate Middle East data centers. Investigate why matchmaking fails or cannot consistently find matches when players are located in the Middle East. Compare the behavior with other regions where Clubs matchmaking works normally. Provide a clear acknowledgement that this issue is being investigated rather than treating it as an individual player's connection problem. Ensure that this issue is properly addressed in a future update instead of allowing it to remain unresolved throughout another full game cycle. This issue has already existed across FC 26 and now FC 27. Players should not have to wait for another game release before EA takes this problem seriously. I hope this report reaches the appropriate technical team and that EA provides a meaningful response and a permanent solution. Thank you.FC 27 crashing/freezing mid-match on Xbox Series X/S — same issue as FC 26
Hi everyone, I’m experiencing the exact same crashing/freezing issue in FC 27 that I had throughout FC 26, and at this point it’s becoming extremely frustrating. I’m playing on an Xbox Series S. During a match, the game will suddenly freeze completely for around 3 seconds, then crash and quit straight back to the Xbox home screen. This usually happens around the second or third match, and when I restart the game, the match is counted as a loss because of the disconnection. What makes this even more frustrating is that I already reported this exact issue during FC 26. I contacted EA Support multiple times and went through the suggested troubleshooting, but the problem was never actually resolved. Now I’ve moved to FC 27 and the same problem is happening again. How is this still happening across two games? I’m not talking about an occasional crash — this has been a recurring issue that can completely ruin a match and give me a loss for something that is clearly caused by the game crashing. EA, I really need an actual explanation and solution this time. Please don’t just send the usual generic troubleshooting steps. I’ve already gone through those with support before. Is anyone else on Xbox Series S experiencing the same freezing → crash → Xbox home screen issue in FC 27? If EA staff are reading this, please acknowledge the issue and explain whether it is being investigated. I’d also appreciate any actual fix or workaround that has worked specifically for this problem. Thanks.Can't complete grounds onboarding
The onboarding fails and leave me unable to access grounds. Each time i puts me back to the UNSKIPPABLE! hunter/mbappe sequences. play the 2v2 with mbappe, get abused for wearing a hoodie, select go to grounds. The screen goes black and doesnt come back. I've tried turning all video modes down to 1080, turning off 120hz, PSSR, HDR etc. same thing happens. I recorded the gameplay where you can hear that the game is still running, but i dont know how to get past this particular element so I can get maybe to the map... Anyone else have these issues please? gameplay video... https://youtu.be/cCT4VszxEDg