@mitu thanks I will try that

@dankcushions nevermind... since i ran into a few other problems with lightdm and pulse which are way beyond my know how, i dropped that build. thanks anyway

@mitu I sincerely apologize I assumed my message was clear. The buttons were mapped but they were mapped to the joystick and the D-pad, etc. However, I was able to figure it out this morning. I keep trying to change the controller config under Quick Menu and then Controls but it is actually under Settings and then Input. I sincerely apologize for the confusion. I really appreciate your time.

@krystalis I thought it might be more than just that diagram. I did have to do a minor edit to the config file for the controller, but I can't remember what it was. I hope you get it sorted.

@retrochip said in Mupen64Plus problems (audio + video):

The only option I see so far is to use the 'Mupen64Plus SDL Audio Plugin' v2.5.9 plugin, but how do I do it? The script mupen64plus.sh should set it (am I wrong?), but if use the old one, it does not change anything and the 'Mupen64Plus SDL Audio Plugin' v2.5.9 plugin is still used.

it should. after a launch, what is the contents of /dev/shm/runcommand.info please?

@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.

dankcushions created this issue in RetroPie/RetroPie-Setup open N64: mupen64plus-gles2n64 not filling screen correctly #3118

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?

Does anyone have some suggestions?

@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 :)