Short screen freeze right after getting to the spawn screen
It started for me with patch 1.3.1. Every time I get to the spawn screen, the screen freezes for a short moment. There was a similar thread where they advised deleting the settings folder, which I did, and everything worked fine upon launch. However, as soon as I restored my settings, the freezes started again. I finally figured out that the freeze occurs when FSR Native AA or FSR upscaling is turned on, but there are no freezes with TAA. Honestly, even in the menu, my screen freezes for a split second whenever I toggle between upscaling options. I'm running AMD driver version 26.5.2 and I have a 9070 XT card.Air radar detection bug
Air Radar Detection Range Bug Bug Description The aircraft radar is malfunctioning by reducing its detection range from the intended 1,000 meters down to as little as 400 meters after the 30TH June patch. During testing, 400 meters was the minimum range observed, occurring near the altitude where the bug reaches its maximum effect. This issue affects both jets and helicopters. Maps Tested - Liberation Peak: The bug starts appearing at around 500 meters altitude and becomes progressively worse when flying closer to the mountains. - Golmud: So far, the bug has not been observed on this map. - Sobek City: Detection range reduced to 400–500 meters. - Tsuru Rift: Detection range reduced to approximately 700 meters. - Firestorm: Detection range reduced to approximately 700 meters. - Mirak Valley: Detection range reduced to approximately 700 meters. - EastWood: The bug starts appearing at around 300 meters altitude. Detailed Description In addition to the reduced radar detection range, the aircraft icon (jet or helicopter) displayed at the center of the radar begins to shift away from the radar's central axis. This displacement is a clear indicator that the bug is active and becomes more pronounced as the issue reaches its maximum severity. Gameplay Impact This issue has little to no impact on infantry gameplay. However, it is game-breaking for jet and helicopter pilots. Since the radar range changes depending on altitude—and the exact altitude at which the bug occurs may vary between players and is not always consistent—pilots can lose critical battlefield awareness unless they are provided with precise enemy positions. This is particularly problematic because this issue had already been resolved before the May 30 patch, but now appears to have returned. Thank you for your time. I hope you can investigate this issue as soon as possible and provide a fix. Also I am absolutely disgusted from your Q and A, since most of the people are getting ignored and there is 0 losdouts in jet for almost 1 year. Please work.
New Beam-Riding / Active Radar Missile Ignores Countermeasures (Flares)
The new beam-riding/active radar missile currently equipped on the attack boats (and expected to be added to the upcoming jets) appears to be ignoring countermeasures entirely. According to the in-game description, the missile is supposed to be vulnerable to countermeasures once it has locked onto a target. However, this does not match its current in-game behavior. Current Behavior: The missile consistently tracks through flares. Deploying flares has no noticeable effect on the missile, no matter when they’re deployed. Once the missile has locked on, it almost always results in a hit regardless of countermeasure usage. In my experience, I have not successfully defeated this missile with flares a single time. A friend reported managing to flare it off once, but that appears to be extremely rare. Expected Behavior: If the missile is intended to be susceptible to countermeasures, flares should have be reliable at breaking the lock or causing the missile to miss, consistent with its description. Impact: This is a game-breaking issue for pilots. Air vehicles have already been heavily affected by the longstanding Igla issues since Season 2, which became even worse in Season 3 due to the increased initial missile speed. Now, the new missile introduced with the Tsuru Reef map is creating an even more severe problem, as it appears to ignore flares almost 100% of the time. Llease either: Fix the missile so it interacts correctly with countermeasures as described, or Temporarily remove it from the attack boats until the issue is resolved. This is having a significant negative impact on air vehicle gameplay and should be addressed as a high-priority bug. And it will becomes even more severe once the new jets come out, if it’s not fixed until then.Restore APAC Normal Real-Player BR Matchmaking (BF6 S4)
I am a long-term dedicated T250 ranked player of Battlefield 6 in Season 3, based in the APAC region. I am writing to formally request urgent adjustments to the current Battle Royale matchmaking system for APAC players, as the recent updates have severely ruined the core gameplay experience for most regional players. Yesterday, EA officially removed the standard normal Battle Royale casual matchmaking mode from the APAC server region. Currently, only bot-filled casual BR and ranked BR modes are available for APAC players. This change has left veteran players with no viable pure real-player casual game options. First of all, the existing casual Battle Royale mode is basically a bot-only mode with almost no real human opponents. As experienced high-rank players, we have no willingness to play against AI bots at all. We sincerely hope to have a pure real-player casual matchmaking mode to practice, warm up and enjoy authentic competitive gameplay without the pressure of ranked scoring. Furthermore, the ranked Battle Royale mode in APAC still suffers from severe matchmaking failures. Even during the prime matching window of 8:00 - 9:00 PM local time, players cannot find any valid matches. To make the situation worse, multiple APAC players (including Korean community players) have confirmed a critical server matching bug: after waiting for merely 8 minutes in the queue, the system will forcibly redirect APAC players to EU or US servers. This forced cross-region matching completely breaks the gaming experience. High ping, severe lag, unstable connections and inconsistent server environments make it impossible for us to compete normally. None of the APAC players want to travel to European or American servers for ranked or casual matches. We only want stable, low-latency matches on our local APAC servers. Here are our clear and reasonable official requests from all APAC BF6 core players: Reinstate the original standard normal Battle Royale casual matchmaking mode for APAC servers immediately. Bring back the 100% real-player casual BR matches, and cancel the bot-only casual mode as the only alternative. We need a pure human-matchmaking mode to meet our daily gaming and practice needs. Add a strict region lock matchmaking feature. Prevent the system from forcibly redirecting APAC queue players to EU/US servers without consent. Allow players to stay in their local server region exclusively. Add real-time regional queue player number display. Let players check the current online queue population of the local server intuitively, which can effectively help generate stable local APAC matches and avoid blind queuing. Different players have different gaming needs: some players pursue ranked competition, while most core players just want relaxed, pure real-player casual matches. The current mode setting only forces players to play bot games or cross-region high-lag ranked matches, which has made the APAC BF6 player base increasingly frustrated. We truly love the Battlefield franchise and hope BF6 can have a healthy regional server ecosystem. Please listen to the voices of APAC veteran players, restore the normal real-player Battle Royale casual matchmaking, and fix the cross-region forced matching bug as soon as possible. Thank you for your attention and looking forward to your official optimization and update! Sincerely, APAC T250 Season 3 Player & Community Players
RPG Aim down sight Brightness bug
This bug is triggered anytime you aim down sight with the RPG only and seems to be on certain maps worse than others. Example, this current bug like what's going on in the attached video is unplayable on maps like Firestorm where the brightness just ramps up as if hit by a flashbang. The issue has been reported several times but was only partially addressed and now is abandoned so I'm making a new post for this because it needs to be fixed.
Are Reported Bugs Monitored
BigBoy here. I have a question regarding bug and issue reports on the forums. When a soldier reports a bug, how long does it normally take before it is reviewed by the EA team? Is this platform actively monitored, and if so, how frequently? The reason I'm asking is that I've noticed another soldier reported a bug around 20 days ago (as shown in my attached screenshot), but there hasn't been any response from EA Customer Services or the development team. I understand this report was made before the Season 4 update, and I appreciate that major updates can sometimes resolve existing issues. However, from a community perspective, it can give the impression that reports are not being monitored or acknowledged, and that everyone is simply waiting for the next update in the hope that the issue fixes itself. I'm not trying to be negative or critical—I'm genuinely interested in understanding how the bug reporting process works and what we, as players, should expect after submitting a report. Even a brief acknowledgement that a report has been seen would give the community confidence that our feedback is reaching the right people. Thank you, and I look forward to your response.Area Marker/Ping Not Working Correctly
Hi EA Team, BigBoy here. I've come across what appears to be a bug with the marking (ping) system in the game. When I try to mark a location or area, the marker either doesn't appear at all or is placed well away from the spot I'm actually aiming at. However, marking enemies and mission objectives seems to work as intended. This issue appears to affect only area/location markers, making it difficult to communicate positions accurately with my squad. Has anyone else experienced this, or is it a known issue that the team is investigating? Thanks for all your hard work, and I look forward to hearing if this can be reproduced.
Adrenaline Challenge Bugged
The Adrenaline Challenge is Bugged No matter how many kills you get after using the Adrenaline injector, you do not get credit for any of them. I just want to get the spawn beacon. It should not be this difficult. I even tried in a bot server and no credit. for any of the work. Please fix this. Thanks.Ping/Area Marker Issues
Hi fellow Battlefield players, BigBoy here! 👋 Just checking in to see if anyone else has been experiencing issues with the ping/marking system lately. Has anyone noticed that when you're in a vehicle—especially a tank—the area marker either doesn't register or lands well away from the location you were trying to ping? It seems to happen far more often in vehicles than when on foot. I've also noticed that marking enemies or objectives works perfectly fine, but trying to mark a specific area on the map doesn't seem to work properly. Is anyone else experiencing this? Does it only affect area markers for you, or is it affecting everything? Leave a comment below and let me know what you've been seeing. I'm trying to find out whether this is a widespread issue or just affecting some players.