I'm in the process of building a new dual monitor arcade cab and found his new revisions a lot simpler to get setup with both PNG and MP4 files.. .

@mitu Seems to be random whenever I write a new image. It has worked the second time I wrote the image. The microsd card is a few months old, though.

@BuZz Thanks, that was exactly what I meant. I have been sitting on a Pi4 since December and I thought I would put it to work now.

OK many thanks for this!

Quick update and some interesting details:

Following

, the controller is immediately recognized, though as a "Generic Xbox Pad". It works, but whenever I shutdown or reboot, I need to do this all over again. But what is strange is that I shouldn't need to be doing this at all: for one thing I never had to go through this workaround with my Pi 3, and second because the Xpad driver already has the device ID configured correctly and recognized as "Hyperkin Duke Xbox One Controller", but it seems that it's refusing to recognize it for me.

So why is this happening?

im looking forward to seeing how mame current is running on the pi 4. I only usually play 80s and 90s that would be an ideal setup for the living room barcade has a mini pc in it at the moment can see me changing that anytime soon. If the mame team do some dynarecs for arm there could be a fair few systems on the go on the pi.

@quicksilver The stable build works fine but it has the menu bug. It's definitely something the dev changed.

@dankcushions it's a fresh setup so ssh is off. I'll look later to see if I can enable it.
Yea, soldered to the board. Maybe I damaged a component too.
UPDATE: I was cleaning the solder joints of the reset pins today. I also noticed I was testing from the 2nd hdmi port so that wasn't giving me a proper display. Maybe the rescue image did do its job. Seems to be working now on 1st hdmi port.

Thanks @mitu. Good news. I looked around but I couldn't find a log file but while I was looking I found a gamelist file and a videos folder in my Roms/Arcade folder. I deleted them and regenerated the gameslist in Skyscraper. The Arcade section now works perfectly.

Thanks again

Pi4 support is ongoing and no, there's no release date. If you want to try it out, use the Manual Install method.

Ok, half a day later, I realize one (perhaps small) problem concerning the Pi4 project. As I am going to build two Arcade Machines together with a friend of mine, I had to setup RetroPie twice. One on a Pi3b+ and one on my Pi4. Testing with the old "Hyper Sports" on mame2003, I realize a perfect behavior on the 3b+ but a small delay on the Pi4. So pushing the button and taking effect differences a little bit (made me miss the skeets on skeet-shooting ;-) ). Do you have any idea why this is and - much more important for me - how to solve this problem?

Best regards,

Rufus

@mitu
Thanks ! :)

@quaker75 said in RetroPie on Raspian Lite missing 151 UAE4ARM:

Problem is all Software which i have is in .adf format. and thats not supportet from amiberry :(

Amiberry does support adf.

@BuZz
I write the solution for my case. Maybe it could help someone

Pi4 model b
access point: TP-LINK RE450

Retropie, any version for some strange reason does not connect to the access point.

SOLUTION: I had to install an OPEN-WRT custom firmware on the access point.

Once rebooted and configured, everything works.

The strange thing, that the first time, with the firmware stock was connected perfectly, then you can not.

Ok that's good to know (how messy they usually are).
I'll follow your advice then and will start my own project from scratch.

As this was an inappropriate question please feel free to remove it!

Cheers

I don't think there's a RetroArch's option to fix what it looks like an overclocking issue - your overclock may not be stable.
Try removing your overclock and try one of the other N64 emulators - mupen64plus, the standalone N64 emulator, or lr-mupen64plus-nx , the newer version of the libretro N64 emulator core.

@Darksavior thanks.

@polishedball https://github.com/RetroPie/RetroPie-Setup/wiki/Runcommand#adding-custom-launching-images. This shows how to get launching images setup for each system.

For Naomi and atomiswave you'll need to use lr-flycast and have the right bios. See here: https://github.com/retropie/retropie-setup/wiki/Dreamcast.

Also wanted to say it's great you decided to build your own image, you'll learn a lot more this way.

@mitu Thank you- now my afternoon has a purpose!