Battlefield 6 DLSS BUG. Exact Triggers and Partial Workaround.
Greetings, this bug has been present and unresolved since the game's launch, and there is significant misinformation surrounding it across numerous reports.
The bug occurs in DLSS 4.0 (Presets K or J, which are the best for this Battlefield except for this issue). It does not occur in DLSS 4.5, but the performance in that version is worse; it remains over-sharpened and exhibits pixelated, unstable highlights or shadows. These artifacts depend on the quality level of the ambient occlusion setting you activate (you can see the effect of each immediately in the Firing Range by toggling between them, and how it is fixed by disabling ambient occlusion entirely).
In any case, it is a priority to fix DLSS 4.0, as it is by far the version that achieves the most natural results and the best performance.
The bug is entirely dependent on the rendering resolution and likely linked to transitioning through screens with UI elements that do not apply DLSS, such as the respawn screen.
Every time you die on Manhattan Bridge or Mirak Valley and pass through this screen (which is why it only occurs in large modes like Breakthrough, Conquest, etc.), you will experience this bug.
At 2160p (4K) resolution with DLSS set to Quality, the bug occurs on Manhattan Bridge and nowhere else. Adjusting the rendering resolution to 107.2% in my case fixes the bug on that map, as does lowering the quality to Balanced.
However, by doing this, the bug then triggers in Mirak Valley and also on the vehicle selection screen. In the latter, you can see how the background begins to show corruption similar to massive over-sharpening, eventually displaying a pattern of white dots after a few seconds if left idle. This also happens in Balanced mode; ultimately, anything that fixes the Manhattan Bridge bug breaks Mirak Valley and this vehicle selection screen (among others, such as the weapon selection screen during a match if you stay on it long enough).
It can be fixed by switching back to Quality, or using Quality + a resolution scale below 106%.
The only thing that fixes everything is using DLAA (which does not upscale) combined with Frame Generation. But in the case of Frame Generation, it is more of a coincidental fix; the feature automatically deactivates when passing through the respawn screen. This acts as if you were manually changing a graphic setting or toggling between Fullscreen and Windowed mode with Alt+Enter—actions that are documented to "fix" the bug until the next respawn.
It goes without saying that the bug causes the game's graphical elements to appear extremely blurry and unstable, a fact widely documented in other posts.
I hope this information is helpful in resolving this bug. It is extremely annoying, and the fact that it remains unpatched after so much time is intolerable.
Thank you very much.
Sample:
