Logitech Precision gamepad hasn't worked since 2.3.3

[Sigma]

WinUAE is not receiving input correctly from my Logitech Precision gamepad. The X/Y axis (for left/right and up/down) are triggering a button 1 event. In some versions, it alternates button 1 / axis, and in some versions, it fires both events at once. (The button 1 and button 2 events are working properly.)

The gamepad works as expected with other programs, and responds as expected in Windows' calibration.

Using the test / remap functions in WinUAE, the gamepad works as expected in version 2.3.3, but has been broken since 2.4.0 (including in 2.6.0 b10). I had no active configuration file while testing.

[Toni Wilen]

Attach winuaebootlog.txt (run winuae with gamepad plugged in, exit and find the log manually or use Paths panel to open it)

[Sigma]

Please find attached a ZIP File with the logs. I didn't know which version you wanted, so I got a boot log from 2.3.3 and from 2.5.0.

[Toni Wilen]

USB HID dump in logs looks fine. (Input method changed to USB HID rawinput in 2.4, old versions used DirectInput which has not been "direct" since Windows ME..)

Do you get both axis and button events if you open Input panel and click Test-button? (Press same axis multiple times to see all events one by one)

EDIT: use 2.5.1 or 2.6 beta.

[Sigma]

The same problem occurs in 2.5.1 and 2.6.0 b10. In the Test panel, the events alternate axis / button if the axis is repeatedly pressed.

[Toni Wilen]

Hmm.. Does not feel like input receiving bug but some kind of default mapping bug.

Could you take a screenshot of input panel input target/source/etc window that shows your game pad config?

[Sigma]

I hope these are the screenshots you wanted. They were taken from 2.5.1.

I observed that in the Input panel, pressing the axis briefly flashed a "Joy2 Left" (or direction as appropriate) event before showing "Joy2 Fire".

EDIT:

Do you get both axis and button events if you open Input panel and click Test-button? (Press same axis multiple times to see all events one by one)

Now I realised what you meant when you asked this. I was previously looking at the Game Ports panel and not the Input panel. As I just mentioned, yes, it shows both events.

[Toni Wilen]

Still nothing obviously wrong. Must be something in USB packet decoding or this pad does something weird.. (Does it use standard Windows USB HID driver or does it use custom Logitech driver?)

More complex testing needed:

run winuae with -log -inputlog 4 command line parameters ("winuae.exe -log -inputlog 4")

Boot some default A500 or A1200 config (+pad enabled), no need for boot disk. Wait for WB insert disk screen.

Move dpad and press buttons, each change in pad's state should output hexadecimal log line (raw usb hid packet)

If log appears normally and each movement outputs new log line, quit emulator, run it again and do following sequence:

- full left
- release
- full right
- release
- full up
- release
- full down
- release
- press button 1
- release
- press button 2
- release
(same for all buttons)

Quit winae, attach winuaelog.txt.

[Sigma]

Originally Posted by Toni Wilen

Still nothing obviously wrong. Must be something in USB packet decoding or this pad does something weird.. (Does it use standard Windows USB HID driver or does it use custom Logitech driver?)

It uses Windows drivers (HID-compliant game controller and USB Input Device).

Please find attached the log file you requested. I performed the steps as you described them. There are 10 numbered buttons on the controller in addition to the axis.

[Toni Wilen]

Argh.. This was something too stupid..

Does http://www.winuae.net/files/b/winuae.zip work?

[Sigma]

It fixes the problem - the axis no longer seems to generates a button 1 event.

Unfortunately, it introduced another: If the axis is held in any direction, button 1 (fire) events are no longer received. (So that means you cannot, e.g. move and fire at the same time.)
I don't know if it affects other buttons as well; I cannot think of any programs I have that make use of two joystick buttons.

[Toni Wilen]

winuae.zip updated. Hopefully it really works now..

[Sigma]

Yes, it looks like it works as expected now. I tested it with a quick round of a game that uses a joystick and it worked. I'll give it a proper play-through later, just to be sure.

Thank you for taking the time to investigate and fix this issue!

[Toni Wilen]

Perfect, thanks!

Last bug was even more stupid, button press was detected correctly but it was also detected as released immediately..