@steeluth said in Retropie ES config 3B+:

Following the guide I first installed the Bookworm from here > Raspberry Pi OS with desktop and recommended software and then retropie on top using image files provided and all went well.

You basically re-wrote the RetroPie image on the sdcard, over the newer RaspiOS image that you installed initially - while you may have the latest RetroPie version, you're still using an older version of RaspiOS (based on Debian buster).

The RetroPie image is using by default the pi user to operate, if you're using a different username, the installed front-end and emulators will not work. I advise you to re-flash the RetroPie image from the download page for your Pi model and boot it up, then continue from there. The system should reboot on the 1st start and then it will start automatically with EmulationStation.

If you want to use a newer RaspiOS, then you can install the Lite version and manually install RetroPie as described in the docs.

Please add some info about your setup, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Mapping are usually created based on the controller/gamepad name, so even if the gamepad disconnects and then re-connects the configuration would still work. I'm not familiar with Arcade1Up inputs - are they using an USB encoder for both players or each player is a separate controller ?

@windg thank you, I will try that asap.

@RetroMalina said in Pi 3B+ Peak Performance.:

My question is, Can a Retropie 3B+ run N64 games stably

Not really. Some N64 titles don't run well (or at all), even on a Pi4.

@mitu Oh understood on that front. As I mentioned above, I made a back up IMG file before wiping the retropie and reinstalling. I am just trying to figure out how I can access the ROMs on there. Because I think they are still there - the IMG file is 250GB...I just couldnt use it to actually install retropie because when I tried, I was running into these issues. Thats why I went down the path of a fresh install and trying to reaccess the ROMs in the backup file.

@Cayaco Anything using electricity is not just on or off. The amount of electricity being used is called power (measured in Watts) and when a computer is doing more, it requires more Power. If your power supply cant deliver the power, a computer can be programed to recognize that not enough power is there and slow down, or you'll just get crashing and shutdowns.

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

They are sorted by type, then alphabetically.

So emulators, libretrocores, ports, supplementary.

Thanks very much for the detailed reply, it seems like the benefits will outweigh the pretty minimal cost.

@Beldar said in The State of Emulators on 3B+:

Will I still get the same nearly flawless experience with those emulators in their current state of development? I would rather not buy a Pi 4 if I don't need to spend the money.

I just updated mine first time in almost 2 years. Make sure to copy all ur splashscreen videos and stuff. I cant find the one I was using. I deleted my SD card and started fresh. However, you can just update the cores. You could try updating the kernel and stuff but I had a hard time because my kernel and stuff was too old it would freeze up. You might now have that problem.

" Will I still get the same nearly flawless experience with those emulators in their current state of development"
It will probably be the same if not better.

@sonicman2020 with respect, your understanding of the runahead settings, and the audio latency settings are very wrong. if you want to get this working properly, please start again from the retropie image, and don't change such settings: https://retropie.org.uk/docs/First-Installation/

Did you have any ports package installed ? If you don't, that might be the reason the system doesn't appear (with your game).
Try installing one of the smaller ports - like lzdoom - this will create the folder and the necessary configuration to show up in EmulationStation.

@mitu Many thanks! Just managed to post what I needed to!

David.

@Rascas Same problems, but the navigation was a bit slower

Unless you are using a current RetroFlag (NES, MD, SNES) case, go for the 4.

You can check using the jstest utility if the buttons are registering correctly in Linux, outside or RetroPie. Attach a keyboard and exit Emulationstation (F4), then run from the command line:

jstest /dev/input/js0

It will show you the gamepad buttons/joysticks and you can press them one by one to see if the input values change on the screen. You can exit the test by pressing Ctrl + C.

If there is no reaction when pressing a button, either the wiring is faulty or the controller.
You can also try connecting the encoder to a PC and test it there also.

@danield420 well the black screen could be a bad rom or possibly a missing bios file. Sure there are other factors for the balck screen i'm still learning myself. This RetroPie Github page has helped me so much https://github.com/RetroPie/RetroPie-Setup/wiki/Supported-Systems .

Or make another topic and i'm sure someone can help you solve the problem if you didn't already on your own.

And it looks like I corrected the issue. I copied the gamelist.xml for Atari 2600 from Emulationstation to the folder that holds the roms. That seems to have done the trick. Thank you guys again for the guidance and help.