Open nfp0 opened 1 year ago
Hi, thanks for this report. I've noticed this happening as well, but irregularly, ever since I merged in https://github.com/emilyst/hid-nx-dkms/commit/5df3aa676463f11141554388d099cf169db6c75f. Presumably this means the first-party hardware is reporting implausible calibration values sometimes. I haven't had a moment to track down whether this is a hardware issue or something on my end.
I should probably print out the supposedly implausible using hid_dbg
somewhere to get a better handle on it. I'll try to do that sometime soonish.
In any case, one question—have you noticed any actual calibration issues, such as drift?
In any case, one question—have you noticed any actual calibration issues, such as drift?
I have not noticed any drift. Why? Does the calibration also include values for deadzones?
But I noticed that, despite the log messages saying it failed to load user calibration, some form of calibration still seems to be present. I say this because with this dkms module, the joystick is usable, while if I blacklist hid_nintendo, the joystick is very badly calibrated, almost unusable.
Calibration data is failing to be loaded on the Pro Controller, as the log messages seem to indicate: