Re: [mupen64plus] New InputAutoCfg

[Richard Goedeken]

It looks like this controller is mapped differently in Windows than in OSX.
Your config only sets up the first port. Can you also configure the second
port as well? You can look at the "[OSX: USB GamePad]" section to see the syntax.

Thanks,
Richard

On 04/15/2013 12:06 PM, tonyb...@gmail.com wrote:
> I've added support for the Mayflah N64 Controller Adapter on Windows. The
> current config file only supports this controller for osx.
>

[tony971]

Well I don't currently have a second controller to attempt this with and even if I did, I don't know where to find out which button which. However, I did find something very useful. Apparently, an earlier iteration of this device was previously posted about here. The configurations are nearly identical. I'm not sure why the c-buttons are different but you'd have a better chance at knowing that I would. Here's the link to the old thread.

https://groups.google.com/forum/?fromgroups=#!topic/mupen64plus/sENZgRpG3og

[tony971]

Actually, the more I look at it, it seems to be the exact controller. The name in Windows is the only thing I can find different about it. As far as the difference in the mappings, the c-buttons are viewed as a z-axis and were probably configured to differently zero-ed calibrations. Or I'm a noob and I'm just talking about things I don't understand. Whichever.

[tony971]

I've gotten a second controller, so if someone could tell me what program to use to button map, it would be great.

Thanks,
Tony

[Richard Goedeken]

There is a joystick test program on the download page of our google code site.
It's called "SDLJoyTest". You run it from the command line. With no
parameters it lists the found joysticks, with a parameter of '0' it tests the
first joystick, etc.

Richard

[tony971]

The command prompt automatically closes itself shortly after running a few lines. This happens to me whenever I try running a ROM straight from mupen64plus, too, though. I think it's some setting I have set wrong.

[Richard Goedeken]

You are probably just double-clicking on the mupen64plus-ui-console.exe,
right? To run it from the console, you need to open up a dos/command prompt,
then use the "cd" command to navigate to the directory containing mupen64plus,
and then enter the command. You must give it at least one parameter, which is
a path to your ROM. So, something like this:

> cd Desktop\Mupen64plus-1.99.5
> mupen64plus-ui-console.exe C:\Roms\SuperMario.z64

If you give it the parameter "--help", it will tell you all of the available
options.

Regards,
Richard

[tony971]

No I right click on the ROM and click open with... and choose mupen64plus from the nightly build. It starts running it and then self-closes. I'm more concerned about the sdljoytest though, since the GUI's circumvent the need for it.

[Sven Eckelmann]

On Thursday 18 April 2013 05:16:30 tony971 wrote:
> No I right click on the ROM and click open with... and choose mupen64plus
> from the nightly build. It starts running it and then self-closes.

Sounds like a problem to find the plugins but it is hard to check this without
getting more output from you.

> I'm more
> concerned about the sdljoytest though, since the GUI's circumvent the need
> for it.

sdljoytest needs a parameter to attach to a joystick and print the joystick
input information. You can use cmd or powershell under windows to get a
terminal and add parameters to the call.

But can't you use wxmupen64plus or m64py to generate the config and then post
the relevant mupen64plus.cfg parts?

Kind regards,
Sven

[tony971]

Very good point. And thanks for posting the path of least resistance to the noob! I've got the config here.

[Input-SDL-Control1]

# Mupen64Plus SDL Input Plugin config parameter version number.  Please don't change this version number.

version = 1.000000

# Specifies whether this controller is 'plugged in' to the simulated N64

plugged = True

# Specifies which type of expansion pak is in the controller: 1=None, 2=Mem pak, 5=Rumble pak

plugin = 2

# If True, then mouse buttons may be used with this controller

mouse = False

# Specifies which joystick is bound to this controller: -2=Keyboard/mouse, -1=Auto config, 0 or more= SDL Joystick number

device = 0

# SDL joystick name (name check disabled if this is empty string)

name = "USB GamePad"

# Scaling factor for mouse movements.  For X, Y axes.

MouseSensitivity = "2.00,2.00"

# The minimum absolute value of the SDL analog joystick axis to move the N64 controller axis value from 0.  For X, Y axes.

AnalogDeadzone = "4096,4096"

# An absolute value of the SDL joystick axis >= AnalogPeak will saturate the N64 controller axis value (at 80).  For X, Y axes. For each axis, this must be greater than the corresponding AnalogDeadzone value

AnalogPeak = "32768,32768"

# Digital button configuration mappings

DPad R = "hat(0 Right)"

DPad L = "hat(0 Left)"

DPad D = "hat(0 Down)"

DPad U = "hat(0 Up)"

Start = "button(9)"

Z Trig = "button(8)"

B Button = "button(2)"

A Button = "button(1)"

C Button R = "axis(3-)"

C Button L = "axis(3+)"

C Button D = "axis(2+)"

C Button U = "axis(2-)"

R Trig = "button(7)"

L Trig = "button(6)"

Mempak switch = "key(109)"

Rumblepak switch = "key(114)"

# Analog axis configuration mappings

X Axis = "axis(0-,0+)"

Y Axis = "axis(1-,1+)"

[Input-SDL-Control2]

# Mupen64Plus SDL Input Plugin config parameter version number.  Please don't change this version number.

version = 1.000000

# Specifies whether this controller is 'plugged in' to the simulated N64

plugged = True

# Specifies which type of expansion pak is in the controller: 1=None, 2=Mem pak, 5=Rumble pak

plugin = 2

# If True, then mouse buttons may be used with this controller

mouse = False

# Specifies which joystick is bound to this controller: -2=Keyboard/mouse, -1=Auto config, 0 or more= SDL Joystick number

device = 1

# SDL joystick name (name check disabled if this is empty string)

name = "USB GamePad"

# Scaling factor for mouse movements.  For X, Y axes.

MouseSensitivity = "2.00,2.00"

# The minimum absolute value of the SDL analog joystick axis to move the N64 controller axis value from 0.  For X, Y axes.

AnalogDeadzone = "4096,4096"

# An absolute value of the SDL joystick axis >= AnalogPeak will saturate the N64 controller axis value (at 80).  For X, Y axes. For each axis, this must be greater than the corresponding AnalogDeadzone value

AnalogPeak = "32768,32768"

# Digital button configuration mappings

DPad R = "hat(0 Right)"

DPad L = "hat(0 Left)"

DPad D = "hat(0 Down)"

DPad U = "hat(0 Up)"

Start = "button(9)"

Z Trig = "button(8)"

B Button = "button(2)"

A Button = "button(1)"

C Button R = "axis(3-)"

C Button L = "axis(3+)"

C Button D = "axis(2+)"

C Button U = "axis(2-)"

R Trig = "button(7)"

L Trig = "button(6)"

Mempak switch = "key(109)"

Rumblepak switch = "key(114)"

# Analog axis configuration mappings

X Axis = "axis(0-,0+)"

Y Axis = "axis(1-,1+)"

[tony971]

I know that the buttons are the same, but the controllers do move independently. I tested with a round of mario kart. But as far as the InputAutoCfg, wouldn't it make more sense to prioritize N64 controller adapters higher than third party controllers? If someone has an N64 controller and an Xbox 360 controller plugged in at the same time, I think the average user would want the N64 controller to be controller 1. 

[Richard Goedeken]

Thanks for sending the configuration. Apparently the Windows SDL library or
USB driver assigns 2 different SDL controllers to this device instead of a
single one like the unix systems. So Mupen64plus should support both N64 joy
ports as it is now.

Richard