PSA: Mouse Input is broken in this game (looks similar to bad frame timing)

smackup4u​ Stop confusing people please,

its all placebo last update didn't change anything, it can't be "a bit better" it's either fixed or not. Its a mouse priority problem not a high CPU usage one.. mine is at 50 to 70% all the time my framegraph is perfect. The mouse has a fixed and low polling rate, input priority might be bad too. Nothing to do with high cpu usage here.

They didnt say anywhere that it was cpu related, youre reading a post from another user regarding things dice did in 2042 to improve the way mouse aiming FEELS not looks. You can literally in 3 seconds prove it is not related to high cpu loads by going into the firing range and see the issue is still there. You people are not helping the situation. 

I believe you're mistaking the better feeling for the update they did to improve how much recoil affects mouse sens (which is an absolute -iq mechanic made to nerf mnk) . 125 polling rate is still there if I open bf6 then open my mouses software it shows 125hz. 

Endgame gear op1 mouse btw 

Testing this further it doesn't seem to change my polling rate in my mouse software consistently when i launch the game.  Yet no matter the polling rate I select it still stutters in game so I guess it's overriding my mouse software and not updating it or informing it I'm guessing? if someone has another software or a way to externally test the polling rate while the game is open and changing your mouse software settings plz experiment. 

Maybe also try running your mouse software in administrator so maybe that makes bf6 not override it. Just spitballing 

Except... Not really. 

Firstly: DICE's statements about anything should be taken with the biggest grain of salt imaginable. 

Secondly: how is it that we have people reporting this issue while CPU usage is reasonable? I understand that CPU usage is non-linear, but I also have such a tweak and still experience the same issues as OP did.

Just want to share my thoughts, that the Winter Offensive update did improve my experience. It's still not perfect, but it feels better. I cannot provide hard numbers but I say got about 50 percent improvement.

For the record: I use a custom config to tweak the CPU usage of the game. And if you read the comments down below, DICE confirms, that the mouse polling problem is related to high CPU usage.

And another update without any fix for this awful broken mouse movement. Another slap in the faces of mature gamers who spent many K Euros in top end hardware and running this crap like a potato. We don't care about your snow ! 

Just by checking the patch notes, we can see so many pointless changes and a way to avoid the resolution of the No 1 problem on PC.

Not seeing an acknowledgement is also worrisome, considering these marketing playtest sessions, betas… it was spotted long time ago and nothing good is happening here.

This issue also impacts your aim accuracy, it’s not only visual disturbance. The mouse is actually not responding for few ms permanently ! How dare  a broken mouse input on a AAA PC shooter like someone also said ?

I am now more than convinced that this is a pure design choice to make this game only for controllers .

Cannot put this in my mind that it has passed any QC tests, it was agreed to release the game that way for PCs to disadvantage us.

This silence is literally unacceptable, we have been really patient. I just want my money back....

Can this issue be at least confirmed with a resolution plan ?

To be honest, my hope is gone and don't even feel the envy of playing this game in the future. I have predicted since the beginning that they will never fix it and it's actually happening. Design choices cannot be reversed and we got the confirmation. 

They reacted here just for political reasons, it never meant they will put this on their issues resolution log (if they actually have one).

• Mouse mode (wired or wireless)                 Wired
• Mouse polling rate (e.g. 1000Hz)              1000Hz
• Whether you’re using mouse software (like Razer Synapse)             G Hero 
• Where your mouse is plugged in (PC, monitor, hub, etc.)         PC USB 3.0
• Keyboard model and connection type (wired/wireless)       Steelseries Wired
• Keyboard polling rate            IDK
• Whether you’re using keyboard software          NO
• Where your keyboard is plugged in         USB 3.0
• Monitor model        PG27UCDM LG 
• Full PC specs (CPU, GPU with driver version, RAM)      Ryzen 7 9800X3D RTX 5090 32GBRAM
• Full Windows OS version (not just "Windows 11")     Win11 25H2
• Whether Gsync or VRR is enabled          Gsync ON
• Full screen mode (fullscreen, borderless, windowed)             Borderless
• Which platform do you play on (EA app or Steam)               Steam
• Any overlays active during play (Discord, EA app, Nvidia overlay, etc.)              Nvidia Overlay
• CPU and GPU usage percentages while playing                   GPU 100
• Whether the issue improves with a framerate cap (e.g. 125 FPS)           

I'm genuinely convinced it was intended they've deliberately done everything they can to cater to roller players. 400million dollar budget for a fps game there's absolutely no way they looked over the mouse input TWICE NOW (same problem in 2042). It took them an entire year to fix it in 2042 and that games mouse input is still borked. If bf6 wasn't as popular as it is the problem would still be getting ignored. I feel for the individuals that have to deal with the community backlash due to the incompetent design decisions of the game. 

Crossplay has ruined fps gaming on mnk they need to do input based matchmaking and stop trying to balance roller vs mnk it will never work. Look at apex and cod (not b07) for example it's all dominated by controllers because of aim assist. It's dumbfounding that the controller is mainstream for fps gaming in the first place. It's a sub optimal aiming device that requires computer assistance to compete because you can't replicate the precision that the mouse provides. Honestly I doubt this problem will be fixed anytime soon but I do hope so considering bf6 has potential but right now it feels like a f2p game that we got rug pulled on. Thanks for listening to my Ted talk o7 to my fellow suffering mouse aimers.

Thank you for this post!  I think dice should hire you to help with this problem.  My only observation about the CPU load aspect is that the mouse movement issue is consistent regardless of CPU  usage.  if I'm in the shooting range or in the middle of a large battle and i slowly move my mouse left and right its the same exact issue. i believe CPU load has nothing to do with this problem . obviously high cpu will lead to frame skips here and there but this issue is different.  Its very frustrating to me because mouse movement is the most BASIC FUNCTION of a fps game.  Dice and Battlefield studios really dropped the ball on this issue.

bromandingo​ I agree the inconsistent mouse polling rate issue should have been fixed a long time ago. I've been waiting over 9 years for a fix since Battlefield 1.

To answer your question about why controllers don't have stutter, but mouse does. Analog stick input from controllers is run through more smoothing and interpolation than raw mouse input. This smooths out the polling rate stutter for controllers.

Mouse input for vehicles has smoothing and interpolation applied to mouse input. Which is why people comment that there's less mouse stutter with vehicles.

I don't consider smoothing and interpolation a fix for mouse stutter. It adds lag and reduces aim precision. The real fix is coding the game engine to poll mouse inputs at a consistent and high frequency. Not an inconsistent and low frequency of 125Hz.

We noticed that the game was having difficulties prioritizing mouse input under high CPU load, thus impacting aim responsivity

-DICE

Translation: under high CPU load the game engine stops polling the mouse consistently and clumps mouse inputs together.

The actual input a mouse sends is X/Y axis counts. Most people refer to this as dots per inch (DPI), but mice actually send counts per inch (CPI).

Moving the mouse 1 inch to the right sends 800 X axis counts, for example.

Inversely, moving the mouse 1 inch to the left would send -800 X axis counts.

The game engine polls the mouse at 125Hz (every 8 milliseconds) and asks the mouse if it has any new X/Y axis counts to report. The game engine then moves the crosshair by that many X/Y axis counts. Up, down, left, right.

Unfortunately, the game engine isn't polling the mouse consistently at 125Hz or every 8ms. When a mouse poll is missed the game engine sees this as the mouse stops moving.

But the mouse is still moving and mouse counts are adding up on the mouse because it hasn't been polled in a while. When the mouse finally does get polled, the game engine sees a huge influx of backed up mouse counts suddenly get sent and moves the mouse twice as fast.

This constant stop, start, stop, start of mouse movement due to inconsistent mouse polling is what's causing mouse stutter and the framerate to feel lower than 60fps. Even though the game is actually running at 100+ fps with super smooth frame times.