search

apartmentEmulator / mupen64plus

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

Gamepads on OS X #312

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Mupen is unable to autoconfig some controllers on mac, due to the fact 
that they have different names under OS X.

You can perform a simple hack for this by changing the controller names 
in mupen64plus-input-sdl/src/autoconfig.c under sJoyConfigMap. for 
example, "Sony PLAYSTATION(R)3 Controller" becomes "PLAYSTATION(R)3 
Controller"
"Xbox 360 Wireless Receiver" becomes "Wireless 360 Controller" if you are 
using the tattiebogle driver. there are dualshock 3 (sixaxis) drivers already 
in place in 10.6 snow leopard.

The button mapping for the 360 controllers is off. (again, with the 
tattiebogle driver. i think it's the only 360 controller driver for mac, 
correct 
me if i'm wrong) the joystick seems to be find mostly, save for this: 
*picture attached* (i don't know what that's about, only happens with 360 
controller) although the buttons are way off. A and B are up and left on the 
D-pad, respectively, and, well... that tells you enough right there. if you 
need a button map (button #s to letters) i might be able to make one, 
although you should probably look on tattiebogle.net before you ask me to 
make one 0_o

Original issue reported on code.google.com by darkmags...@gmail.com on 14 Jan 2010 at 2:05

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by richard...@gmail.com on 14 Jan 2010 at 5:35

GoogleCodeExporter commented 8 years ago 
Okay, I just committed the OSX names for the 2 controllers.  Can you do me a 
favor
and build the latest from source and and fix up the PS3 controller settings by
editing the InputAutoCfg.ini file?  You can post or email the resulting 
settings and
I'll update the official .ini file.  I looked on the tattiebogle.net site but 
it only
gives low-level info about the hardware interface.  I have no idea how the OSX 
driver
and SDL translate that into button and axis numbers.

Original comment by richard...@gmail.com on 20 Jan 2010 at 2:10

GoogleCodeExporter commented 8 years ago 
the ps3 controller works by default, i tried messing with the settings on the 
ini file, but 
the button numbers there don't seem to correspond with the button names on my 
tester program. what do you use to find out the button ids?

Original comment by darkmags...@gmail.com on 31 Jan 2010 at 3:45

GoogleCodeExporter commented 8 years ago 
I looked around for OSX programs that could tell you the button IDs but didn't 
really
find anything too user-friendly.  You could always just make notes on what 
buttons do
what and experiment with the .ini file to figure out the mappings.  Or you could
install mupen64plus 1.5 and use the blight input plugin to set up the joystick 
and
send me the blight_input.conf file.

Original comment by richard...@gmail.com on 31 Jan 2010 at 6:14

GoogleCodeExporter commented 8 years ago 
Here's the blight_input.conf file you wanted. this has the most complete button 
mappings i could get for the 360 controller.

Original comment by darkmags...@gmail.com on 31 Jan 2010 at 8:48

Attachments:

GoogleCodeExporter commented 8 years ago 
The blight_input.conf file which you attached is incorrect; if you open it with 
a
text editor you can see some problems: the D-pad is only mapped to some keys, 
and
there is no mapping for the start button.  The way that the Mupen64Plus 1.5 
input
plugin handles the configuration is with a 'default' config file which is 
copied to
the user's home when the emulator is first run.  I think you attached the 
default
config file rather than the one which was modified when you set up the xbox 360
controller.  Please look for a blight_input.conf file in ~/.mupen64plus/ and 
attach
this one.

Original comment by richard...@gmail.com on 1 Feb 2010 at 3:51

GoogleCodeExporter commented 8 years ago 
yeah you're right, i copied the one from the .app file. here's the one from
~/.mupen64plus. looks like the mappings are right in the text editor.

Original comment by darkmags...@gmail.com on 1 Feb 2010 at 7:14

Attachments:

GoogleCodeExporter commented 8 years ago 
Okay, thanks for the update.  I have updated the InputAutoConfig.ini file in the
input plugin.  Please test one last time with the latest code and verify that it
works properly.

Original comment by richard...@gmail.com on 2 Feb 2010 at 2:11

GoogleCodeExporter commented 8 years ago 
yeah, it works fine, although i can't try it with the latest code that i cloned 
it
from.. something about zlib not being 64 bit.

Original comment by darkmags...@gmail.com on 2 Feb 2010 at 3:39

GoogleCodeExporter commented 8 years ago

Original comment by richard...@gmail.com on 2 Feb 2010 at 3:08

GoogleCodeExporter commented 8 years ago 
how do i apply this to the to the infoautocfg.ini there are alot of spaces and 
how do i just get it to recognize the controller properly and where can i find 
the mapping so i can also configure it myself?

Original comment by BFarbe...@gmail.com on 26 Apr 2011 at 2:47