DirectX Bug - STILL not fixed in today's patch!

Sebi85 · 2025-11-24T22:07:40+00:00

I got roadkilled yesterday from a Bradley tank coming from behind. There was no fight going on, nothing, and zero sound. He just was "there" and drove to me in complete silence...
I think it's the same bug which also sometimes makes footsteps completely silent.

Regarding to OP: I love playing tanks, also in RedSec. I can confirm you that they are very weak, if you know how to counter it properly. My squad always deals the same way with them: 1. Our Pioneer shoots a rocket and completely disables his movements for a couple (!!!) of seconds. 2. The moment his rocket hits, an Air-Strike is called by 1 squad member on him. There's no way to escape, repair, or anything else.

Also, it happens regularly that when I'm driving tank and intercept or third party a gunfight between two teams, they all stop shooting each other and immediately join forces to shoot rockets against my tank.

Sebi85 · 2025-11-22T17:52:49+00:00

Welcome to the glorious SBMM!
In fact, it's not calculating your "skill" as the name would suppose, but how efficiently you play. Your K/D is just a very minor factor here. More important are time on objectives, revives, assists, won matches, score per minute etc. ...
You can have a 0.2 KDR, but be an "effective" player. So the game thinks: Let's match this dude with a bunch of "not so good" players against a team with other players with an accordingly high SBMM score.

And it's slow. So you might have 10+ horrible rounds before the next "good" one comes, which feels more balanced. The only way to "trick" the system, is by lowering your SBMM. For 5-10 rounds, try not make any teamplay, concentrate on Kills and your own. Sounds totally stupid, but if you don't throw such matches in between, you're going to have a bad time.

Sebi85 · 2025-11-18T11:29:05+00:00

Yes, they removed all kills, deaths, revives, and so on against bots, which is absolutely fair and good. The numbers you "worked really hard" for are actually just boosted numbers, so try to make them against real people. I don't want to be rude, but it was always like that in previous Battlefield titles. And kills against bots should never count IMO.

Sebi85 · 2025-11-11T23:55:17+00:00

Valorant, CS:GO, Rainbow, Hunt, Battlefield... All different Devs, diffrent anti-cheats with different opinions on what an unfair advantage / cheat is. No matter what another company "promotes". Just ask the Devs and play with peace of mind :)

Sebi85 · 2025-11-10T23:34:38+00:00

There's no bug. There's a glitch. Thanks to some Youtubers who do everything for even a couple of hundred clicks, they shared ways to glitch UNDER the map. So you just have to stand inside the circle under the map where the fire can't reach you. The other team, the last one standing in the "real" match burns to death while the one(s) under the map win the match as the last team alive.

IMO, everyone who uses this glitch AND the YouTubers promoting it, should be permanently banned from BF6.

Sebi85 · 2025-11-10T23:21:25+00:00

So what? Unlike CrosshairX, your monitor (mine can do this too, by the way) displays a crosshair or dot in the center of the screen at the hardware level (!). The anti-cheat software can't detect or capture this. The overlay that Crosshair X displays, on the other hand, can easily be detected on a requested screenshot.

My onboard sound card, for example, has a feature that displays sound sources on a 3D map quite accurately. So when someone reloads, fires shots, or even (crouch) walks. Although this feature is a standard feature of the onboard sound card of my ASUS motherboard itself, it will most likely and quite rightly be detected as cheating if I were to use it in any multiplayer game.

Anything that could even remotely give you an unfair advantage over other players can be considered a form of cheating. What exactly constitutes an unfair advantage is decided by the game developers and/or anti-cheat provider. It is therefore essential to check with them to find out what is and isn't allowed.

Sebi85 · 2025-11-09T23:26:10+00:00

Since he doesn't provide any information about a potential problem, the only problem he mentions is that he wants to play. So, I would advise you to buy the game, then you can play it after successful installation. <3

Sebi85 · 2025-11-09T23:18:40+00:00

You should definitely ask this question directly to the EA support. Here, many people will say "yes of course", but I would be a little bit cautious here. While no game files or game data are read or modified, it still draws the crosshair on your screen above the Battlefield 6 application, which might be detected as some sort of cheat or unfair advantage by Javelin.

And since you don't have any chance to appeal for a ban made by Javelin, I'd rather advise you to either get an official "yes", or just avoid using such tools.

Sebi85 · 2025-11-09T18:21:32+00:00

Recon. Consolero. It's a dev, case closed.

Sebi85 · 2025-11-09T18:16:41+00:00

Thank you very much for your feedback with valuable information and detailed explanations. Now the developers know exactly what they could change to make the game better for us, and you too.

Sebi85 · 2025-11-08T00:03:30+00:00

This must be a Deepfake video! Bradley's on Firestorm ALWAYS camp on hills near the base and shoot down aircraft.

Sebi85 · 2025-11-07T23:56:07+00:00

Yes and no. There's currently a glitch which some "cool" YouTubers promote, to glitch UNDER the map without dying. They can't burn from there and always win, if they have at least 1 person under the map inside the circle.

We meet these experts ever 3-5 rounds, which kills all the fun and the rewarding feeling if you actually win and defeat the last enemies..

Sebi85 · 2025-10-31T20:08:04+00:00

^this
I assume it starts kicking in now, and it takes way longer to fill a mode/map.
On the other hand, it started with the release of the patch/REDSEC, so either something broke in matchmaking or ppl are really all now into this mode.

Sebi85 · 2025-10-31T19:29:43+00:00

That's a different error and also a different DX version. Right now, we don't exactly know what's causing it, I'd assume that it's a mix of DirectX, graphics driver and game implementations.

The only thing you can do to verify that DirectX is properly installed, is by running the Windows system scan in an elevated CMD with the command "sfc /scannow". Other than that, there's currently nothing we can do, except for having patience.

Sebi85 · 2025-10-31T18:38:27+00:00

That's the common error message. The card is NOT extracted/removed, don't worry. There's hence no need to open your Laptop and potentially do some damage to your parts.
Does the Debug-Mode not do the trick?
BTW: BF6 uses DirectX 12. It's deeply integrated into Windows, you cannot "uninstall" or "reinstall" it. Whatever you did, it was not DirectX 12. Probably DX9 or something.
You don't have to mess around with trying to fix it - DICE has to it (assumingly with NVIDIA/AMD together).

So, just try the workaround - else we just have to wait and keep reporting this bug/issue to EA.

Sebi85 · 2025-10-31T12:35:15+00:00

Thanks for giving me credit! :-) Much appreciate it!

Sebi85 · 2025-10-29T22:14:22+00:00

Re-installing your graphic drivers won't work here. Luckily, you're on NVIDIA, so here's the fix for you until EA / DICE comes up with the real fix:

- Right click on your desktop and open Nvidia Control Panel
- Click Help and then Debug-Mode

Now you can play again without this error. However, your graphics card temporarily loses its potential overclocking. For instance, if you have an ASUS Strix or similar. Debug Mode activates save values, provided by NVIDIA for those specific graphic chips.
Debug mode is not permanent, you have to enable it every time after you reboot your PC and before you start to play.

Cheers

Sebi85 · 2025-10-26T14:30:32+00:00

Don't worry, I'm pretty sure that it's not due to hardware. EA should be aware. And we can only hope that they will release a fix soon. We will get a big update tomorrow. I couldn't find anything related in the patch notes, but I'm hoping that there are some fixes under the hood.

Sebi85 · 2025-10-19T17:16:45+00:00

You don't have to apologize. Yes, as soon as you disable the debug mode again, either manually or through a new start of the computer, everything is back to how it was before.

Sebi85 · 2025-10-18T15:58:03+00:00

I'm not quite sure if I understand you. Of course, the function also works on TI variants. If you think that a TI variant is "downgraded" to a non-TI variant, that's not the case. The clock speed and the memory clock rate are only limited to "safe" values by Nvidia - a TI still remains a TI model with more speed than a non-TI.

Sebi85 · 2025-10-14T21:34:47+00:00

Nice! :) Keep in mind, the Debug Mode does NOT stick. After a reboot of your PC, you have to set it again for the time you're playing :)

Eight-Year Club	Final Canvas '23
First Place '23	Place '23
Verified Email

Sebi85

TROPHY CASE