Replies: 1 comment 1 reply
-
I'm guessing the "bad calibration" is being applied to XInput controllers specifically? For XInput controllers, Xidi gets controller data directly from XInput. I imagine XInput might ignore the calibration data, which is why Xidi-WinMM also appears to ignore it. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Using Windows 10's "Game Controllers" calibration function, I intentionally mis-calibrated several controllers in order to understand application behavior using Xidi-WinMM. Interestingly, the bad calibration (sticks only allowed to travel left or forward, leaving right and backward fully saturated) was completely ignored by Xidi-WinMM. That is, stick movement was 100% smooth, whereas tests without Xidi-WinMM reflected expected behavior - movements jumping wildly in the right and backward directions.
Removing the DLL and using the default OS library yielded testing results consistent with the bad calibration. Does Xidi-WinMM mask or ignore calibration data?
Beta Was this translation helpful? Give feedback.
All reactions