Battlefield 6 Season 3 Performance and Netcode Issues
It’s honestly unbelievable that we are now deep into Season 3 and many of the biggest Battlefield 6 issues are STILL here — some of them dating all the way back to Season 1 and even launch week. This is not about “small glitches” anymore. These are gameplay-breaking problems affecting gunfights, matchmaking, performance, networking, and overall game stability. The community has been reporting the same issues for months, yet every new update somehow introduces even more problems instead of fixing the old ones. Here’s what players are STILL experiencing in Season 3: Broken hit registration Delayed damage and desync Rubberbanding Packet burst feeling Random ping spikes Matchmaking putting players into high-latency servers Massive frame-time spikes and stuttering Inconsistent recoil and aiming responsiveness UI bugs that survive multiple patches Visual glitches making maps literally unplayable Ranked mode launching with known bugs And the worst part? A lot of players have perfectly stable internet, high FPS, strong PCs, and STILL get terrible gameplay quality because the issue is clearly server-side or netcode-related. Community reports repeatedly show that official servers feel dramatically worse than community-hosted experiences. Even EA Forum posts are filled with complaints about: broken HUD ping indicators, severe lag after the Season 3 update, FPS instability, missing UI elements, persistent unlock notifications, and visual bugs that completely blind players on certain maps. Meanwhile, DICE openly launched Ranked Battle Royale with a list of “known issues” already acknowledged on day one. The Battlefield community has supported this franchise for years because when Battlefield works, it’s one of the best FPS experiences on the market. But right now it feels like players are being used as beta testers every single season. How does a company the size of Electronic Arts and DICE still struggle with: basic server stability, functioning hit registration, proper matchmaking routing, and performance consistency months after launch? Players should not need VPNs, routing workarounds, FPS caps, or third-party fixes just to make the game feel playable. The community is tired of hearing: “We are investigating.” We want actual fixes. Season 3 should have been about improving the game. Instead, many players feel like the technical state is worse than before. Battlefield deserves better. And honestly, so do the players paying for it. (cm edit updated title for vis)2.2KViews18likes203CommentsBF6 Crash on Launch, Black Screen
Hi, has anyone come across this problem - BF6 was working fine on my computer until last update (i think!!). Steam loads ok, game starts to load, no error messages, anticheat loads etc then when the black screen comes up just before the start menu appears the game Shuts Down (Steam still remaining open) I have cleared caches; checked latest drivers; deleted and reinstalled both Steam and BF63.9KViews3likes162CommentsBattlefield 6 - Repeated BSODs caused by EA Anti-Cheat (Intel i7-14700K)
Hi everyone, I'm posting this in the hope that EA can investigate this issue, as I've spent days troubleshooting and have ruled out many common causes. System Specifications: CPU: Intel Core i7-14700K GPU: Sapphire Nitro+ Radeon RX 7800 XT Motherboard: ASUS TUF Gaming B760M-PLUS WIFI II RAM: 32GB Corsair DDR5 5600MHz Storage: Windows on C: drive, Battlefield 6 on a separate NVMe SSD (D: drive) PSU: Gigabyte UD850W (850W) Cooler: Corsair Titan 360 RX AIO Windows 11 (fully updated) Latest AMD GPU drivers Latest motherboard BIOS The Issue: Around 28th-30th July, Battlefield 6 suddenly started crashing my entire PC with Blue Screens of Death. Before then, the game had been working normally. Nothing changed with my hardware or BIOS configuration immediately before the issue began, yet the crashes started completely out of nowhere. This is not a normal game crash—it completely crashes Windows and forces the PC to reboot. The crashes are inconsistent. On some occasions I can play a full match before the system blue screens, while on others the PC crashes within 5–10 minutes and even when I'm idling in the menu. I have not found any consistent action or point in the match that triggers the crash. I also tested today's Battlefield 6 update as soon as it became available, but it did not resolve the issue. The game continues to trigger the same BSODs on my system. Crash Analysis: I've analysed multiple minidumps using WinDbg. Every dump consistently points to: IMAGE_NAME: eaanticheat.sys FAILURE_BUCKET_ID: AV_eaanticheat!unknown_function SYMBOL_NAME: eaanticheat+4b480f3 Every crash dump I've analysed points back to the EA Anti-Cheat kernel driver, with the stack trace consistently ending inside eaanticheat.sys. Troubleshooting Already Performed Over the last several days I have tried: Completely uninstalling and reinstalling EA Anti-Cheat. Repairing EA Anti-Cheat multiple times. Running the EA Anti-Cheat installer and launcher as Administrator. Verifying the Battlefield 6 game files. Updating Windows. Updating my motherboard BIOS. Updated Intel Chipset Driver, Intel Management Engine Interface and Intel Serial IO. Updating to the latest AMD graphics drivers. Using DDU (Display Driver Uninstaller) to completely remove my GPU drivers before installing the latest AMD driver. Testing with XMP both enabled and disabled (the PC still crashes after roughly 10-20 minutes either way). Disabling third-party antivirus. Adding Battlefield and EA Anti-Cheat to Windows Exploit Protection exclusions. Disabling as many third-party kernel-level applications and background software as possible. Restarting between troubleshooting attempts. Performed CPU and RAM stability testing (including OCCT) to check for hardware instability. Those tests did not reproduce the Battlefield 6 BSODs, suggesting the crashes are specific to Battlefield 6 and/or EA Anti-Cheat rather than occurring under general system load. One interesting thing happened after repairing EA Anti-Cheat. The game crashed to desktop instead of blue screening my PC, and I managed to finish a full match beforehand. I initially thought this had resolved the issue, but after repeating the exact same repair process, the crashes returned and my entire PC blue screened again. I have also tested Battlefield 1 on the same system without any crashes, BSODs or unexpected reboots, suggesting the issue is specific to Battlefield 6 rather than gaming in general. Request: Has anyone with a similar system, particularly an Intel 13th or 14th generation CPU, experienced this? If anyone from EA is reading this, could this please be investigated? Multiple crash dumps consistently identify eaanticheat.sys, and despite extensive troubleshooting the issue persists. A game crashing is frustrating enough, but software causing repeated kernel-level BSODs is a much more serious problem. At this point, I feel I've exhausted the troubleshooting that can reasonably be performed on my end, which is why I'm raising this in the hope that EA can investigate it further. I'm happy to provide crash dumps, WinDbg output, Event Viewer logs, or any additional diagnostic information if it helps identify the cause.Ok... its time we had a talk as a community
Why do anyone hardly play their role? Medics hardly Revive(they'll literally be 1 meter from your body and run off or even squat over you)and toss ammo, engineers hardly fight off armor, assaults hardly push objects, and recons is selfish with their scouting and spotting... this game is nowhere near as complex as these guys make it. Another thing... you have a squad for a reason.... to stick together and back each other up. Not for everyone to lone wolf and just spawn on each other. Battlefield would be beautiful if it was actually played as it is intended. Can we as a community fix these issues?Solved654Views5likes66CommentsBroken RPK animation 2
Continuing to report bugs related to RPK animations — here's a second issue: the magazine reload animation with a vertical foregrip installed. During reloading, the magazine clips through the foregrip. It's worth noting this happens specifically with the 40-round magazine, since it's very long. Below I've attached screenshots showing the magazine clipping through the foregrip. Also, if you'd like to support the fix for another RPK-related animation issue, please follow this link and vote: https://forums.ea.com/idea/battlefield-6-bug-reports-en/broken-rpk-animation/1360422735Views4likes6Commentsi have been incorrectly banned––a player for playing series for q thousans hours
Here's the situation. I am a Chinese player and have put a lot of effort into the Battlefield series. My data is also normal, and you should be able to check it. However, due to the issue with the regional network, I had to use an accelerator to play. On June 23rd, I played the game as usual with my friends. Perhaps due to unstable network conditions, the EA anti-cheat program triggered a ban. I sent an appeal email but received no response. I guarantee that I have not used any game-enhancing software or exploited bugs for any enhancements. I sincerely hope that you can re-examine my account and help me. following is my log information, which can prove i'm right, by the way, my kd is below 2, a normal kd for players like me who have played the series for almost a thousand hours, i really need your tos reviewparty members not getting put into game when host searches and finds game
I will say this up front that this issue has been happening since the beta. I didn't report it before as I assumed it was a known issue. Clearly, the issue is still occurring. This has happened to multiple of my friends on Xbox. We have tried different hosts, exiting the previous game when finished to main menu, staying in the previous lobby and not exiting, rebooting consoles, rebooting game, and I have personally even uninstalled and reinstalled the game. Nothing we do fixes the issue. There is no rhyme or reason for it happening as far as I can tell. Sometimes it happens when we are in the after game menu. Other times it happens when we are on the main menu and host is searching. There is no way of replicating the issue as it is completely random.14KViews152likes177Comments