@mitu thanks for your help. This helped me a lot. The frameskip issue is now gone, but I'm facing a brand new problem now :( https://retropie.org.uk/forum/topic/24606/rpi4-freezes-at-boot-after-update Thanks to everyone else helping me here! :)

@quicksilver Sir, you ARE amazing. Future people, here is the link Software Installation SSH the Yodeck player by using this guide here Run the below command and when the installation finishes, exit the command line of the player curl https://download.argon40.com/argon1.sh | bash Link: https://www.yodeck.com/docs/display/YO/Configure+Argon+1+case+with+Fan+and+Power+Button#ConfigureArgon1casewithFanandPowerButton-SoftwareInstallation

Something I can do? As @Thorr69 said, right now the PI4 model is not fully supported by RetroPie. If you flashed a Pi2/3 image, it won't work on the Pi4. You can manually install RetroPie on the PI4 following the Manual installation guide. Support for this new model is ongoing and if you're just starting with RetroPie (or Linux), then is best to wait until an official release that supports the Pi4 will be announced.

There might be a bug in RetroArch which picks the first resolutions offered by the display instead of the current resolution. If the first resolution is 4k@30fps, you'll see it as a slowdown. You can check the resolution picked by RetroArch by running with verbose logging enabled from the Runcommand launch menu and then looking into /dev/shm/runcommand.log (which you can upload to pastebin.com if you want us to take a look at it). You can forcibly disable the 4K resolutions by modifying config.txt on the boot partition and adding [hdmi:0] hdmi_max_pixel_freq=200000000 [hdmi:1] hdmi_max_pixel_freq=200000000 (Ref: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=255970&p=1561266)

Update: Updated the RetroPie-Setup script and all OS packages and restarted the Pi. This got the Bluetooth to connect (unreliably, it still fails to register about 1/4 of the button pushes I make). Frame rates are still very poor but I think that might just be the state of RetroPie on Pi 4 at the moment.

@RGCTech As I said, support for the Pi4 is ongoing and some bits might not work or function as they were on the previous PI models. Try leaving aside the resolution change, since it's not currently not added to runcommand on the PI4. Use the native display resolution - which you can set it manually to 1080p if it's not automatically detected by using raspi-config from the RetroPie menu.

So apparently I'm an idiot. Following the guide over at Reddit, I missed one thing. I had the mini-hdmi cable plugged into the second port and not to the port closest to the power supply. Looks like everything is working now.

@BuZz Read it. Know it. Was just looking for a workaround to use till it eventually is supported (for the most part, most has been working on retropie, I’m happy to report). I’ll try the other package that was suggested.

THX! It looks like there was a hidden sign (copy and paste failure)

@dalves you could also try lr-bluemsx for coleco.

For up 16bit era stuff I'm running a Pi 3B+ in an R2D2 that I think I will make another of when there is official support for Pi4. I also have a GPi case with a ZeroW for portability and such. I've got a few other 3B+ builds sitting around in Retroflag cases. I've got a 10L beer keg that I was thinking of turning into a portable emulation machine but I don't think it would get much use. For more intensive emulation I have and Odroid XU4 in that snazzy N64 style case with the screen on it. It's a great little board but I use my Pi setup a lot more. Not really relevant but I'm thinking of modding my Wii to be able to play GameCube games from an HDD.

I believe that is a Windows only device

@mitu said in Getting AdvanceMAME to run on FKMS builds: Do you care to elaborate on the Video appears a bit degraded part ? I confess I didn't use advmame before, so I don't have a past reference, I just test it out on the Pi4 - the 3.9 version - to see how it works. Sure mitu, Overall, it looks like anti-aliasing doesn't work with the SDL driver. Examples: Vector game lines are not anti-aliased System menu font appears jagged Video Rgb Effects, such as scan2horz do not blend nicely with the game screen. The setting display_antialias is set to yes, but there is no visual difference when it's disabled or enabled. One of the draws of using AdvanceMAME is for the clean high-res Vector images, so that's a bit of a miss. But having AdvanceMAME available for rendering raster games like Cotton 2 and Baku Baku is a must-have. There are also some issues going in and out of the settings menu (Tab). Sometimes, when returning to the game, the screen blanks. Also, gets very sluggish and occasionally hangs. Might not be related to the driver, but different from running this on a 3B+ without Buster.

Thanks for the help guys. I'm not using Retropie at the moment, I'm using Mupen64plus-next on Lakka. My old Pi3B+/Retropie setup wasn't overclocked so I didn't use N64 much. Mariokart 64 and Rouge Squadron are my go to games for trying to judge resolution. Rogue Squadron has been covered and Mariokart has slight graphical glitches in anything above 320x2xx which leads me to think that it ran in low res.

just for completeness mine was at : /opt/retropie/emulators/daphne/daphne.sh

FYI guys thanks for your help. Ive got RetroPie installed on my RPI4 now - not yet configured, but installed at least :)

@BuZz can you explain me how to fix it? Do you know when it will officially released?