released - halfway - pressed
0 - (-32767)<-> (32767) - 0
but does it happen in reverse order when releasing pedal ?
seems the interpretation of this is up to the application really,I don't think that the change is interpreted, because the clutch value seems to be computed directly, i.e. applying the app. calibration value on the the axis value received from the kernel;
but /if/ the -32767 to 32767 change happens all around the 'halfway'
spot, maybe it is (in the app. engine) interpreted as 'change'
and it's effect applied to 'car engine' not directly, but integrated
(time-integral function applied) first ?
I'd say, for the clutch simulation it's the /change-in-time/ thatI agree, but trying to calibrate the axis produces the 'jump' effect also on the clutch value, so that either the first half of the axis isn't taken into account, or it produces full clutch already at halfway, and then value 0 after the halfway spot.
matters, not the /exact/ value; so no 'static' calibration is
ever going to be relevant (bar maybe the device telling us when the
pedal is fully pressed or fully released - in case app is not tracking
it)