Closed GoogleCodeExporter closed 8 years ago
Is this a USB joystick? Can you post the output of lsusb please? And the dmesg
output relating the joystick might be helpful.
Original comment by Adam.JT...@gmail.com
on 18 Jul 2013 at 12:06
Original comment by Adam.JT...@gmail.com
on 18 Jul 2013 at 12:06
Hi Adam!
Thanks for looking into it. I reported this bug 4 years ago, I was working with
a borrowed joystick (Genius MaxFighter F-16U, 4 button joystick with throttle).
Yes it was USB. Worked fine on both platforms but only got recognized by pyglet
on Windows. Right now I don't have it to test again. I returned it to the owner
and she is far away. And I don't have any other joystick with me, but I could
get one from a friend to test if it would help. Let me know!
Original comment by twoelz
on 18 Jul 2013 at 1:25
I probably won't find the same model to test.
Original comment by twoelz
on 18 Jul 2013 at 1:41
about the lsusb and dmesg (can't do those now of course) but back then I
remember testing this to make sure it was not a driver or linux problem. But it
wasn't. And the joystick was recognized by games and worked fine in Ubuntu.
Original comment by twoelz
on 18 Jul 2013 at 1:46
Sorry it took so long, thanks for replying so quickly despite that. If you
could test a joystick with the latest code that would be great so I can try to
fix it or close this issue.
Cheers.
Original comment by Adam.JT...@gmail.com
on 18 Jul 2013 at 11:01
No worries about the delay! I'll do it when I get a hold of a USB Joystick...
Original comment by twoelz
on 18 Jul 2013 at 11:13
Ok, tested both the latest trunk (rev eb6ff34e1ce8 July 17 2013) and the
released pyglet-1.2alpha1 (tar packaged, uploaded/released by Richard Jones
about a year ago: July 13, 2012).
Both worked!! (joystick and all buttons)
System info: on Ubuntu 12.10, running on a Dell Studio 17 (i7 core laptop). I
used the "show_input.py" script in the "examples" folder and also the
"input.py" (more verbose) script. The "joystick.py" script does nothing though.
I don't know what that script is supposed to do, and haven't looked into it,
but it just shows a red triangle with a tiny blue rectangle intersecting it
below, and nothing changes when I use the joystick. Is that an old test script,
is that broken? Anyway, seems that the important things are ok now!
Thanks you!
Original comment by twoelz
on 20 Jul 2013 at 9:56
Oh, forgot to mention: tested with this joystick:
Brand: Genius
Model: MaxFire Blaze2
Original comment by twoelz
on 20 Jul 2013 at 9:58
It is a PS2 style with USB (and PlayStation2) connection.
Original comment by twoelz
on 20 Jul 2013 at 9:59
Thanks a lot for testing that, I'll check that script and close this issue as
fixed. Cheers.
Original comment by Adam.JT...@gmail.com
on 20 Jul 2013 at 10:02
Original issue reported on code.google.com by
twoelz
on 20 Aug 2009 at 5:29