Battlefield 6 - Community Update - Ongoing Quality of Life Improvements
[p]Hey everyone,
[/p][p]I’m Florian Le Bihan, Principal Game Designer on Battlefield 6. I’ve been working closely with our gameplay, networking, animation, and audio teams to improve the core combat experience. My focus has been on connecting these systems to deliver encounters that feel consistent, responsive, and exciting every time you step onto the battlefield.
[/p][p]With Season 2 underway, I want to take a deeper look at several foundational systems that directly impact the feel of the game. Hit registration, Netcode, Time to Kill, soldier visibility, and audio clarity are tightly connected systems. While we’ve delivered numerous improvements since launch, our work is ongoing. We will continue to analyze, evolve, and enhance the experience based on feedback because the connection between the game and the player sits at the heart of Battlefield.
[/p][p]Combat reliability is not driven by a single system, but by how these layers interact with one another. Improving this experience requires careful sequencing. In many cases, stabilizing one system is necessary before adjusting another. Networking behavior affects how Time to Death is perceived. Visibility influences pacing and damage clarity. Animation alignment impacts “shot behind cover” scenarios.
[/p][p]Because these systems overlap, changes must be validated carefully to ensure they improve consistency without introducing new issues. This process takes iteration and large-scale testing, which is why Battlefield Labs plays such an important role in our approach.
[/p][p]Today, I want to walk you through where we are, what we’ve already improved, and what we’re continuing to refine based on your feedback. In parallel, our broader efforts continue across performance, stability, UI clarity, progression, and other player experience improvements.[/p][p][/p][h3]Hit Registration / Netcode[/h3][p]Extreme Measures (Season 2 Phase 1) introduced the first round of networking changes aimed at improving combat reliability. Bullet data is now handled more efficiently, and additional stability updates are planned for our next major update. These refinements continue to be validated through Battlefield Labs to ensure improvements hold up under full live service conditions.
[/p][p]Since launch, this topic has been one of the most discussed aspects of Battlefield 6. We’ve seen examples of shots appearing to land but not registering, and situations where players felt they were eliminated after reaching cover. Some of these experiences are influenced by perception - especially when some of our weapons have a particularly fast Time to Kill combined with limited visibility - but technical issues have also contributed. We’ve addressed several of these issues already, and we are continuing to work to stabilize and refine others.
[/p][p]With our recent update, we optimized how bullet-related data is being transmitted between client and server. In rare cases, too much information exchanged within a single update could delay damage feedback for either the shooter or the player taking damage. These changes prioritize critical interactions, such as shots landing or damage being applied, so they are processed more reliably and in a more timely manner.
[/p][p]Another key area involves how clients remain synchronized with the server, often referred to as Time Nudge. In online shooters, the game client cannot display events at the exact same moment the server processes them due to network latency - information is never transmitted instantaneously between client and server. Instead, it buffers a small amount of incoming data to smooth out network or performance fluctuations. When functioning correctly, this results in fluid movement and stable hit registration.
[/p][p]At launch, this system could drift outside safe bounds under unstable network conditions or heavy system load, contributing to desynchronization. We are targeting configuration adjustments to better constrain and stabilize this behavior in the next major update. The goal is to ensure that what you see on screen more closely matches what the server sees, even when performance fluctuates. Internal and Labs testing shows improved alignment, but more player impressions are needed before we consider this resolved.
[/p][p]In addition to this, we will look into refining the responsiveness and clarity of both incoming and outgoing damage indicators. When you take damage or land shots, feedback should be immediate and readable across UI, audio, and visual effects. Improvements in this area will continue alongside our networking efforts. We’ve also corrected cases where the soldier health bar updated a few frames after the actual damage occurred and where incoming damage animations lacked clarity, which could have compressed multiple hits into what looked like a single hit.
[/p][p]We are also examining how the server validates damage during close encounters. In multiplayer shooters, the server decides whether damage should count, since players are never experiencing the exact same timeline due to latency. In some cases, if the server determines that a player was already eliminated, it may invalidate incoming damage to prevent unintended trade eliminations. This behavior exists to preserve fairness, but it comes with some trade-offs, particularly in fast close-quarters fights where a shot may feel like it should have landed. We are reviewing how these server-side damage rejections behave to ensure the balance between fairness and responsiveness.
[/p][p]Lastly, we identified cases where third-person character visuals do not always accurately reflect what is happening in combat. One example involves enemy facing direction, where a character model may appear to be oriented away from you while they are in fact aiming and firing in your direction. We have a fix scheduled for the next update. Separately, we have also observed inconsistencies when transitioning from standing to prone, where a player’s first-person view may suggest safety while their third-person character model remains partially exposed to others. The fix for this behavior is planned for later in the season to better align visual representation with actual gameplay.[/p][p][/p][h3]Time To Kill (TTK) / Gunplay[/h3][p]The first phase of Season 2 delivered improvements to recoil consistency and a weapon balance pass to ensure weapon handling feels more predictable and responsive. We’ve heard concerns that Time To Death (TTD) can feel too fast, and it remains an active topic of discussion within the team. Before we make broad changes, we’re concentrating on strengthening combat clarity, including responsive audio-visual damage feedback, improved enemy readability, continued Netcode refinements, and more.
[/p][p]TTD is heavily influenced by how clearly combat events are communicated. When multiple bullets land in rapid succession and feedback is unclear, even a four-shot kill can feel instantaneous. At the same time, many players report that TTK from the shooter’s perspective feels satisfying and responsive. Introducing broad changes before stabilizing the underlying systems risks creating a “bullet sponge” experience, elongating TTK, weakening weapon satisfaction and unintentionally shifting pacing. Our priority is to strengthen systems that support gunplay, especially those that affect TTK.
[/p][p]One approach currently being validated in Battlefield Labs involves reducing damage dealt to limbs across several weapon archetypes. Shots landing on arms or legs may require an additional bullet to secure a kill, while headshots remain unaffected. If a bullet passes through an arm and strikes the head, it will correctly register as head damage. This approach rewards accuracy without fundamentally changing the feel of gunplay.[/p][p][/p][p]In addition, we are validating adjustments to the economy of the Hollow Point and Synthetic Tip ammunition attachments through Battlefield Labs as well. Our aim is to make them more meaningful and competitive choices when customizing weapons, ensuring that attachment selection reflects intentional trade-offs rather than default picks.
[/p][p]Weapon control has also been a central focus. Since launch, recoil compensation could behave unpredictably, sometimes requiring more input than expected to counter weapon kickback. This season introduced tighter alignment between recoil output and the aim input required to manage it, improving overall recoil stability. With that foundation in place, we will continue to evaluate recoil balance across weapon archetypes to determine whether additional tuning adjustments are needed. Ongoing refinements will continue through Battlefield Labs as we gather live in-game data across skill brackets and modes.
[/p][p]Our goal is to ensure that when you win or lose an engagement, it feels earned or fair.[/p][p][/p][h3]Soldier Visibility[/h3][p]Soldier visibility continues to influence pacing and perceived fairness, especially in close-range and interior engagements. We are exploring improvements to lighting transitions and visibility systems without breaking immersion. This includes refining how characters read against dynamic environments and varied lighting conditions. Larger art-direction shifts are unlikely in the near term, but targeted changes and longer-term exploration remain active.
[/p][p]Visibility impacts more than spotting an enemy. It affects decision-making, reaction time, and how combat feels overall. When you cannot see who eliminated you, fast TTD feels even more abrupt.
[/p][p]One significant factor involves transitions between interior and exterior areas. Current exposure calculations consider first-person weapon and arm models, which can exaggerate lighting shifts. We are investigating adjustments that exclude these models from the calculations of the exposure in favor of world lighting, with the goal of reducing instances of blinding exteriors or overly dark interiors. While this will not eliminate every scenario, it should meaningfully improve how exposure and lighting transitions between exterior and interior environments behave during gameplay.
[/p][p]Battlefield environments are intentionally grounded and detailed. Debris, destruction, dust, and environmental effects all contribute to immersion but can also make soldiers blend into their surroundings. The game uses a visibility filter and a brightness boost that increases at range to help separate characters from the environment. We are targeting testing in Battlefield Labs once improvements are in place, focusing on improving close-quarter and long range clarity while ensuring characters do not appear out of place within the world.
[/p][p]Achieving the right balance between immersion and readability requires careful iteration. While large visual shifts are unlikely in the short term, we are continuing to make targeted adjustments and researching longer-term solutions for both live updates and future Battlefield experiences.[/p][p][/p][h3]Audio[/h3][p]Audio clarity plays a critical role in combat awareness, especially when it comes to footsteps and vehicle positioning. Since launch, we’ve been working to address cases where footsteps were unclear, vehicles were difficult to track, or sounds would unintentionally drop out in intense moments. Extreme Measures introduced initial fixes to raise footstep clarity and rebalance audio priorities, with more comprehensive changes planned for our next major update.[/p][p][/p][p]Audio challenges in Battlefield are rarely caused by a single issue. Footstep clarity, vehicle audibility, and positional accuracy are influenced by memory limits, file size constraints, performance considerations, and how different sounds compete for priority in large-scale engagement. In scenarios like buildings collapsing while multiple players are firing, the system must decide which sounds take precedence. That prioritization is complex, especially at scale.
[/p][p]With this season, we addressed several of these constraints by reducing file sizes, optimizing performance, and adjusting audio priorities so that footsteps and key combat cues stand out more consistently. These changes were an important first step, but they do not fully solve every scenario players have reported.
[/p][p]In the next update, we are introducing more updates to how footsteps behave within the mix. Footsteps will interact more dynamically with surrounding sounds and feature improved built-in prioritization. Close enemies will be more audible without relying on heavy volume boosts, and distinctions between enemies, friendlies, and your own movement will be clearer. The reliability of obstruction will also be increased, ensuring that sound behaves more consistently when blocked by surfaces, and reduces cases where footstep assets fail to play due to performance constraints.
[/p][p]Vehicle audio is also receiving targeted adjustments. Multiple jets will contribute less to overall noise-floor buildup, and enemy ground vehicles will be prioritized more clearly in the mix, particularly in REDSEC. These changes are intended to improve spatial awareness without overwhelming other critical audio cues.
[/p][p]We’ve also made global mix adjustments to improve clarity and positioning accuracy overall, including updates to stereo and headphone mixes and new width settings in the audio menu that allow for further customization. Default settings are tuned for balanced comfort and positional accuracy, but players who prefer a narrower or wider soundstage will now have more control.
[/p][p]As with all improvements, audio clarity requires continued testing under live conditions. Feedback from the community has been essential in identifying edge cases we could not reproduce internally, including unintended vehicle silence. We will continue refining these systems and keep you updated as further adjustments are validated.[/p][p][/p][h2]Thank You[/h2][p]Large-scale validation can only truly happen in a live environment, which makes your feedback and the data we gather from real matches incredibly valuable. If you encounter issues, enabling the Netgraph in the System settings and sharing clips that include it helps us investigate more effectively. We will continue to speak openly about Netcode and combat reliability, answer questions where we can, and keep you informed with a clear and direct approach as this work evolves.[/p][p][/p][p]//Florian Le Bihan, Principal Game Designer
[/p][p]This announcement may change as we listen to community feedback and continue developing and evolving our Live Service & Content. We will always strive to keep our community as informed as possible.[/p]
