[Bug 9720] deadzone regression on eventX input devices

wine-bugs at winehq.org wine-bugs at winehq.org
Thu Sep 20 07:24:10 CDT 2007


--- Comment #3 from Gerald Folcher <geraldf2 at free.fr>  2007-09-20 07:24:09 ---
Correct me if I'm wrong but I think there's no way/tool to change
these deadzones under Linux. In this case then shouldn't Wine avoid
using this info to initialize deadzones if there is no way for a Linux
user to change these values ?

(Btw, no, the Windows game does not provide a deadzone configuration,
but there's no such deadzone problem under MS-Windows)

Go figure, it seems my driving wheel device (or is it the driver ?)
report some "flat" value even on the pedals (accelerator and brake)
axes (I think it's what is used to set the deadzone, right ?). What
sense does it makes to have a deadzone on a pedal ? Yet one is
reported, and now used by Wine, at least in this case I would say
these values are bogus and should not be used. (And I won't argue
about the pure evilness of a deadzone on the wheel itself).

I don't understand how all this works, but taking some very wild
guesses: if it's hardwired in the device then it's really bad to use
this info without providing a configuration option to not use it. If
it comes from the driver but there's no way for the user to change
these values that's bad too, thought in this case it may be useable,
but only some day in the future, eventually.

Now if you can (you can't) point me to a way to configure/turn off
these deadzone values you win :)

Thanks for reading, and I hope I don't sound too annoying, I'm still
thankful for the work you all do on Wine.

Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the wine-bugs mailing list