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"
Sorry for major bump, but just wanted to say that despite several months between posts, I finally managed to update my install completely to version 4.6.9 and I would say yes it does seem to have improved a bit. I reduced my N64 stuff and completely removed Dreamcast though, as lets be honest you aren't going to get much joy on that front on a Pi3B+. But the couple of dozen N64 games I do have seem to run a lot better than they did on previous installs with only a small margin of tweaking and my usual slight GPU overclock, and I notice the standalone GlideN64 is definitely improved. Very pleased, and worth it for pi3B+ diehards imho.
@v-roshpi Contact the seller ? You can download RetroPie from our site, and try and get that to work but you will need to contact them for configuration unless you know what it's using to interface etc
the full core information displayed should be "1.7.6 Reicast r0.19XXXXXXXX", so i'm 100% sure that it said reicast and not retroarch.
First is the RetroArch version, then it's the name of the core (reicast) and its version. RetroPie also includes the same version of RetroArch, but the core name has been renamed upstream since the Lakka release you are using, in RetroPie it's lr-flycast.
yeah i had a dreamcast backup game image with the dreamcast bios on a usb stick, just like the guide told me to, then i put it in the pi, but reicast didn't show up. then i look at the guide and it says to install the emulator you want using the package manager and whatnot. so i guess that's what happened.
I wasn't going to bring that up in this thread but since we went that direction...
I was actually planning my cabinet to have player one as one set of joystick/buttons off of Pi USB 1, player two as the second set off Pi USB 2, the dedicated buttons on the third controller on Pi USB 3, and then a hub stuck into Pi USB 4 which would tie (via extension cables) to two external USB ports on the cabinet, to which I could plug in a keyboard, or two SNES joypads or other types of joypads or joysticks. I was going to cross that "hot swappable/which is active/how do I program that" bridge when I came to it.
It sounds like, from above, it actually matters which of the 4 USB ports on the Pi I plug into? I figured they were all just addressed the same. Is that true? If so, I assume I plug a hub into USB 4 and those become 4, 5, 6, 7...?
To clarify what I'm actually doing...
I'm making a portable console like those ones you can buy online, which simply has a power cord and an HDMI cable and can be plugged into a TV anywhere. But my intent is to have the central portion of the panel have all the "hotkey default" dedicated buttons - save, load, exit, reset, etc. - and then have each of the two joy/button controller areas be small pull-out boxes with long cords, so the "base" can sit on the coffee table while the two controllers get passed between the kids sitting on the sectional sofa. I have plans in my head, and I'm using USB extension cables as the "pull out" cables (connecting the zero-delay boards to the Pi in the base).
But what this means is that I can't (at least easily) use the pin plugs on the zero-delay boards in each "remote controller" for the buttons which I want on the base. Each zero-delay board will be in the pull-out box, and the "hotkey" dedicated buttons will be several feet away in the base on the coffee table. The only way to have those "hotkey" buttons plugged into the boards which operate the joysticks and action buttons would be to do some wire dissecting and soldering, and I don't want to bother with that.
So my original question above was, can I use a third zero-delay board in the "base" which would only have those load-save-exit-reset-RGUI dedicated buttons, but NO actual controls tied to it? I suppose another way of looking at it is, can you "null" out all the hotkeys on player one and player two, and then null out all the directional/joystick/X/Y/A/B stuff on player 3 and still assign the hotkey commands?
I'm working up a sketch of what I'm imagining for more clarity and will post when done, if this isn't clear... or too long that you didn't read it... :)
Power buttons are a bit more difficult, as the Pi needs to be shutdown cleanly, you can't just rip the power away and expect it to be fine next time (sometimes it is, but not always). You could create a custom shutdown script or use something like the PowerBlock or actually, to combine the function you could use the ControlBlock https://blog.petrockblock.com/controlblock/
Here is another fact, I started a new image from scratch and moved exactly the same amount of roms, the system is duplicated manually in a fresh install and it takes 2.84 seconds more to load ES on the new PI3B+ running Retropie 4.4 than the PI 3B running 3.9, its akward, but true. I have an intro video wich overlays the ES loading screen and now I have to make it that time longer because Retropie 4.4. with a PI3B+ takes more time loading.