ps3 controler analog irresponsive

[GoogleCodeExporter]

Describe your system:
 - Operating System (be specific):slackware linux 13.1
 - Machine type (32-bit or 64-bit):32-bit
 - Mupen64Plus version:1.99.3
 - Plugins used:standart

For visual artifacts, give:
- game name and CRC/MD5 hash (printed on console)
- description of the artifact (missing polygons, flashing, wrong colors,
etc)

Describe the problem:cant get the ps3 controller analog stick to work on any 
game (and a number of buttons), and cant find a way to make it work, or 
configure it, it remains irresponsive, sorry for my english tanks in advance

Please provide any additional information below., i have tried to edit the 
InputAutoCfg.ini, iv tried it on zelda oot mq, and starfox64, only start and 
square works

Original issue reported on code.google.com by slack...@gmail.com on 26 Sep 2010 at 2:20

[GoogleCodeExporter]

triying it the iv founf it only moves horizontally, and the controler seems to 
plusate

Original comment by slack...@gmail.com on 26 Sep 2010 at 5:27

[GoogleCodeExporter]

the analog only works on the diagonal, of the stick, and only sends it left or 
right, 

Original comment by slack...@gmail.com on 26 Sep 2010 at 6:03

[GoogleCodeExporter]

xx it's _unresponsive_. i can confirm it works fine on a mac, and there are 
corroborative reports for windows and ubuntu too. Ensure proper drivers are 
installed; it's possible you need to edit your controller configuration file as 
well, if sticks are being given nonstandard assignments.

Original comment by alexchan...@gmail.com on 25 Jan 2011 at 2:45

[GoogleCodeExporter]

I use ubuntu 11.04 and cant configure the buttons. Im using a ps3 control via 
bluetooth. Anyone knows how to configure it?

Original comment by rodnu...@gmail.com on 3 Aug 2011 at 12:23

[GoogleCodeExporter]

I have the same issue. The joystick only moves up and down, not left and right. 
Using the autoconfig. I'm running Fedora 19 64 bit. It used to work just fine. 
Very irritating! 

Original comment by 09f...@gmail.com on 7 Jul 2013 at 1:55

[GoogleCodeExporter]

Check that you are using SDL2 or SDL1.2 != 1.2.15 (1.2.15 has a bug which kills 
some axis on devices with many axis). Just try to compile the sdl 
tests/testjoystick.c (can be found in the SDL sources) and check what 
information it shows for when starting it with the correct parameter (most 
likely 0 for your joystick) and you move the axis. You can now change the mode 
of your joystick to 0 in mupen64plus.cfg and rearrange the buttons/axis (use 
the information from the testjoystick program).

For the SDL1.2 version:
wget http://hg.libsdl.org/SDL/raw-file/fba40d9f4a73/test/testjoystick.c -O 
testjoystick.c
gcc `sdl-config --cflags --libs` testjoystick.c -o testjoystick
./testjoystick 0

For the SDL2 version
wget http://hg.libsdl.org/SDL/raw-file/d6eabafa8776/test/testjoystick.c -O 
testjoystick.c
gcc `sdl2-config --cflags --libs` testjoystick.c -o testjoystick
./testjoystick 0

Original comment by s...@narfation.org on 7 Jul 2013 at 1:20

[GoogleCodeExporter]

I was just informed that the order of the gcc parameters are not 100% correct. 
Here is the fixed version:

For the SDL1.2 version:
wget http://hg.libsdl.org/SDL/raw-file/fba40d9f4a73/test/testjoystick.c -O 
testjoystick.c
gcc `sdl-config --cflags` testjoystick.c `sdl-config --libs` -o testjoystick
./testjoystick 0

For the SDL2 version
wget http://hg.libsdl.org/SDL/raw-file/d6eabafa8776/test/testjoystick.c -O 
testjoystick.c
gcc `sdl2-config --cflags` testjoystick.c `sdl2-config --libs` -o testjoystick
./testjoystick 0

Original comment by s...@narfation.org on 15 Dec 2013 at 12:06

[GoogleCodeExporter]

Unfortunately, the user don't seem to respond with additional information. It 
just looks like an SDL bug in the first place.

Original comment by s...@narfation.org on 18 Dec 2013 at 11:35

• Changed state: Invalid