[Bug 9720] New: deadzone regression on eventX input devices

http://bugs.winehq.org/show_bug.cgi?id=9720

Summary: deadzone regression on eventX input devices
           Product: Wine
           Version: 0.9.45.
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: wine-directx-dinput
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

I don't know exactly with which Wine version this has been introduced
since I jumped from 0.9.42 to 0.9.45, so this may be in-between.

Previously (e.g with 0.9.42) there was no default deadzone using a
'/dev/input/eventX' input device (joystick/wheel), which was good. It
was similar to the behavior on MS-Windows (at least according to my
experience).

Now with Wine 0.9.45 there is a default deadzone which is really bad,
it effectively render my controller unusable. It is especially bad
with a driving wheel controller (really really bad), but it's bad even
with an analog stick joypad (I started using /dev/input/eventX instead
of /dev/input/js0 just because of that when I used such a pad). To be
honest I wonder why someone would even want a deadzone on his
joystick, it renders any fine control impossible.

If there is a way to turn off the deadzone (except from modifying the
source code) please someone tell me, but if it exists it should be
easily accessible (like in the winecfg utility) and turned off by
default (if only to reflect MS-Windows behavior).

Please tell me if you intend to keep this default deadzone anyway, so
that I know I'll have to edit Wine's source code every time I upgrade,
it's not a problem for me since I already have to do that to get force
feedback working anyway but I would be very sorry for the common folks
that just want to play.

Thanks for reading.