@buzz @mitu I have a VirtualBox's Virtual Machine set to Debian (64 bits) running Raspberry Pi Desktop (https://www.raspberrypi.org/software/raspberry-pi-desktop/), which may be 32 bits?

Then I followed the guide on how to install RetroPie on Ubuntu/Debian https://www.raspberrypi.org/software/raspberry-pi-desktop/

@dan1300 Yes I tried that, under that config the Z trigger doesn't work and the B button doesn't work and A and B are swapped with each other and I think 1 or 2 other issues.

This is the controller I got:
https://www.amazon.com/gp/product/B0744DW55H/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

Which is identified in RetroPie as "SWITCH CO.,LTD. Controller (Dinput)"

@sade even if you manage to build emulators, expect crash and/or black screen nearly everywhere, most emulators provide no support or only partial support for big-endian cpus

@peggytam009 said in why does mupen64 run better on my old phone, even though it has same specs as the pi3?:

@dankcushions said in why does mupen64 run better on my old phone, even though it has same specs as the pi3?:

what RDP (video) plugin is your phone mupen running?

i'm guessing your phone's GPU is GLES 3.x (pi3 is GLES 2.x), so it can run yabasanshiro, which is a good android saturn emulator. we're yet to get it running great on even pi4, but it won't run on pi3 at all, due to GLES version.

i managed to find the driver that mupen64 uses on my phone, its "GLES2N64"

mupen64plus-gles2n64 is available on retropie, however it's not very compatible and there's an issue with pi4: https://github.com/RetroPie/RetroPie-Setup/issues/3118

as for the saturn emulation, i think i was running the experimental package one called "yabause"

yeah, as far as i know this is good for android, but the linux gles versions are lacking. yabasanshiro is a promising fork, but has issues right now, and no-one to lead development on the pi side.

So I just wiped InputAutoConfig.ini and started again.

When it's this:

; 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

the game works perfectly, but keyboard only - WASD and cursors and a few others.

When I add this:

; usb gamepad _START [usb gamepad ] plugged = True Start = button(6) A Button = button(1) B Button = button(2) X Axis = "hat(0 Left Right)" Y Axis = "hat(0 Up Down)" ; usb gamepad _END

the keyboard stops working and the Start, A and B buttons all map to the proper buttons on the arcade joystick, (and button 5 quits back to EmulationStation) but the stick itself does absolutely nothing.

Those X and Y axis lines are taken from some semi-gibberish here:

https://retropie.org.uk/docs/Nintendo-64/

where it says *"Note for configuring Arcade Joystick or non analogue controller to use N64 correctly.
Changing the below inside /opt/retropie/configs/n64/InputAutoCfg.ini

From X Axis = "hat(0 Left, 0 Right)" Y Axis = "hat(0 Up, 0 Down)"

To X Axis = "hat(0 Left Right)" Y Axis = "hat(0 Up Down)""*

But none of those lines, with or without quote marks, make the joystick do anything at all.

If I change it to:

; usb gamepad _START [usb gamepad ] plugged = True Start = button(6) A Button = button(1) B Button = button(2) DPad D = hat(0 Down) DPad U = hat(0 Up) DPad L = hat(0 Left) DPad R = hat(0 Right) ; usb gamepad _END

nothing changes. The stick still does nothing, whether I put quotes round the hat commands or not.

What in blazes do I need to do to make the dumb emulator recognise the stick?

Did some more digging on this problem, I didn't realise when lr-mupen64plus-next is built the GLideN64.custom.ini file is used. Learn something new everyday. Anyway I tested it by building from source, editing the tmp folder of the build to make your change, then rebuilt from source. Voila the game's camera is totally fixed in the lr-mupen64plus-next core.

I've sent an issue under github and made a pull request for my edit. So hopefully they'll update it.

@stattmone If you're using the standalone emulator, then the configuration you've done have no effect. Look in the /opt/retropie/configs/n64/mupen64plus.cfg file and re-arrange the controllers there (look for [Input-SDL-Control1], [Input-SDL-Control2], etc.). The same file is available at \\retropie\configs\n64, if you're using file shares to access your Pi.

@hackedmacbook111 said in Mupen64plus-gliden64 from source is broken:

I used mupen64plus on pi3B+ and it freezes with glide 64 games have more lag than with impending 64 plus
I recently updated 4.5 to 4.6

Start a new topic, this issue has been solved and isn't the same as yours.

@Jste84 said in N64 (mupen64plus-GLideN64) performance fix:

My default emulator is lr-mupen64plus-next...

whoops, you're right. will update post

Should I change this? Or run the fix?

i think both. -next does not have a setting to reduce slowdown, so it will always be present.

kodi addon is not maintained, no activity on github and no answer on github issue.
so i want to find solution manually :)

@quicksilver did you ever figure out your issues you had loading games with lr-parallel-n64? Oddly that emulator works quite on my Mac for some stuff (seems to be the of the only ways to use rice on retroarch too), but nearly everything I've tried to boot crashes except Mario 64 & Goldeneye.

The audio crackling is caused by the audio resample method in the mupen64plus.cfg. This issue was fixed a while ago but looks like it is broken in latest Dev builds of retropie. There is a pull request that should fix this issue it just hasn't been merged yet.

@sepp86 said in [Mupen64Plus] Rice Video plugin is missing:

Makefile:259: ***Mupen64Plus API header files not found! Use makefile parameter APIDIR to force a location

So you need to find API header directory and run:

makefile install LIBDIR=/opt/retropie/emulators/mupen64plus/lib/mupen64plus SHAREDIR=/opt/retropie/emulators/mupen64plus/share/mupen64plus APIDIR=<API header directory>

if your directories are diffierernt change them (LIBDIR and SHAREDIR), but i dont know where API header directory is, so try to find it.
horever i dont know that it will even work.

personally, if i was doing this i would make a fork in github with my changes, and then edit the retropie build script to point at it, then compile it through retropie - update via source.

eg https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/emulators/mupen64plus.sh#L32

if i made a change to the master branch of my fork of mupen64plus-core, i would this line to
'dankcushions core'

note that when you edit retropie scripts the script updater will complain when you come to update it.

@Flextrade said in N64 Rom specific Controls:

@mitu ok thank you.
but is there any way to create a something similar for the mupen64-plus?

Not that I'm aware of.

I've seen that there's a Python front-end for Mupen64 that has a GUI where you can select different cheats, but I'm guessing it just loads them before starting the emulator the same as the CLI you posted.

https://github.com/mupen64plus/mupen64plus-ui-python