[Bug 48802] Logitech Extreme 3D Pro joystick works fine in joy.cpl but buttons wrongly mapped in Battlefield 4

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48802

--- Comment #14 from Luca Boccassi <luca.boccassi at gmail.com> ---
(In reply to Zebediah Figura from comment #13)
> Please don't paste logs in comments, but attach them instead.
> 
> Probably the most interesting case here is hidraw, since that should in
> theory match Windows exactly, without losing any information after passing
> through SDL or evdev. I own a Logitech Extreme 3D Pro, and according to my
> testing we're reporting all of the same data from the HID layer (at least
> since 5.5). Despite comment 12, the log pasted in comment 9 implies that the
> SDL backend was used. Can you please try disabling SDL and evdev, and
> enabling the hidraw backend instead?
> 
> I do see some apparent misbehaviour with hid.exe: only buttons 1 through 8
> are reported; the throttle is not reported anywhere (though the yaw does
> work), and the hat switch only seems to be reported when pressed upwards.
> However, this seems to be a reflection of bugs in hid.exe itself; I see the
> same behaviour on Windows. (Actually, Windows seems worse for some reason:
> it doesn't acknowledge yaw, the X axis doesn't seem to work right, and the
> hat switch only registers as "up" inconsistently.)

Sorry for not being more specific: the comments were reflecting incremental
testing, so the logs pasted in comment 9 were with the default settings in the
registry.

I have now disabled SDL and evdev in the registry, and I now see the exact same
behaviour you see in hid.exe.
However the situation in BF4 is now worse - while before X/Y axis and some keys
worked, now nothing does. No button, no axis - it's completely dead in the
water.
joy.cpl continues to work perfectly, it recognises everything correctly.

I'll attach the logs of bf4.exe ran with +hid,+hid_report,+plugplay - games
starts, went into settings, tried to bind a key to any joystick action.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.