Windows 10 has issues with mouse movement when raw input is turned off in-games. Mainly on low sensitivity or DPI the mouse will hitch and not move properly, this may be the cause of your issue and seems to affect games across the board not just BF2. The issue does however seem to be improved on the insider preview builds not there may be other stability issues with those builds so caution is advised before using them. On the insider builds there also seems to be an issue where the mouse will randomly continue floating off in the direction you were moving it after you stop moving your mouse but this seems rare.
Hmm.. All I know is that this is the first game I've played with raw mouse off with this issue. Using Windows 10 I never had this issue with other EA/FrostBite titles such as Battlefield 1, SW:Battlefront 1, BFH, or BF4.
Furthermore I do not have this issue with the new Call of Duty WWII or Destiny 2. It is ONLY with SW:Battlefront 2!! So something needs to be done about this. The game is literally unplayable for me!!
But if this is indeed issue with Windows 10 (1st time I've encountered this problem, play many games on Windows10) Then the developers could resolve it easily by simply adding a "Invert X-axis" option in the settings on top of the already existing "Invert Y-axis".. That's exactly what they did in Destiny2.
Raw mouse on or off is a basic option available in many games for a long time now. they need to figure out a way to get this fixed. It really feels like a step backwards!
@PossiblyNotLegitI decided to put your theory to the test. I have another rig running Windows 7 so I installed SW:BF2 on that system to find out for sure if this is a Windows 10 OS issue as you are professing or if it's truly on the game's development side.
And after testing it I can tell you that it did the EXACT SAME THING ON WINDOWS 7!! I set "GstInput.MouseRawInput" from 1 to 0 and it did the same thing as it did in Windows 10 (stuttery, stuck, broken mouse movement).
So I can say with absolute confidence that this is clearly a GAME BUG, NOT an OS issue and it needs to be fixed! There is absolutely no reason that your mouse movement should completely break because you disabled raw mouse input. Somebody on the team did not do their due diligence, that much is clear!
My only question now is how can I make sure that this gets to the right person at Dice/EA who can actually help get this corrected quickly?
<><>
@PossiblyNotLegit Do you have any other ideas? Can someone from the game development side maybe throw in some input? Again, there is absolutely NO reason why disabling raw mouse input should break the mouse look/movement.
Thing is that this has not been solved...
