Given that Linux is not running on these new systems, the answer is no.
You can use something like OpenEMU, it's a nice retrogaming frontend + emulators package for macOS systems. Not sure if it's been ported to the new M1 platform or if it runs through the new Rosetta2 emulation layer.

@mitu Thanks for the pointer on the docs. I've gone through a lot of research and reorganizing since my last post, but it now appears to be working! There were two issues at play: bad rom directory structure and bad install of vldp2.

For reference to the curious, here's the problem I was having with vldp2. Every time the emulator started, it would give this daphne error saying ERROR: could not open the VLDP2 dynamic library (file not found maybe?):
daphne-error.png

For the sake of testing, I ran the following from the command line to see the console output:

/opt/retropie/emulators/daphne/daphne.sh $HOME/RetroPie/roms/daphne/lair.daphne

And at the end of the output, I saw this:

libvldp2.so: cannot open shared object file: No such file or directory Could not load VLDP dynamic library!!! Shutting down sound system... Shutting down video display...

Well the install script for daphne is supposed to install vldp2 for you, but in my case, it wasn't doing that.

You can manually install the Linux x64 version of it by running the following in a temporary directory:

git clone https://github.com/DavidGriffith/daphne.git cd daphne/src/vldp2 ./configure --disable-accel-detect make -f Makefile.linux_x64 sudo cp libvldp2.so /lib

My theory is that the script was compiling vldp2, but then failing to copy it to the /lib directory that it's supposed to get installed to (that last line in the command above).

I tried fiddling with the script a little to get it to work automatically, but gave up because it was hard to debug. If I can gather the motivation, I'll try to fix it properly and then send a PR to include the changes in RetroPie-Setup.

I'm having a similar issue with Sega CD / lr-genesis-plus-gx on the pi4. My files are .chd format. Worked in my previous build, verified the BIOS against the official documentation... nothing.

@lekzerum Any chance you could throw that file in a google drive link for me to try?

I ended up using @cyperghost 's script from [https://retropie.org.uk/forum/topic/17415/multi-switch-shutdown-script?_=1609290226722](link url)

and now have things working.

@thiagofm thanks - I think this should be included in RetroPie!!

@mitu It works, im in!

Thank you so much!

@mitu said in How to donwngrade PPSSPP to v1.5.4 (solved):

@stumcbill said in How to donwngrade PPSSPP to v1.5.4 (solved):

Ah ok, is there anyway I can reinstall the version that comes with 4.7 to see if it makes a difference?

Since PPSSPP isn't installed on the 4.7 image by default, even if you download the 4.7 image, installing from binary will still get you the current/last version. So, no - you can't reinstall the old version from RetroPie-Setup.

Ah, I never realised that. Sounds like I’m out of luck then.

Thanks

Please don't re-post the same topic multiple times.

@dankcushions I appreciate the info and was thinking I need to do a fresh install. I was hoping for a workaround without having to start from scratch but will try the fresh install.

@traptedmind - Thank you for posting this! The googledrive link appears to require access. Can you post the contents of the .cfg file to the thread?

Thank you!

@onemorning said in accidentally wiped dc memory card and redream is gone:

@mitu really?
https://retropie.org.uk/forum/topic/25950/redream-boot-issues/7

would it have killed you to say the same thing that youve said to this guy?

Not supporting 3rd party images isn't just about software licencing issues - although that's reason enough.

We can't know if they've changed anything from the standard image and any suggestions may unwittingly break things we don't know about.

Imagine someone had suggested a fix to your problem that overwrote a custom change in the 3rd party image and it had stopped the whole system working.

@revolutionflat said in 8bitdo SF30/SN30 Pro controller bluetooth pairing trouble after updating RetroPi on Pi4:

This isn't so much of a please help post, but a "There's a problem, here's how I fixed got around it" post.

I purchased 2x bluetooth SF30 Pro controllers and the new RetroFlag NES case for the Pi 4. When the controllers arrived, I spent hours trying to get them to pair but one outright refused to connect after pairing, and the other wouldn't pair in a mode that allowed all the buttons to be used (triggers didn't work).

After 3 re-imaging and installations, I realized THEY WORK ON THE 4.6 IMAGE just fine, connects immediately and behaves as you'd dream. If you update, that's when the problems occur. I was able to install extra themes/emulator packages/retroflag scripts without disturbing the connections. Hope this helps people going through this!

Edit: On the clean 4.6 image, I had the controllers in [Start+B] mode, I'd recommend re-flashing the firmware if you've been troubleshooting.

Received my SF30 Pro for my RetroPie 4.7.1 and have been having bluetooth connectivity issues. Did what RevolutionFlat did by reverting back to flashing my SD card with ver 4.6 and SF30 Pro finally connected... HALLELUJAH!!! Thanks for the version revert advice!!!

Only the P1 controller has access to the Hotkey, so you can do any configurations for a game in the RGUI with a controller that has a hotkey defined (the one you chose when you configured the controller in EmulationStation). Make sure that controller has also an X button configured, otherwise you can't open the RGUI with the Hotkey + X combination.

To enable Multitap - and get more than 2 players working - you can do so from the Options menu, where you need to toggle on the Show other input settings, close the RGUI, then open it again and in the same Options menu, can set _Multitap_1 to ON and Pad 2 to Pad 4 to dualshock.
Since not all games support Multitap and enabling it globally would probably break input for it, make sure that you use the 'Create Game Options file' menu at the top of the Option list, then toggle off the Multitap option(s).

@gizmobjb said in Atari VCS with RtroePie installed in Ubuntu getting failed to find mixer elements error:

Besides my custom es_system file not working, when I add it the only system shown is one is sg-1000. I can live with that issue as the custom file is set up to order the systems by maker and old to new.

If the file is incorrect, EmulationStation might not load it. There's a log file in $HOME/.emulationstation/es_log.txt that might help diagnose this.

But every time I exit emulationstation I get a blank purple screen and have to logout of ubuntu and back in, not the end if the world though.

That might be the (Gnome) terminal from where EmulationStation is started. Have you tried typing exit or pressing Ctrl+C Ctrl+D at that point ?

@forthias said in lr-pcsx-rearmed not detecting bios:

A head ache, but now I know what's wrong and feel like I wasted your time lmao. Thanks again, I think I know what's going on, now. Maybe that the corrupt images are making the emulator default to the hle bios

It's not a waste of time if we find out what's the cause.
Regarding the SSD issue, it might not be the cable, but the USB/SSD controller. There is an extensive topic in the Raspberry Pi forums about it, including workarounds and ways to diagnose it.

@nateo44 While the original poster here said it didn't work for them, the only way I was able to solve this issue is to update xpad from source individually, even after doing a full update of the entire system the usual way. From inside of EmulationStation, choose RetroPie, then: RetroPie Setup, Manage Packages, Manage Driver Packages, xpad, then Update (from source). I'd restart the entire system afterward. Once that's done, go back into EmulationStation, hit Start, choose Configure Input, and go through all the mapping again for each side of your X-Arcade Tankstick. Note that this is with the unit in Mode 4 on a newer Tri-Mode Tankstick unit. Worked for me; YMMV.

No idea if it's unique to a Pi 4, or what the deal is, but it was the only method I could find for getting LT and RT buttons to work properly.