Mouse aim disrupted/not possible with Simagic P2000 simracing pedals connected
Windows 11 23H2, R9 7950X and RTX 4090 FE. Peripherals connected are Coolermaster USB keyboard, Razer Deathadder V2 Pro, Simagic P2000-R simracing pedals and Fanatec Clubsport v3 shifter. During this playtest my Simagic Alpha wheelbase was not connected.
On loading into a game or training/shooting range, the view immediately and smoothly looked down to the floor. I was able to pan left or right but not up or down. Disconnecting the simracing pedals allowed mouselook to start working correctly again. This happened regardless of whether Simagic's "SimPro Manager" software was running.
I connected a USB XBox 360 pad, rebooted, and was still unable to look around using the left gamepad stick. I tried again with an Xbox One gamepad, same result.
I found that if I held the Simagic P2000 clutch pedal at around 50% (so the axis, with values ranging from -1 to +1, registered around 0) that full mouselook started working, so long as I kept holding the pedal at that point. If I fully depressed the clutch, the view immediately looked to the ceiling. If I let go, the view immediately looked to the floor.
I was also unable to rebind look up/down in the menu while the pedals were connected and registering non-zero input on the clutch Axis. As soon as I disconnected the pedals' USB cable, BF6 immediately began to respond correctly to the mouse.
As other people have said, the mouse works fine in the UI before a game, it's only during the game that input is not correctly handled.
According to https://hardwaretester.com/gamepad tester, the P2000 Haptic pedals enumerate as USB Device 1. My theory is that BF6 is mistakenly interpreting the device as a gamepad, improperly interpreting Axis 3 as look up/down. (For these pedals, Axis 3 is the clutch, Axis 4 is the brake and Axis 5 is the accelerator. All axes register -1.00000 when not being pressed.)
BF6 should not be interpreting pedals or devices - which are clearly not gamepads - as control inputs without being explicitly bound in the gamepad bindings page. This is a major bug, because people nowadays have various peripherals connected (HOTAS, simracing, etc) which should not need disconnecting. No other games I've played in the last decade misinterpret inputs like this, or allow them to supercede or override previously bound mouse X/Y axis inputs, unless bind is specifically overwritten by the user.
