Not working properly with Madcatz xbox 360 wired controller

[GoogleCodeExporter]

Describe your system:
 - Operating System (be specific):Crunchbang linux waldorf (based on debian wheezy)
 - Machine type (32-bit or 64-bit):64-bit
 - Mupen64Plus version:Version 1.99.5

 - Plugins used:default plugins

Describe the problem:I finally got my controller to work with mupen64plus by 
editing the /usr/share/games/mupen64plus/InputAutoCfg.ini but and I set it to 
use a standard button setup but the buttons are all whacky.

Please provide any additional information below.
The c-stick doesn't work right, the b button is being the down on the c-button, 
and all sorts of other weird combinations. I have tested my controller with 
jstest-gtk and all buttons are good and working. My setup is:
[Mad Catz Wired Xbox 360 Controller]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
DPad R = hat(0 Right)
DPad L = hat(0 Left)
DPad D = hat(0 Down)
DPad U = hat(0 Up)
Start = button(7)
Z Trig = axis(5+)
B Button = button(2)
A Button = button(0)
C Button R = axis(3+)
C Button L = axis(3-) 
C Button D = axis(4+)
C Button U = axis(4-)
R Trig = button(5)
L Trig = button(4)
Mempak switch = 
Rumblepak switch = 
X Axis = axis(0-,0+)
Y Axis = axis(1-,1+)

Original issue reported on code.google.com by t.mieste...@gmail.com on 31 May 2012 at 3:55

[GoogleCodeExporter]

First thing: please test it again with sdljoytest. SDL in Debian Wheezy has a 
bug that makes some gamepads behave quite weird (some axis not working and 
similar things).  http://bugs.debian.org/673324

Then I am not sure whether this configuration is now a working one or it is the 
whacky one. Do you mean by wacky the unusual mappings of n64 buttons to your 
gamepad?

And you should not edit  /usr/share/games/mupen64plus/InputAutoCfg.ini - it 
will be overwritten when I upload a new package to the Debian archive and you 
update. The correct place would be ~/.config/mupen64plus/mupen64plus.cfg

The configuration can also be changed with wxmupen64plus. 

Original comment by s...@narfation.org on 1 Jun 2012 at 6:34

[GoogleCodeExporter]

Original comment by s...@narfation.org on 1 Jun 2012 at 6:35

• Added labels: Component-SDL-Input

[GoogleCodeExporter]

But everything shows as working on the controller on jstest-gtk...?_? And the 
configuration was a modified version of 
http://code.google.com/p/mupen64plus/wiki/ControllerSetup and I checked 
jstest-gtk to set it to a standard configuration (standard being A button set 
to what is marked as A button on controller and so forth). And yes by wacky I 
mean unusual mappings of n64 buttons to gamepad when on mupen64plus, jstest-gtk 
shows the buttons as normal.

Original comment by t.mieste...@gmail.com on 1 Jun 2012 at 6:48

[GoogleCodeExporter]

Again: please use sdljoytest. It can be found on the download page of 
mupen64plus. I already explained what might be the reason for the problem

To sum up: The configuration you posted is working in jstest-gtk but not in 
mupen64plus

Original comment by s...@narfation.org on 1 Jun 2012 at 6:30

[GoogleCodeExporter]

Well I downloaded that and tried it and this happened

todd@shadow-lugia:~/downloads$ ./SDLJoyTest-linux32
There are 1 joysticks attached
Joystick 0: Mad Catz Wired Xbox 360 Controller
       axes: 6
      balls: 0
       hats: 1
    buttons: 11
Then after I did ./SDLJoyTest-linux32 --help a window opened and I could see 
some squares move and stuff when I pushed buttons.

Original comment by t.mieste...@gmail.com on 1 Jun 2012 at 7:28

[GoogleCodeExporter]

But i saw that you are using the 32 bit version on 64 bit... please don't do 
that because it uses a complete different version of SDL. Do get a 64 bit 
version, please do following steps:

$ sudo aptitude install libsdl1.2-dev
$ wget http://www.libsdl.org/release/SDL-1.2.15.tar.gz
$ tar xvf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15/test
$ gcc `sdl-config --libs --cflags` testjoystick.c -o testjoystick
$ ./testjoystick 'Mad Catz Wired Xbox 360 Controller'

You can now see in the console the keycodes of the buttons you pressed + a 
visual feedback in the window

Original comment by s...@narfation.org on 2 Jun 2012 at 6:39

[GoogleCodeExporter]

I would also recommend that you either upgrade libsdl1.2 to 1.2.15-4 or 
downgrade to 1.2.14-6.1 to see whether the button codes are different with 
these version

Original comment by s...@narfation.org on 2 Jun 2012 at 6:42

[GoogleCodeExporter]

Well the libsdl I have I installed through the standard wheezy repo, I'm sure 
that's the normal one for 64bit otherwise I wouldn't see it in my repo and it 
is version 1.2.15-3 which is the latest version for wheezy. I was only using 
the 32bit of the sdljoytest because I didn't see a 64bit one in the download 
page.

Original comment by t.mieste...@gmail.com on 3 Jun 2012 at 12:11

[GoogleCodeExporter]

Nobody said that 1.2.15-3 is not the normal one. But the link I gave shows that 
this version is buggy (1.2.15 to be more precise). That's the reason why I 
asked to change to another version.

The 32 bit compat libraries (ia32-libs-20120102) currently have an older 
version (1.2.14-6.1 to be more exact). So testing with 32 bit version will not 
be representative when using for the other components the 64 bit version.

Original comment by s...@narfation.org on 3 Jun 2012 at 2:37

[GoogleCodeExporter]

Alright well

todd@shadow-lugia:~/SDL-1.2.15/test$ gcc 'sdl-config --libs --cflags' 
testjoystick.c -o testjoystick
gcc: error: sdl-config --libs --cflags: No such file or directory

Original comment by t.mieste...@gmail.com on 3 Jun 2012 at 4:35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

` and not '

Original comment by s...@narfation.org on 3 Jun 2012 at 5:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Well the error keeps looking like:

testjoystick.c:1:1: error: stray ‘\177’ in program
testjoystick.c:1:1: error: stray ‘\2’ in program
testjoystick.c:1:1: error: stray ‘\1’ in program
testjoystick.c:1:1: error: stray ‘\1’ in program
testjoystick.c:1:8: warning: null character(s) ignored [enabled by default]

and it keeps doing that for a lot of lines.

Original comment by t.mieste...@gmail.com on 3 Jun 2012 at 7:30

[GoogleCodeExporter]

Also 

todd@shadow-lugia:~/SDL-1.2.15/test$ ./testjoystick.c `Mad Catz Wired Xbox 360 
Controller`
bash: Mad: command not found
There are 1 joysticks attached
Joystick 0: Mad Catz Wired Xbox 360 Controller
       axes: 6
      balls: 0
       hats: 1
    buttons: 11

Original comment by t.mieste...@gmail.com on 3 Jun 2012 at 7:40

[GoogleCodeExporter]

> testjoystick.c:1:1: error: stray ‘\177’ in program
> testjoystick.c:1:1: error: stray ‘\2’ in program
> testjoystick.c:1:1: error: stray ‘\1’ in program
> testjoystick.c:1:1: error: stray ‘\1’ in program

This happens when you overwrote the source file with the binary and then try to 
compile the binary.

> todd@shadow-lugia:~/SDL-1.2.15/test$ ./testjoystick.c `Mad Catz Wired Xbox 
360 Controller`
> bash: Mad: command not found
> There are 1 joysticks attached
> Joystick 0: Mad Catz Wired Xbox 360 Controller
>        axes: 6
>       balls: 0
>        hats: 1
>     buttons: 11

No, here I used ' and not `

Original comment by s...@narfation.org on 3 Jun 2012 at 8:15

[GoogleCodeExporter]

Alright well that worked but it just shows squares, doesn't say button names on 
that window or on the terminal.

Original comment by t.mieste...@gmail.com on 3 Jun 2012 at 8:23

[GoogleCodeExporter]

It must be on the terminal that you used to start the program. Otherwise you 
did not compile what I told you, your sdl is completely broken or you fiddled 
around with the stdout file descriptor.

Original comment by s...@narfation.org on 3 Jun 2012 at 8:38

[GoogleCodeExporter]

Well you forgot to mention to compile it, compiled it and the only testjoystick 
I see is the testjoystick.c which is not an executable file, so I had to run it 
in a terminal and this time same thing happened except it didn't open a new 
window it just said 

There are 1 joysticks attached
 Joystick 0: Mad Catz Wired Xbox 360 Controller
        axes: 6
       balls: 0
        hats: 1
     buttons: 11

Original comment by t.mieste...@gmail.com on 3 Jun 2012 at 9:02

[GoogleCodeExporter]

> Well you forgot to mention to compile it,

No, i gave the instructions in comment #6

> compiled it and the only testjoystick I see is the testjoystick.c which is 
not an executable file

I told you how to compile it in step 5 of comment #6

> , so I had to run it in a terminal and this time same thing happened except 
it didn't open a new window it just said 

I told you in step 6 of comment #6 what you have to do to run it and get a 
window and terminal output

Original comment by s...@narfation.org on 3 Jun 2012 at 9:14

[GoogleCodeExporter]

Alright well I did that and again it still doesn't list the buttons in the 
window that pops out of the terminal it just shows squares when I push buttons 
etc. and it doesn't say what buttons were pressed on the terminal. Ok well 
maybe it lists the buttons but it keeps on showing axis info so fast and so 
much I can't read the buttons.

Original comment by t.mieste...@gmail.com on 3 Jun 2012 at 9:26

[GoogleCodeExporter]

I never said that it should show any text in the new window.

And when you have too much information... just remove it.

$ ./testjoystick 'Mad Catz Wired Xbox 360 Controller'|grep -v 'axis'

Original comment by s...@narfation.org on 4 Jun 2012 at 6:28

[GoogleCodeExporter]

Unfortunately, the user did not reply with the necessary information

Original comment by s...@narfation.org on 18 Dec 2013 at 12:01

• Changed state: Invalid