N64 controller and recalbox.

[boxcarpilot]

Because it falls into the topic title...

I'm guessing that will the xbox 360 controller will be enough... right?

I mean... I can map C buttons to the right stick(gamecube style)... and Z to be like RB (again gamecube style)... correct?

I wonder... is there any way I can do this like... manually? Maybe editing the same n64configfile I guess....

[Substring]

@boxcarpilot you wot need to edit anything, all is mapped in a clever way

[Victor Guimarães Barreto Alves]

hey guys....
well, I have the same problem here... I've changed the recalbox.conf and InputAutoCfg.ini using notepad++, and it didn't work.

does anyone knows what I might be doing in a wrong way?

Or, is there any possibility to share those files with me? Thanks in advance !!!

[Substring]

@Victor-Guimarães-Barreto-Alves have you read the topic at least ? N64 is autoconfigured.

[eagleeye1011]

@Substring

Okay so I just recently installed Recalbox 4.0.1 on my Raspberry Pi 3 and purchased the same controller as @Zelaf. I'm having trouble configuring it to work. I logged into root access, used the js command, which listed the Retorlink controller as something to the effect of, "Joystick (Generic Joystick .....)" I then used the "nano /usr/share/mupen64plus/InputAutoCfg.ini" command to edit the InputAutoCfg.Ini file but noticed my controller name (Joystick (Generic Joystick....) in the list with the exact same button configuration as that in the Github forum. Do I need type a whole new configuration or can I simply edit the configuration that matches my controller to read "Retrolink N64 controller" or something to that effect? Also, how do I add n64.configfile=dummy in recalbox.conf? Thanks for the help. Really excited about playing old N64 games.

[Substring]

@eagleeye1011 If it exists, just edit recalbox.conf to add the specified line. You can use nano ~/recalbox.conf to do so

[eagleeye1011]

@substring Can you explain this further so I understand? Very new to this whole thing.

[Substring]

@eagleeye1011 I guess editing the recalbox.conf must be detailled in the wiki ...

The easy way if you're running windows : open yout browser to http://recalbox/

[eagleeye1011]

@substring I've tried the "nano ~/recalbox.conf" command and it did nothing. I am more than likely very confused. What is the purpose of adding "n64.configfile=dummy" in recalbox.conf and how exactly do I do this step by step.

[Substring]

@eagleeye1011 said in N64 controller and recalbox.:

I've tried the "nano ~/recalbox.conf" command and it did nothing

How and where did you try it ? Have you followed https://github.com/recalbox/recalbox-os/wiki/Root-access-on-terminal-(EN) ?

Have you tried the URL I gave you ?

The n64.configfile=dummy prevents recalbox from auto-configuring N64 depending on your pad setup. It's mandatory if you want to customize your inputs as they don't follow the main configuration rule.

[fiveminutebreak]

@substring Tried every method to access InputAutoCfg, and cannot find a way to access it with write permission. Every time it opens as read-only. Is there something I'm missing or something that changed?

[acris]

Hello
https://github.com/recalbox/recalbox-os/wiki/Make-a-partition-writable-(EN)

[Substring]

@fiveminutebreak That file is in /recalbox/share/system/configs/mupen64 which is writeable

[dh04000]

@Substring

Hey, I recently purchased one of these controllers myself, and I can't seem to get it to work. I followed the (https://github.com/recalbox/recalbox-os/wiki/Configure-N64-controllers-(EN)) but jstest won't work. I added this (n64.configfile=dummy) to the end of my recalbox.conf file. I tried to manually edit the InputAutoCfg.ini file (nano /recalbox/share/system/configs/mupen64/InputAutoCfg.ini) and added the following to the end of the file:

[Generic USB Joystick]
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(9)
Z Trig = button(7)
B Button = button(8)
A Button = button(6)
C Button R = button(1)
C Button L = button(3)
C Button D = button(2)
C Button U = button(0)
R Trig = button(5)
L Trig = button(4)
Mempak switch =
Rumblepak switch =
X Axis = axis(0-,0+)
Y Axis = axis(3-,3+)

But, I don't think it sees the changes I made when I start up the emulator. Just what changes I made in the controller config GUI in the controller menu.

[dh04000]

@Substring

Never mind. I found the problem, I had an extra bracket far right to the controller name.

To help other's with this controller. here's my controller config:

[Generic USB Joystick]
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(9)
Z Trig = button(7)
B Button = button(8)
A Button = button(6)
C Button R = button(1)
C Button L = button(3)
C Button D = button(2)
C Button U = button(0)
R Trig = button(5)
L Trig =
Mempak switch =
Rumblepak switch =
X Axis = axis(0-,0+)
Y Axis = axis(3-,3+)

I unmapped the left trigger to use for the mupen64plus.cfg, where I mapped J0B4/B9 as exit emulation, J0B4/B6 as save state, and J0B4/B8 as Load state. These options are changed in the [Core Options].

What is the command for Hat0 left or right though..... do you know Substring?

[Substring]

@dh04000 said in N64 controller and recalbox.:

What is the command for Hat0 left or right though

i don't understand

[dh04000]

@substring said in N64 controller and recalbox.:

@dh04000 said in N64 controller and recalbox.:

What is the command for Hat0 left or right though

i don't understand

I should have written more clearly. What I was asking is what the symbol for directon pads looks like in the mupen64plus.cfg file. Player 1 Button 9 is J0B9. What is Player 1 direction pad right? J0(something)?

[Substring]

@dh04000 should check in the mupen doc, but i think they can't be mapped

[Chris Matthes]

@dh04000 said in N64 controller and recalbox.:

@Substring

Never mind. I found the problem, I had an extra bracket far right to the controller name.

To help other's with this controller. here's my controller config:

[Generic USB Joystick]
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(9)
Z Trig = button(7)
B Button = button(8)
A Button = button(6)
C Button R = button(1)
C Button L = button(3)
C Button D = button(2)
C Button U = button(0)
R Trig = button(5)
L Trig =
Mempak switch =
Rumblepak switch =
X Axis = axis(0-,0+)
Y Axis = axis(3-,3+)

I unmapped the left trigger to use for the mupen64plus.cfg, where I mapped J0B4/B9 as exit emulation, J0B4/B6 as save state, and J0B4/B8 as Load state. These options are changed in the [Core Options].

What is the command for Hat0 left or right though..... do you know Substring?

thank u so much! works with my 1€ N64 USB Controller on ebay

[dh04000]

@chris-matthes said in N64 controller and recalbox.:

@dh04000 said in N64 controller and recalbox.:

@Substring

Never mind. I found the problem, I had an extra bracket far right to the controller name.

To help other's with this controller. here's my controller config:

[Generic USB Joystick]
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(9)
Z Trig = button(7)
B Button = button(8)
A Button = button(6)
C Button R = button(1)
C Button L = button(3)
C Button D = button(2)
C Button U = button(0)
R Trig = button(5)
L Trig =
Mempak switch =
Rumblepak switch =
X Axis = axis(0-,0+)
Y Axis = axis(3-,3+)

I unmapped the left trigger to use for the mupen64plus.cfg, where I mapped J0B4/B9 as exit emulation, J0B4/B6 as save state, and J0B4/B8 as Load state. These options are changed in the [Core Options].

What is the command for Hat0 left or right though..... do you know Substring?

thank u so much! works with my 1€ N64 USB Controller on ebay

I'm glad that I was able to help you with my documentation.