@BuZz Thank you sir. That helps a lot.

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.

@mitu This was helpful! But I also had to force 1080p by setting hdmi_group and hdmi_mode:

hdmi_group=2
hdmi_mode=82

For more video mode options see:
https://elinux.org/RPiconfig#Video_mode_options

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.

I've found a work around, if you are using a ps4 controller you could use the middle touch pad to "wake" raspberry pie. As i said, it is a work around but it is working :)

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

I was able to get jzintv installed and running. The only problem I have now is I can't get it to display with a 4:3 ratio. I have used the below configuration file on my Raspberry Pi 3 and it works great. If I launch Emulation Station from the Buster Desktop, then jzintv will display the correct 4:3 ratio in a window. However if I exit out of Buster and run Emulationstation by itself, jzintv will automatically stretch to fill the screen. I've tried making display adjustments in Retroarch, but it doesn't seem to affect it. Other emulators like Stella, Nestopia, and a few others, maintain the 4:3 ratio automatically. Just wondering if anyone else has seen this problem with jzintv or some other emulators?

jzintv = "/opt/retropie/emulators/jzintv/bin/jzintv -p /home/pi/RetroPie/BIOS --gfx-palette=/home/pi/RetroPie/roms/intellivision/composite_colors.gfx -z1430x1070,8 -b10 -q -v1 -s0 --kbdhackfile=/home/pi/RetroPie/roms/intellivision/hackfile.cfg %ROM%"
default = "jzintv"

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.

@Uskompuf
Anyone's know if it can run Badlands and the others that didnt work before ? :)

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

@mitu Thank You! I realize it is not supported but there is usually a way!

this actually has been solved, follow the steps exactly here, and you'll fix that SDL2 error. i had the same thing and this fixed it.
https://retropie.org.uk/forum/topic/23984/solved-rpi4-sdl2-problem-during-installation-meanwhile-its-available-via-apt-get

@UDb23 Yes it was a good deal. I bought it locally from a flea market/store. Wii consoles are pretty common these days and you should be able to find a wii with a reasonable price in your local area.

For me it was quite easy since Denmark want's to make a positive change in climate and more reuseable items gets sold. Now we have flea stores that we always can visit just like a normal store. :-)

@Xystus777 Normally this is done by runcommand when launching a game, by running

setterm --blank poke

Are you not using runcommand to start your game ?