You should try with SCPH101.BIN bios instead. It's the one from PSOne, so it's more modern and updated and generally should work better (at least that's the case with my games I've tested). Also, try disabling some features like Interlacing and Dithering.

@flyingtomahawk said in Overlays per rom folder?:

Thanks @Rion
So there is no way to avoid creating cfg files for each single game?

I think you can do it for NeoGeo because they have there own rom folder. Same way you setup a overlay for Nes, Snes and so on. But for Fba and Mame with different screen resolutionshot for many games and that's excluding the vertical games I don't think that's possible. But someone please correct me if I'm wrong.

What about using a USB stick, would that work for you? Check out the documentation, in the Getting Started section there is a whole page on Transferring Roms: https://retropie.org.uk/docs/Transferring-Roms/

EDIT: Sorry re-read your post, emulators, not roms.....never mind

@andrewpelt The new version of RetroPie-Setup is supposed to download a new version of go to a non-default location and us it to build the scraper. I did this to hopefully make it more stable. Go has a guarantee that new versions won't break any old code. It only adds new features and fixes bugs, but there wasn't a guarantee that code I depended on wouldn't take advantage of one of these newer features and break everything.

In Go 1.6 they added the ability to copy all the dependent libraries in to my repo so now it will always build. I can't explain why these issues are popping up.

@m1s3rys1gn4l Neo Geo games are considered arcade games in the scope of retropie. Arcade games come in ROMsets. They come in as parent or clone. A parent rom is a full rom dump of a particular version of an arcade game. A clone may be a different version of said game, but the file itself relies on some of the files on the parent, that is basically just the different files from the parent. So the hack may be a clone that is missing files from the full rom to run.

http://choccyhobnob.com/articles/demystifying-mame-roms/

@dankcushions ok, I'll try them. Thanks for input. Hopefully they can figure it out! Thanks again.

Note for anyone finding this thread -- the aforementioned link contains much more information regarding the troubleshooting and fix of this issue. Please reference that for more information.

Ah... That seems to have been the issue. You know, I actually checked each folder to be sure but I must have skipped over atari2600 or perhaps just didn't see it. It being 5am here and me not having slept yet may have contributed. To think, I sat here for about an hour and a half trying to figure out what went wrong before asking for help too! Regardless, I appreciate the fast reply and apologize for clogging the forum with such a silly problem.

@kmetz7547 inside emulationstation, when you press start in the menu there are sound settings. Try adjusting it in there.

@dankcushions

I see...
Thanks.

@tony_retrogamer make sure you edit the es_systems.cfg in /opt/retropie/configs/all/emulationstation/ otherwise it will get overwritten if you update.

Here's another good link along with Bakers to MAME setup. It covers pretty much every supported version on the Pi. The 'Arcade' drop down on the left shows the different sections even how to build and validate sets.

https://retropie.org.uk/docs/MAME/

I do keep most of the supported version sets non-merged (ROM set type not emulator) zipped and just extract the ROMs as needed. There is a lot of crossover between version sets if you plan to implement them all it's pretty redundant. Some emulators run certain games better than others so it's usually is a mix-and-match of MAME emulators and ROM/game subsets.

ly-tyrquake isn't working at the moment due to a faulty upstream commit. https://github.com/RetroPie/RetroPie-Setup/issues/2055#issuecomment-318223271

You'll need to wait for the fix, but if you're competent with the terminal, you can manually build the core with the commit reverted and it'll work again.

@tonythetiger
That "Sniper Mode" bug is a known issue for Reicast. Check out their official compatibility list:
http://wiki.reicast.com/index.php/Reicast_Compatibility_List?wap2

I watched a YouTube video of someone on an Android phone using Reicast and they had the same issue (from 2014):

More information here and here (both are also from 2014):
https://github.com/reicast/reicast-emulator/issues/76
http://forums.reicast.com/index.php?topic=122.0

@buzz
That did the trick! Thanks!

Kind regards
Toke

@timmyroux Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first (use a new topic and provide information about your set-up, as agreed when registering. Thanks).

lr-fceumm i tried to name them "xxxx (E). zip" and "xxxx(Europe).zip" and every time they play like regular ntsc.