@Rascas the issue is max_framebuffers=2 on retropie. It should be max_framebuffers=1 when using a single display. This resolved my issue.
Tried all different cables, monitor inputs, monitor outputs, rebuilding libcec. only solution was max_framebuffers=1.
@mitu Glad to know I'm not the only one having the issue with Arcade's Greatest Hits - The Atari Collection 1. The fact that both of these games play properly on ePSXe, using the same BIOS (SCPH1001.bin) and ROM files, leads me to believe that it's an issue with lr-pcsx-rearmed. I suppose, worst case scenario, I could try The Atari Collection 1 on SNES and Hot Wheels Turbo Racing on N64 if myself or anyone else can't figure out the issue on PSX.
Games will have bugs or not run correctly. You might not have noticed it, but I did. It depends on the game.
I agree with that between 0.36 and 0.78 it nearly doubled and between lr-mame2000 and lr-mame2003 I would think a shoe in for the latter and is considered the gold standard in certain aspects except maybe vector where AdvMAME outshines them all. I do agree to that FBA seems to run Neo-Geo, Capcom, Konami games better. They just seem to run smoother for certain.
I do also use multiple emulators too depending on the game. Mainly lr-mame2003 roughly 300 or so games with aforementioned options of shader and analog d-pad support. AdvMAME for vector, FBA for Neo-Geo, etc.
The original author of mame4all-pi (squid) had a majority of the games running at 100% without frame skip. It's been a hobby of mine since the late 90's. I do faithfully download the split updates every few months merge it and join the torrent. That includes the CHD's & extras, etc. I think it's close to 400GB now. It's where I spend most of my time when it comes to emulation.
That's what I was pointing out is the binaries (ROMs) are mostly 100% identical between the two version which are only 3 years apart. I don't believe the driver/board support emulation improved that much between those versions but they went crazy with additions.
You would have to be more specific on what exact games you find buggy in 0.37b5 that work differently in 0.78? My main point is that mame4all-pi (not lr-mame2000) is still very relevant if not a choice not just for the familiarity and support for being so widely ported but also the input configuration is still superior out of the box it works. Meaning there's certain configuration scenarios lr-mame2003 can't do...yet or at least not easily as I believe you will loose hotkey functionality if you "nul" all the Retroarch inputs to rely on lr-mame2003 inputs alone to correct the issue. :)
@zoop did you reboot the raspberry? when exactly do you get that screen? Can you detail the text or message you receive? Any capture or pic? Which Raspberry do you have? Which sd card? Any other specs? Whta do you mean with too aggressive?
Pi Model or other hardware: PI 3 Model B
Power Supply used: 5V/2.5A Power supply charger for Raspberry 3B
RetroPie Version Used (3.6, 3.8.1, 4.01 etc.. - do not write latest): 4.1
Built From: Pre made SD Image on RetroPie website
The overclock settings I am using without issues are (credit YouTube vid where I found them):
When I bumped the arm_freq up to 1450 I received the aforementioned error. Resolving the issue on my end was as simple as modifying my config.txt to scale back the arm_freq to 1400 again and powering the system off then back on again. To my great relief everything just worked once the setting had been changed back to a stable configuration.
I do not 100% remember how the screen looked with the error. It may have just been a single line reading segmentation fault. All I remember for sure is there was a 'segmentation fault error' on the screen and I figured it had to be my OC settings. I just had to hope I had not corrupted my image or something..
Apologies for the delayed response, I hope you find what you're looking for and are able to resolve the issue. Best luck!