danielb6611 / mupen64plus

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

controller configuration interface (or a similar workaround) #380

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
mupen64plus 1.99 really needs some kind of interface to configure your gamepad. 
if only a separate tool used to generate an InputAutoConfig code.

personally, i have been trying to use my ps3 controller on my windows partition 
with mupen. mupen has a configuration for the ps3 controller, but it doesn't 
work because to use the ps3 controller on windows you have to go through a tool 
called MotionJoy, and the controller isn't called PLAYSTATION(R)3 Controller 
it's called MotionJoy Virtual Game Controller. it can also emulate an xbox 360 
controller, which works ok on pc games, but gets really dodgy when i use it 
with mupen (for example, all of the c buttons are matched to different areas of 
the bottom right of the right joystick).

Original issue reported on code.google.com by darkmags...@gmail.com on 6 Aug 2010 at 12:36

GoogleCodeExporter commented 8 years ago
Since Mupen64Plus doesn't have a standard GUI yet, there likely won't be any 
interface for configuring buttons unless implemented in a 3rd-party GUI 
front-end.

You can add controllers yourself to the InputAutoCfg.ini file.  Just copy one 
of the other controller settings, paste it somewhere in the file, and rename it 
to [MotionJoy Virtual Game Controller] (however the name appears exactly).  As 
for the buttons, you'll just have to experiment with the numbers until you find 
the setup you like.  There are plenty of controller testing applications all 
over the web that will tell you what numbers correspond to which buttons.  
Also, analog sticks and I think the PS3 controller's L2 and R2 buttons (as well 
as the 360 controller's LT and RT) are axis inputs, so you'll have to find the 
right values for those too.  So for Mupen to recognize them correctly, you'd 
have to put something like "axis(5+)" or similar.

These kinds of development packages aren't really meant for typical end-users, 
so it's not so farfetched that something as simple as button configuration 
isn't all that intuitive just yet.

Original comment by TheReal...@gmail.com on 6 Aug 2010 at 4:55

GoogleCodeExporter commented 8 years ago
Here is a program (if you use Windows at least) so that you wont have to guess 
the numbers for the buttons:
http://code.google.com/p/mupen64plus/downloads/detail?name=SDLJoyTest-1.2.14-win
32.zip

Original comment by q.gu...@gmail.com on 6 Aug 2010 at 9:37

GoogleCodeExporter commented 8 years ago
the sdl joy test was the first thing i tried, but it only seems to print the 
number of buttons and axis that there are.

Original comment by darkmags...@gmail.com on 7 Aug 2010 at 4:36

GoogleCodeExporter commented 8 years ago
If you run it like "sdljoytest 0" then it will open a window and print (on the 
console) events from joystick #0, which is the first one.

Original comment by richard...@gmail.com on 15 Aug 2010 at 12:22

GoogleCodeExporter commented 8 years ago
There is a workaround: opening the config file with a text editor and setting 
the controls yourself.  I know it's not the most user-friendly thing but it 
will have to do until a good GUI front-end rises above the crowd.

Original comment by richard...@gmail.com on 1 Dec 2010 at 1:46