https://bugs.winehq.org/show_bug.cgi?id=40658
--- Comment #21 from Paul geoff.pvgn1@gmail.com --- (In reply to Rémi Bernon from comment #20)
Thanks, I'll have a look.
FWIW dinput has some builtin deadzone and saturation calibration features, it should be implemented but it's not persistent yet or easily configurable either, only programmatically accessible by any any application which may set it.
We could think of having it persistent and exposed in joy.cpl to ease the setup of Wine joysticks.
I see. Since the consensus seems to be that the application should be controlling the deadzone, I'd be all for leaving it up to that, conditionally to whether the app does it well! A good point was made at the link I offered, which is if the application employs any math to calculate a variable deadzone, then a presence of a lower-level deadzone would skew the results. My only goal in using the js device node was to use 'jscal' to actually eliminate the built-in deadzones at the time.