Battlefield™ 6 News

[p]Update 1.1.3.6 is a small quality-of-life update focused on polish, stability, and targeted fixes across Battlefield 6. It addresses a selection of gameplay flow issues, UI reliability improvements, audio consistency fixes, and map-specific adjustments, with a particular focus on smoothing out edge cases reported by players.[/p][p]
The update will be available on Tuesday, February 3 at 09:00 UTC.[/p][p]
Major Updates for 1.1.3.6[/p]

• [p]Fixed player movement issues, including cases of excessive sprint-jump momentum and unintended movement behaviour. This won't impact player movement at a large scale and is meant to target those specific edge cases.[/p]
• [p]Addressed REDSEC Battle Royale issues affecting insertions, parachute behaviour, and redeploy UI elements.[/p]
• [p]Resolved a set of destruction-related visual and lighting issues on Eastwood that could result in lighting artifacts, blackouts, or incorrect colour rendering.[/p]
• [p]Fixed a handful of UI, audio, and stability issues, including crashes related to challenges, minimap accuracy, unintended gadget audio playback, and platform-specific problems.[/p]

[p]CHANGELOG[/p][p]PLAYER:[/p]

• [p]Fixed an issue where sprint-jump momentum could behave inconsistently and grant higher or lower momentum than intended.[/p]
• [p]Updated the Objective Ace and Winter Warning cosmetics to better align with Battlefield’s visual identity.[/p]

[p]MAPS & MODES[/p]

• [p]Fixed an issue on Eastwood where destroying a building near the A flag could cause unintended green or purple visual effects across nearby structures.[/p]
• [p]Fixed an issue on Eastwood where destroying a building near the B flag could cause a complete lighting blackout across the map.[/p]
• [p]Fixed an issue on Eastwood where destroying the villa near the B flag could cause excessively bright lighting artifacts to appear.[/p]

[p]UI & HUD:[/p]

• [p]Fixed an issue where downed squadmates were shown on the minimap for classes unable to revive them.[/p]
• [p]Updated legal text to reflect current policies and requirements.[/p]

[p]AUDIO:[/p]

• [p]Fixed an issue where UAV Drone enemy detection audio could be heard by all teammates instead of only the operator.[/p]

[p]PERFORMANCE & STABILITY:[/p]

• [p]Fixed an issue on PlayStation 5 where ownership validation could fail during system lifecycle events, causing connectivity issues.[/p]
• [p]Fixed an out-of-memory crash on Xbox Series S that could occur when loading Daily and Weekly Challenges.[/p]

[p]REDSEC[/p][p]PLAYER:[/p]

• [p]Fixed an issue where Battle Royale Initiation matches did not end after eliminating the final AI opponent.[/p]
• [p]Fixed an issue where parachute deployment could remain linked to the jump leader after breaking off.[/p]
• [p]Fixed an issue where players could become stuck mid-air during insertion after progressing through the pre-deploy sequence.[/p]

[p]UI & HUD:[/p]

• [p]Fixed an issue where the Second Chance redeploy icon could incorrectly transfer to a living teammate.[/p]
• [p]Fixed an issue where the Second Chance redeploy timer refreshed each time the map was opened.[/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]

Battlefield 6’s Season 2 was recently pushed back by a month to give Battlefield Studios time to polish up its content. Now, the developer has revealed how it plans to use some of that time, and the first port of call is Battlefield Labs.

Read more

Battlefield 6’s efforts to break ground while Gittin’ Back To When Battlefield Was Gud continue with the announcement of two forthcoming maps. One of the maps is Contaminated, a brand new field of battle that is comparable in scale to Battlefield 1’s St Quentin Scar and Arras in Battlefield 5. It's coming in the EA shooter’s second season, which begins 17th February. The other map is a remake of Battlefield 4’s Golmud Railway – a big, grassy vehicular affair, based on China’s actually existing Golmud-Lhasa railway line. It'll launch at some point further down the line.

Read more

[p]Hey everyone,
[/p][p]We hope you had a wonderful holiday season and are ready to jump back into the action as Battlefield Labs kicks off the new year.
[/p][p]As we mentioned in our January Update blog, we’re using Labs to further polish and refine Season 2 content, validating changes and making final tuning adjustments ahead of launch while continuing to apply what we learn as we evolve the experience.
[/p][p]In this next session, we’ll be testing content on one of Season 2’s new maps: Contaminated.
[/p][p]We’ll be evaluating how vehicle gameplay and aerial presence interact with infantry combat, alongside cover and asset placement, and objective boundaries. We’ll also be testing how the map’s unique gameplay mechanics function in live matches, as well as the tools available to players to interact with them.
[/p][p]While we’re saving full details on the new map for a later time, we can share that in terms of size, Contaminated falls between Eastwood and Mirak Valley, and is comparable to classic Battlefield maps such as St. Quentin Scar (Battlefield 1) or Arras (Battlefield V).[/p][p]
[/p][p]Alongside our Season 2 map testing, upcoming Battlefield Labs sessions will also include a handful of additional gameplay-focused tests. This includes early testing of the AH-6 Little Bird ahead of its planned arrival in Season 2, allowing us to evaluate how it fits within the broader vehicle ecosystem and how it performs across different combat scenarios.[/p][p][/p][h2]On the Horizon[/h2][p]Looking further ahead, we’ll be running more exploratory tests across aircraft and vehicle combat systems. This includes initial testing of Aircraft Radar, an important part of the aircraft gameplay experience and a system we’re actively evaluating as part of future air combat improvements.
[/p][p]In parallel, we’ll be exploring a tuning package focused on rocket and vehicle interactions, including early adjustments to weapons such as RPGs and TOW launchers, as well as vehicle handling considerations when countering rockets.
[/p][p]Future testing will also validate improvements we’re making to hit registration and overall combat consistency, as it is one of the more complex areas of development. We spoke with Lead Producer David Sirland, who emphasized that “these issues are rarely tied to a single change, but instead require careful iteration across multiple systems, extensive testing, and time to validate results at scale.”
[/p][p]This work includes a number of changes currently in development, with some improvements planned to arrive earlier in Season 2 and additional, more impactful updates in the coming months. Battlefield Labs will help us test, iterate, and validate these improvements as they progress, including scenarios where players may be eliminated after reaching cover, often referred to as “death behind cover” or desync-related behavior.
[/p][p]We also have plans to bring a fan-favorite map from Battlefield 4 into Battlefield Labs, prior to it going live in a future season: Golmud Railway.
[/p][p]Golmud Railway is being rebuilt for today’s Battlefield, not simply ported forward. Our goal is to preserve what made the map so memorable in Battlefield 4, particularly its combined arms gameplay, while improving how it plays and supports Battlefield 6 systems. Golmud is planned to be the largest Battlefield 6 map to date, giving us the opportunity to expand gameplay on a larger scale.
[/p][p]We’re bringing Golmud into Battlefield Labs early as this will be a multi-session project. Through Labs, we want to test changes such as larger flight space, increased cover for aircraft, and other adjustments as the map evolves over time.
[/p][p]We’ll share more details on timing and how to take part in upcoming play sessions at a later date.[/p][p][/p][h2]Battle Royale Solos Testing[/h2][p]We’re also continuing internal and exploratory testing around Battle Royale Solo play, as we evaluate how different player configurations impact pacing, balance, and the overall Battle Royale experience.
[/p][p]This work is focused on understanding where Solo play can best fit within the broader Battle Royale roster, including how it affects match flow, survivability, and long-term engagement when featured alongside other Battle Royale experiences. These tests are part of our ongoing effort to make informed decisions about how Battle Royale is structured and presented over time, rather than committing to a single permanent configuration.
[/p][p]Any future player-facing testing would be approached with the goal of learning and validation, and we’ll share more details ahead of time if and when those tests are planned. As always, when testing does take place, clear guidance on participation and feedback will be provided so we can evaluate how the experience performs in real matches.[/p][p][/p][h2]Get Involved[/h2][p]We’re looking forward to getting back into Battlefield Labs and continuing to build the future of Battlefield alongside you. Battlefield Labs play sessions are an important part of how we test, iterate, and refine new ideas, and your participation helps guide where we go next.
[/p][p]If you’re interested in taking part, you can learn more about Battlefield Labs and sign up for EA Playtesting on our website. To stay up to date on all things Battlefield, including Battlefield Labs updates, we also recommend joining the official Battlefield Discord.[/p][p]
[/p][p]We’ll see you in Labs![/p][p][/p][p]//The Battlefield Team[/p][p]
[/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][p]Battlefield Labs participation remains subject to NDA, which means no sharing of screenshots, videos, or any of the content that is being tested. The timing and details of tests are confirmed via email to invited participants, so make sure you use an email address you frequently check when signing up.[/p]