tournament rewards not given
hi i came first in a tournament, the ping in the ready up area was full bars, all green, but when i the match starts in the finals, of course, it’s fixed at 230 ms. Anyway, i scored the first goal and he quit, yet i only received the notification 40 minutes after he quit, saying i came second
EA FC26 crashing on starting, black screen
I have contacted the ea help system, and after 5 hours they didn't get any answer that solved my problem, so they asked me to write in here to see if anyome else had this problem and got it solved. Basically when I opened the fc26 via ea app on pc it crashed, just appeared a black screen, then it closed and opened ea app again, I will leave a video of it attached below.
FC 25 won’t launch on Windows 11 24H2 – Splash screen crash, no error, no logs
My system GPU RTX 3080 CPU Ryzen 7 3800X OS Windows 11 Pro 24H2 Build 26100.3476 No overlays or RGB tools active All drivers and system updates are current The issue The game crashes right after the splash screen and goes back to the EA App There is no crash dump, no error, no log What I already tried - Uninstalled FC25 via EA App - Manually deleted leftover files and folders - Uninstalled and reinstalled EA App - Uninstalled and reinstalled EA AntiCheat via the official installer - Reinstalled Visual C++ Redistributables x64 and x86 - Installed DirectX End User Runtime - Ran EA App and FC25 as Administrator - Tried compatibility mode (Windows 7 and 8) - Cleared EA App cache - Created and tested a new Windows user - Closed all background apps and overlays (Razer, HyperX, MSI Afterburner, Discord, etc.) - Used DDU to reinstall NVIDIA drivers without GeForce Experience - System is fully updated - Deleted EA AntiCheat registry entry - Disabled antivirus and firewall Nothing worked. Help.
Teknik hata
FC 26 yı PlayStation üzerinden oynuyorum ve ultimate team oynuyorum maç sırasında oyuncularım karşı takımdan kat ve kat iyi olmasına rağmen adamlar beni rahat bir şekilde geçe biliyor ben oyunda ne kötüyüm ne de en üst düzey kadar iyiyim ancak benim kalecim 92 lik olmasına rağmen adamın kalecisi 85 lik nasıl her topu tutuyorsa benim kalecim her topu yiyor üstelik herşeyi 90 ea olay insanlaeı lütfen sizden ricam maç sırasında ya herkesin eşit olacağı bir eşleşme yapın yada adamları boostlatmayın benim oyuncularım iyi olmadan öncede gene 90 lık adamlar karşıma da geliyordu ve ben bile boostlanmıyoken adamları nıe bostlatıyorsunuz şu hatanızı lütfen düzeltin
Repeated “Pause Screen Locking Cheat” Incident in FC26 Champions
Video evidence: *snip* This is already the second major exploit or hack that I personally recorded in FC 26, but overall I have encountered similar suspicious incidents many times in Champions mode. At this point it has probably happened 10–20 times over the course of playing the game. I can no longer ignore this issue and decided to start documenting and publishing these incidents publicly. During this specific match, my opponent immediately paused the game right after kickoff. I already know about similar suspicious tricks from previous matches, so I intentionally waited until the pause timer expired. However, after the pause ended, my screen became stuck on the stadium cinematic/introduction camera view where players are warming up before kickoff. At the same time, the match itself continued in the background. I could see the in-game timer and score changing while my opponent was actively scoring goals against me. I was unable to see actual gameplay or control my players normally. The only thing available to me was partial menu/tactics interaction. Meanwhile, it appeared that my opponent could fully control the match on his side without restrictions. This does not look like a normal bug anymore. It strongly appears to be an exploit, cheat, desync manipulation, or some type of hack being abused in FC 26 Champions to gain unfair wins and farm rewards, FC Coins, rankings, and stronger Ultimate Team squads. These accounts may even be connected to coin farming or black-market activity. Previously I also experienced incidents involving controller/gameplay blocking, and now this new “screen lock” exploit has appeared again. Please investigate this issue seriously. I believe many other players may also be experiencing similar problems. I am posting this publicly in hopes of finding other players who encountered the same exploit and to bring more attention to this issue within EA SPORTS FC 26. #FC26 #EASPORTSFC #FC26Cheater #FC26Hack #FC26Glitch #UltimateTeam #FC26Champions #EASports #Gaming #CheaterExposed #FC26Bugs (CM: Edited to remove video naming and shaming per forum rules)
Unknow Error bf6 error code 0:51009s... on startup
Whenever I launch the game I het Unknow Error 0:51009s:11468332130:1073807360q as it tries to connect to the servers. I have now been talking to support for 3+ hours and they told me to pos here as they have no fix for this 'bug' I did the entire slew of troubleshooting steps suggested. Game was working fine yesterday, no hardware or software changes since then.
FC 26 black screen on launch, account-side issue, looking for help
Hi everyone, I'm posting here hoping someone in the community has dealt with this and found a solution, because I've been stuck for over 18 days and I've run out of things to try. The issue: when I launch FC 26 from EA App, Javelin Anticheat loads correctly, the game window opens to a black screen, and after about 10 seconds it closes by itself with no error message. EA App stays open in the background as if nothing happened. The game worked perfectly until late April, and I have over 200 hours of playtime on my account. I've already tried every standard troubleshooting step I could find: Repairing the game through EA App Fully uninstalling and reinstalling FC 26 Manually deleting C:\Program Files\EA\AC and reinstalling EA AntiCheat by launching FC 26 as administrator Reinstalling EA AntiCheat from the standalone installer Updating NVIDIA drivers to the latest version Trying older NVIDIA drivers Disabling NVIDIA App overlay and Discord overlay Closing all background apps Clearing Documents\EA SPORTS FC 26 entirely Disabling cloud saves in EA App settings Signing out and back in to the EA web/companion app Freeing up significant disk space on C: Running the full clean boot procedure with msconfig Creating a brand new Windows user profile and testing from there Installing/reinstalling Visual C++ Redistributables (x86 and x64) Checking environment variables for GAME_DATA_DIR Verifying Secure Boot status and TPM 2.0 Restarting properly multiple times Launching as administrator None of it made any difference. The behavior is identical every time. The interesting part: a friend logged into his EA account on my PC, and FC 26 launched and ran perfectly fine. Same hardware, same Windows, same drivers, same setup, only the account changed and the game worked. So this clearly isn't a hardware or local issue, it's something tied to my specific account. I'd also like to mention that this same exact issue is being reported by other users in another active thread on this forum, with very different hardware setups (one user has a 7800X3D + RTX 4090, mine is a Ryzen 5 4600 + RTX 3050), different countries, different configurations. The only common factor between us is that our specific accounts can't launch the game while other accounts can on the same machines. About that cross-account test: I want to mention that while it has been useful as a diagnostic, it's not really practical as a repeated suggestion for every new user reporting this. FC 26 is tied to whoever purchased it, so testing with another account requires another person who already owns and has installed the game, lives close enough to help, and is comfortable sharing their login. Sharing EA credentials is also against the Terms of Service, which makes it awkward to keep recommending. I performed this test once, it confirmed the account-side nature of the problem, and I think that should be enough. I'm attaching a video showing exactly what happens on launch, along with my latest DxDiag for reference. If anyone here has actually managed to resolve this specific issue (not just similar-sounding ones), please share what worked. Any lead is appreciated. And if anyone from the EA team can take a look, I'd really appreciate an update on whether there's progress on the backend side. Thanks in advance to anyone who reads this and shares any insight.