sysgodmin / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

XBOX controller buttons mapped incorrectly #505

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Describe your system:
 - Operating System (be specific): Mac OS X 10.7.4
 - Machine type (32-bit or 64-bit): 32
 - Mupen64Plus version: 1.99.5
 - Plugins used: all

Describe the problem:
I updated mupen to 1.99.5 and my XBOX 360 wireless controller no longer works 
properly.  The only buttons that are mapped are the D-Up button, which is 
mapped to the n64 start button, and a right stick X axis, which is mapped to 
the Z button.  I used SDLJoyTest and the buttons are all working properly, and 
proper outputs are coming forth.  I checked the .ini file and everything seems 
fine.   I deleted mupen and redownloaded it and the problem persisted.  The 
controller works perfectly with my SNES emu, so I can actively rule out the 
controller.  There MUST be something I am missing.  I will attach the .ini to 
make sure.

Please provide any additional information below.

Original issue reported on code.google.com by samuel.r...@gmail.com on 11 Jul 2012 at 4:08

Attachments:

GoogleCodeExporter commented 8 years ago
I should add something I forgot.  I downloaded a launcher for Mac OS X that was 
linked on your site shortly after.  After this whole ordeal happened, I went 
back to my previous Mupen build (I do not know which build this was, but it was 
pre-1.99.3, which had worked flawlessly to this point controller-wise, and the 
problem persisted inside this build as well.  I've since deleted (and used an 
App Cleaner to get rid of anything connected to) the launcher, as it didn't 
really do anything I couldn't do in terminal.

Original comment by samuel.r...@gmail.com on 11 Jul 2012 at 4:15

GoogleCodeExporter commented 8 years ago
Ok, something even wilder -- D-Down also save states.

Original comment by samuel.r...@gmail.com on 11 Jul 2012 at 4:16

GoogleCodeExporter commented 8 years ago
Please check that you don't use SDL 1.2.15

Original comment by s...@narfation.org on 13 Jul 2012 at 11:17