I'm not sure, it sounds like it might be a problem with SDL. If all else fails you can bypass the pygame joystick support, and just read from /dev/input/js0 yourself and create the same joystick pygame events manually. It's actually pretty easy but may be a tiny bit less flexible.
It may also be possible to define the number of axes a joystick has, I'm not sure. Any of the guys got an idea? Rene, Lenard? Should this be entered as a bug somewhere? -Luke On Sun, Aug 8, 2010 at 12:38 PM, Coto <[email protected]> wrote: > Thanks for the clue, > > I used jstest /dev/input/js0 and it prints: > > Joystick (Licensed by Sony Computer Entertainment America Harmonix > Guitar for PlayStation®3) has 6 axes and 13 buttons. Driver version is > 2.1.0. > > When i use the strum bar it prints: > > Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 32767 > Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off > 8:off 9:off 10:off 11:off 12:off > > it shows me that the axis i have just used is the 6th axis. > > By the other side when i execute the SDLJoytest-GL it prints: > > Joystick 0 > Name:.........Licensed by Sony Computer Entertainment America > Harmonix Guitar for PlayStation®3 > Axes: 1 > TrackBalls:...0 > Buttons: 13 > > Wrong number of Axes!!!!! > > I think thats the problem but how can i solve it? > > Thanks! > > On Aug 7, 2:28 pm, Luke Paireepinart <[email protected]> wrote: >> On Sat, Aug 7, 2010 at 1:25 PM, Coto <[email protected]> wrote: >> > Hi, >> >> > Just to start my OS is Fedora 13, the version of pygame is: >> > pygame-1.9.1-1.fc13.i686, and the version of python is: >> > python-2.6.4-27.fc13.i686. >> >> > The problem comes when i try to use the strum bar of my PS3 rockband >> > guitar in Frets on Fire, FoFix or SDLJoytest-GL. >> > All other buttons are perfectly recognized, but when i try to >> > calibrate/configure the strum bar the software freezes, throws these >> > error and closes. >> >> > Fatal Python error: (pygame parachute) Segmentation Fault >> > Aborted (core dumped) >> >> Perhaps the joystick is identifying its number of axes / buttons >> incorrectly, so that SDL gets confused when it receives too much info? >> That's best guess off the top of my head. >> >> Try finding a non-SDL event utility and monitor the events that the >> guitar is sending, and then go into pygame and inspect the values for >> the # of axes/buttons that it claims are defined, and see if those >> values match up. >> >> Also, did you google using ps3 controller w/ SDL? this might already >> have been discussed. >> >> Either way, let us know how it turns out. >
