Patrol boat's mortar is unusable in 3rd-person view for some of us (on mouse)
As can be seen on the video ("Extract 1"), the issue concerns people who use a medium/low sensitivity :forearm aiming. In fact, since the mortar 3rd-person view sensitivity is way lower than the 1st-person one (the classic gunner view), and since they're both tied to the “gunner aim sensitivity” setting, the 3rd-person mode is literally unplayable for anyone using forearm aiming in 1st-person gunner view (sensitivity ≥30 cm/360), as can be seen in the attached video. This probably affects controller players less, if at all, since they can provide continuous input with their joysticks. My settings : 1600 DPI / "Vehicle mouse aim sensitivity" = 6.6 / "Gunner aim sensitivity" = 74. / Meaning that my effective gunner sensitivity is ~45cm/360. Those affected, feel free to share your settings in the comments, but you absolutely need to provide all three, as they all multiply together to determine your true gunner sensitivity ;) Alternatively, you can directly give your "effective gunner sensitivity" in cm/360 (it doesn't have to be exact to the centimeter, ± 5cm is fine) Leaving a comment is great because, if the dev handling this ever reads it, they'll hopefully take low-sensitivity players in consideration next time a new vehicle or gunner view is implemented, in order to avoid this kind of issue (which was already an issue with tanks in S1 & S2, until it got partially tweaked in S3). Temporary fix use the keyboard's arrow keys boost your DPI 5 to tenfold Neither of them is a convenient workaround, though: the former requires switching DPI every time you change views, while the latter requires moving your right hand between the keyboard (arrow keys) and the mouse whenever you switch views, since, like me, you most likely use "3" and "4" to switch views and trajectories, meaning your left hand needs to stay on the keyboard. How to replicate: Try playing the mortar in 3rd-person view with a mouse, using the aforementioned sensitivity settings (as well as any additional settings provided in the comments). Suggested fix : Untie the 3rd-person gunner view sensitivity from the main “gunner aim sensitivity” slider, and give us a separate sensitivity slider for this particular view ("gunner 3rd-person sensitivity" for example), with a wide range of values since the base sensitivity is very low compared to other views. By the way: Some of us have also been asking for the 3rd-person tank camera sensitivity to be untied from the “Tank Aim Sensitivity” slider and to be given its own dedicated slider, so that we can set the 3rd- and 1st-person sensitivities separately. In fact, the relationship between 3rd- and 1st-person sensitivities was arguably much better thought out in BFV and BF2042 (1.7 multiplier). So if you decide to proceed for the mortar slider, it would be greatly appreciated if you could kill two birds with one stone here :) -------------------------------------------------------------------------------------- There are 2 other little inconveniences with the patrol Boat (video extract #2) #1 The camera goes crazy (47") How to replicate : drive the boat under a bridge for example. This also seems to happen whenever the camera is obstructed by an object (pylon, or anything else), and also sometimes in the middle of nowhere, for no reason (waves maybe?) #2 When reversing, the steering controls are inverted compared to those of ground vehicles (55") So this one might be a realism thing (I don't know, I've never steered a boat), but it can be annoying from a muscle-memory standpoint when switching back and forth between boats and ground vehicles, especially when every quarter of a second can make the difference between life and death in a boat. Having a toggle to invert the left and right reverse steering controls, so we can harmonize the boat's reverse controls with those of ground vehicles, would be greatly appreciated. Ty for reading :)
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.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.
Contaminated Breakthrough Sector 4 Obj B Fence Potential Exploit
Sector 4 Objective B allows the attacking team to get in-between the restricted border and the fence line making it near impossible to kill the player and allows them unfettered sightlines into objective B. Happens at 0:16 seconds. Is this intended to allow them to go into the restricted border and get in that small area there?Endurance tier one challenge still bugged.
After completing the gauntlet tier one endurance challenge four weeks ago, the reward sticker is still locked and blacked out. This isn’t an isolated problem. Me and other players across other platforms who play gauntlet/br are having this issue with this as well. I understand the new season just came out and things are quite busy, but this issue has been around for over a month. It would be great for us to use the rewards that we put time in to get.3 Weeks Later: Black Challenges Still Broken, BR Wins Still Not Counting
21 days ago, I reported the Black Challenge reward bug. The reward icons turned into black squares, the rewards never unlocked, and I never got a single reply. The bug is still there. Now I'm dealing with another progression bug. The Battle Royale challenge that tracks wins doesn't count any wins at all. I've won multiple matches, including 5 consecutive wins, and the challenge is still sitting at 0. Nothing counts. At first I thought it was just my account. I was the first one in my friend group to have this issue. Now all of my friends are getting the exact same bug. Meanwhile, I keep seeing newer bugs being looked at and fixed through the Battlefield Discord, while these progression bugs have been ignored for weeks. It's hard not to feel like these reports are just getting buried. These aren't small visual issues. They completely block challenge progression and prevent players from earning rewards. Can someone from the team please look into this and let us know what's going on? Even a simple "we're aware of it" would be better than complete silence after three weeks.
