lr-mupen64plus Control problem

Sid1968

Raspberry Pi4 with RetroPie 4.6.6.

Hello friends,
I use an arcade joystick with 10 buttons under RetroPie, which works great with all the emulators I use.

Well except for one. With the "lr-mupen64plus" I can control Nintendo 64 games without any problems, but when I play "Aeoroguage", for example, every time I move the stick forwards, the vehicle is moved upwards, but the camera perspective is also changed at the same time. It's frustrating! Can you turn that off?

Cheers
Sid1968

dankcushions

@Sid1968 when you did your initial binding (https://retropie.org.uk/docs/First-Installation/#configure-controllers) did you bind your joystick to the digital (dpad) controls AND as your right analog controls? that would cause issues like this, since by default the 'C' buttons are mapped to the right analog stick.

if you reset your controls via Retropie Setup Script >> Manage Packages >> Manage Core Packages >> EmulationStation >> Configuration / Options >> Clear / Reset EmulationStation Input Configuration, you can be sure that binding is not done.

Sid1968

No i mapped the Joystick only as DPAD. Should i map it as left analog joystick instead?

dankcushions

@Sid1968 nope.

can you paste this please: /opt/retropie/configs/n64/InputAutoCfg.ini

Sid1968

Of course. I use the "MY-POWER CO.,LTD. USB Joystick".
I correct: Camera changes by moving joystick downwards.

; InputAutoCfg.ini for Mupen64Plus SDL Input plugin

; Keyboard_START
[Keyboard]
plugged = True
plugin = 2
mouse = False
DPad R = key(100)
DPad L = key(97)
DPad D = key(115)
DPad U = key(119)
Start = key(13)
Z Trig = key(122)
B Button = key(306)
A Button = key(304)
C Button R = key(108)
C Button L = key(106)
C Button D = key(107)
C Button U = key(105)
R Trig = key(99)
L Trig = key(120)
Mempak switch = key(44)
Rumblepak switch = key(46)
X Axis = key(276,275)
Y Axis = key(273,274)
; Keyboard_END

; Gamepad PC USB Controller_START 
[Gamepad PC USB Controller]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
Mempak switch = 
Rumblepak switch = 
C Button D = button(14) axis(3+) 
C Button L = axis(2-) 
L Trig = button(8) 
Start = button(3) 
Y Axis = axis(1-,1+)
DPad U = button(4) 
C Button U = button(15) axis(3-) 
A Button = button(13) 
DPad D = button(6) 
X Axis = axis(0-,0+)
R Trig = button(9) 
DPad R = button(5) 
B Button = button(12) 
DPad L = button(7) 
C Button R = axis(2+) 
Z Trig = button(10) 
; Gamepad PC USB Controller_END 


; MY-POWER CO.,LTD. USB Joystick_START 
[MY-POWER CO.,LTD. USB Joystick]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
Mempak switch = button(10) 
Rumblepak switch = button(11) 
L Trig = button(2) 
Start = button(9) 
C Button D = button(7) 
A Button = button(1) 
R Trig = button(3) 
C Button U = button(6) 
B Button = button(0) 
Z Trig = button(4) 
X Axis = hat(0 Left, 0 Right) 
Y Axis = hat(0 Up, 0 Down) 
; MY-POWER CO.,LTD. USB Joystick_END 


; e4you e4you Retro Fun_START 
[e4you e4you Retro Fun]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
Mempak switch = 
Rumblepak switch = 
A Button = button(0) 
C Button D = button(1) 
X Axis = axis(0-, 0+) 
Y Axis = axis(1-, 1+) 
Z Trig = 
; e4you e4you Retro Fun_END

dankcushions

this one looks problematic:

; Gamepad PC USB Controller_START 
[Gamepad PC USB Controller]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
Mempak switch = 
Rumblepak switch = 
C Button D = button(14) axis(3+) 
C Button L = axis(2-) 
L Trig = button(8) 
Start = button(3) 
Y Axis = axis(1-,1+)
DPad U = button(4) 
C Button U = button(15) axis(3-) 
A Button = button(13) 
DPad D = button(6) 
X Axis = axis(0-,0+)
R Trig = button(9) 
DPad R = button(5) 
B Button = button(12) 
DPad L = button(7) 
C Button R = axis(2+) 
Z Trig = button(10) 
; Gamepad PC USB Controller_END

the c U/D buttons appear to be mapped to buttons AND an axis. however the joystick you say you use appears fine.

do similar things happen with all games? eg, in mario 64 the C buttons are mapped to the camera. in goldeneye 64 the D pad and C buttons are mapped to looking, so you should see some strange behaviour if it's a binding problem.

Sid1968

I dont use the device "; Gamepad PC USB Controller_START". That must be a standard entry, so i deleted the entry. But it didnt fixed the problem.

In "Aeoroguage" Camera changes by moving joystick downwards.

In "Mario Kart64" Camera changes by moving joystick upwards.

In "Mini Racers" Camera changes by moving joystick downwards.

dankcushions

oh hang on, you're using lr-mupen64plus, so that input file is redundant, as it uses retroarch configs.

in which case, you can have a look at the core options to see if there's anything relevant: https://retropie.org.uk/docs/RetroArch-Core-Options/

or core input remapping to rebind it completely: https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

however for pi4, i wouldn't recommend using lr-mupen64plus at all - it has a lot of issues and is out of date. instead use mupen64plus-gliden64 with this fix: https://www.reddit.com/r/RetroPie/comments/gc83sc/n64_mupen64plusgliden64_performance_fix/