@roslof I was using gpu_freq=500 before I updated. Never an issue. After updating, I could no longer use this setting in config.txt

There are other setting that effect GPU, so there maybe others effected too.

@mitu Gotcha. Thanks so much.

@retropieuser555 Hopefully you see this, but I was able to fix it by going into /home/pi/.config/AM2R/config.ini and changing:

[Screen] Fullscreen="1.000000"

to

Fullscreen="0.000000"`

This usuall happens on the Pi4 when you're using a 4k resolution, for some reason the setup dialogs are not properly displayed.
Edit the config.txt file on your SD card (you can edit it from a PC) and add 2 lines at the end:

hdmi_max_pixel_freq:0=200000000 hdmi_max_pixel_freq:1=200000000

Try booting again your RetroPie system and see if you can open the setup script or raspi-config.

@ibonihs hello! I take it you haven't relied on Retropie Setup to get latest Amiberry binary. This is not supported way at this time given there are still some outstanding issues with Amiberry 4.x especially on pi3.
=> Please rely on Retropie Setup to get a supported version (3.3).

Amiberry's core is based off WinUAE meaning the emulation (accuracy + performance) is great. To the point that I never consider using any other "core" on pi3/pi4. As I recall on pi3 some copperlist-intensive games could run a bit slow (eg. Jim Power comes to mind). However on a pi4 I do have fullspeed perfect emulation on the ~500 games I've been tested it with. I have no issue with Flashback nor with any other games mentioned.

The "lha packages" (also known as WHD packages) are the definite way to go for the Amiga emulation. It really simplifies the process and keeps everything tidy. The only requirement indeed is to ensure to get the latest version for such packages as they're being updated on a regular basis. Older packages might run flawless but no guarantee though not recommended.

Your screen issue is due to 4.x as it doesn't properly get some values from a specific conf file.
=> Reverting to 3.3 will fix that.

@mitu I feel so dumb I am so sorry to bother you. It worked turns out it was wring problem like you said.

Thank you for everything though

I'm a bit confused. If you're using the Pi4 image provided on retropie.org.uk/download, there's no additional installation to be done - RetroPie is already installed and the system should boot to EmulationStation.

How are you installing RetroPie ? Is a Raspberry Pi OS image from raspberrypi.org working on the device ?

@kanz1a It's encouraging to hear that it worked on an older image, which means it is most likely a fixable driver or software bug, rather than a hardware oversight.

I have investigated just about everything related to usb, and controller drivers that I could find, and nothing seems to fix the problem except for diverting all signals away from the 3.5mm jack. I hope there is some solution, and if not I hope a hotfix/patch is possible in the future.

@punx45 , I'm about to go almost the same way myself, wiring up buttons from my genuine arcade machine. I'm planning to use the grounding instead of the plus feed (Raspberry's GPIO's should trigger fine on three state i.e. either open circuit going high to feed voltage OR going low to GND).

However, my thought was also a prevention from involentary multi triggering but not by H/W support, we do have plenty of computer power at hand; have a look at this article Physical computing with Raspberry Pi. Some simple sleep timers should do it.

@mitu They don't work at all. :(

I ran through the install instructions posted on the main page twice to be sure. Fresh RetroPie install on a 32GB card, updated everything RetroPie then right to the shutdown scripts. No go. So I did it again with a fresh install with no updates. Still no go. I also used Putty so I could copy and paste the commands with no chance of incorrectly typing them in.

The former dev said he hasn't touched them in over 16 months.

EDIT for added info

@clyde thanks clyde!
Gosh, the Pi4 is a great piece of hardware, no doubt!
But it is PITA for anyone trying to get the beast connected to a CRT compared to the Pi1 to 3 :/

@domb84 Hey dude what changes do I need to make to use this script for the pi 3 b +?

@redmarsbluemoon Cheers dude will keep trying thanks and I know the feeling of not having enough time...

@alegasalv Is the gpu_mem actually using the 512mb though? I found that enabling the 'hdmi_enable_4kp60' overrides the setting, as running 'free' in the terminal was showing less than 512 being used. It's only meant to boost the stock gpu memory by 50mb's...or so I've read.

I have mine set at:

force_turbo=1
over_voltage=8
arm_freq=2147
gpu_freq=750
gpu_mem=512

Needed to force_turbo in order to go above gpu_freq=550 though, tested by running 'vcgencmd measure_clock core' to confirm. Also, 'vcgencmd measure_clock arm' for the cpu.

edit: Forgot to mention...if raising the gpu_mem, then using the raspi-config gui to modify anything, it will automatically hash out the hdmi_enable_4kp60 on you...or at least it does for me. I guess it's anything over a certain value.

edit2: Sorry...also forgot to mention that in order to use the gpu_mem=512, you need to enable cma=512 as well. The kernel crashes on me otherwise.

dtoverlay=vc4-fkms-v3d,cma=512

@mitu I updated the setup script and Wolf4sdl, and all is good. I can once again hear enemies shout "mein leben". Thanks again for the help!