@mitu : Thank you very much. After installing Joy2key, the navigation works again with the gamepad. Thanks for the good advice.

@breadpie said in N64 on a Pi 3B+:

I have my Pi 4 (which is great), but I also have an older Pi 3B+ where the microSD became corrupted and I finally got around to putting in a fresh one. I grabbed the download from the retropie website, put it on a new card, etc. But, I noticed two things: 1) that mupen64plus (not lr-mupen64plus, and not lr-mupen64plus-next which wasn't installed by default) is the default for N64; and 2) that updates were available for mupen64plus. The stock build seems to have mupen64plus current as of Oct 2020, if I recall correctly. Normally I would update a package reflexively, but I also remember concerns about regressions with an N64 update from around last year. So, my questions, specifically for a Pi 3B+:

Should mupen64plus stay as default?

yes. standalone is fastest and most compatible. lr-mupen64plus (NOT -next) or mupen64plus-gles2n64 or even lr-mupen64plus-parallel may be faster in some scenarios, but the best balance is mupen64plus-auto (which i believe is the default for pi3), which selects the appropriate video plugin for mupen64plus-standalone, per game.

Is there any potential downside to installing the latest updates (since the most recent stock install) to these emulators on a 3B+?

not that i'm aware of, but as always, always back up before any updates. do note that n64 emulation is probably only going to get slower with updates, as emulation gets more accurate, compatible, etc.

@retrotarta I'm replying myself to say that lr-snes9x is apparently working reasonably well.

This has been resolved and the answer is on this thread that I referenced earlier.

SOLUTION:

I brought this up in another thread, but that covers other issues, so for details that aren't here, you can check there.

I solved this on the dhcp server (dnsmasq). Oddly enough, even though I was specifying to use 172.16.7.17, somehow it was being read as 172.16.7.174. I have no idea why, but that was in my reserved range of IP addresses to not give out, so the dhcp server was having issues with that and not giving it to the Pi.

I changed and ended up using 172.16.7.11 instead of .17. After I changed to that, allowing time for propagation, it worked out.

It is puzzling, since the dhcpcd logs on the Pi say they're being offered 172.16.7.17, but the server says it's .174 instead of .17. I have not tried to change back - I don't want to deal with that again. (I'm wondering if something was glitchy when the dhcp server wrote the config file to the drive.)

Looks similar to this error. Seems like the recent release of Debian Bullseye gets apt-get in trouble.

@mitu
Yes it turns out that the custom Retropie xpad driver was the culprit. I was pointed to this issue thread here, https://github.com/RetroPie/RetroPie-Setup/issues/3379

I tried uninstalling and once again my XBox One controller worked fine with the program im working on (Chiaki)!

I'm still waiting to hear if that solves my user's similar issue as well.

Thanks!

@mitu wow that was so easy thanks again everything is good now

Oh.

Sorry.

I don't think I read your first post correctly.

Here's a better video, about 13 minutes in length if you have the time.

He covers everything quite well.

I found an easy way to do this.

I just needed something like a Turtle Beach Ear Force DSS 7.1 Dolby Surround Sound Processor.

One can find that on Ebay currently for $10.

https://www.ebay.com/itm/272275549904

@mitu

Thank you so much!

End result:

/opt/retropie/configs/all/autostart.sh

sudo bluetoothctl remove 40:1B:5F:BA:D5:A0 sudo timeout 6 bluetoothctl scan on sudo bluetoothctl connect 40:1B:5F:BA:D5:A0 sudo bluetoothctl trust 40:1B:5F:BA:D5:A0 emulationstation #auto

Now I can easily pair my controller back to the Pi on system startup without even having to plug it in using USB and navigating through all of the menu options.

So happy! :)

@lister-of-smeg thank you very much for your hints, i never thought if trying an optional port, neither i was aware of a version called "Super Big Brother" for the PC-Engine.
Much appriciated!

@dmg9626

OMG! IT WORKED 🤯

For the record this fixed my Retro-bit "SEGA Saturn® Bluetooth® Wireless Control Pad - Slate Grey" pairing issues with my rpi 4.

TYVM dmg9626 u the man 🥳

@barbudreadmon said in Analog stick bind recently stopped working in MAME:

@slimbrick there were some changes with that analog-to-digital feature last month, if you recently updated retroarch maybe you'll want to read https://www.libretro.com/index.php/retroarch-1-9-6-released/

Thanks! This will certainly help and the timing correlates very well with when I started having problems.

Thanks everyone.
It was due to bad dumps. I had bin files and a .zip romset solved the problem.
The control issue came from the 8bitdo controller. I connected it like a switch pro controller and everything is fine again.
I went further and replaced some of the original roms with dreamcast ports in order to use Redream. Really good perfs now !

@adamantiumpimp said in Stuck on a splashscreen/command prompt!:

@exarkuniv Apologies for my ignorance. Is it the PlayBox part of it that is the rebuild? Sorry I'm just now getting into all of this and am unfamiliar with the lingo.

It is impractical to provide support for a system that neither you nor we know how is configured. *Pre-built, aka third-party (anyone[3] who's not you[2] or the RetroPie project[1]) systems are not supported. The only supported configurations are the official SD images available on the download page or installed on top of an existing OS using the setup script.

We will gladly help you through the process if you'd like to start over with the default image and build a system yourself. Or, you can contact the author of your custom build and ask them to provide support for the system that they have configured.

Hi again.

The above post has solved my problem. I was able to effortlessly pair both controllers by following those instructions. For anyone who is stuck and sees this thread, I believe it was this command that solved the problem: sudo apt install bluez=5.50-1.2~deb10u1+rpt2. After updating the packages and checking the bluetooth status, I still got the Failed error messages, but once I inputted this command they disappeared. Of course, try everything just to be safe.

Thanks for your help!

@mitu Thanks for the reply! I’m not at my Pi at the moment but when I get situated, I’ll give that a shot and report back!