@mitu said in Regional dependencies on ROMs across different emulators:

The emulator should be able to scale it to your native TV screen's resolution.
EDIT: What I've other people recommend - and it sort of makes sense - is to try and run the NTSC version of a ROM when possible. NTSC ran at almost 60hz, similar to the modern displays.

Bingo - that's exactly what I just did before I'm reading this :-)
Set boot config to CEA-4, removed default emulator video choice from on-game startup menu and sorted out my ROMs so now it's all USA (NTSC) versions.
Now it's all perfect.
As always: Thanks buddy for your good explanation and clarification.

@barbudreadmon OK, so I tried again with the list of games you mentioned last time. Played every game about 5 minutes and had Frameskip = 1 for all of them from the beginning. I also enabled Cyclone (except for R-Type Leo, I think). This time I enabled the FPS counter and jus took notice how it behaves, I think the final RA log message about dropped frames is not so relevant.
Both cores play almost the same, there's no notable difference between them as far as I played.

rtypeleo - noticeable sound glitches (not so annoying), default runs at about 48 Fps. Increasing Frameskip to 2 makes it go to 50-52, but it's noticeable it's not running at full speed. Almost passed the first boss after the asteroid field.

firebarr - slowest of all, default (gcc) runs at about 48fps, but the sound artifacts and slowdown are more noticeable than for rtypeleo. The clang core runs about the same (46-48), but not better. I didn't increase the frameskip to 2, seems the game is quite taxing.

killbldp seemed to run fine, at about 60 fps, there's no noticeable slowdown. I played a match in both cores, seems fluid (remember it's still with frameskip = 1). If I remove the Frameskip, the FPS is around 58-59, but no noticeable slowdown.

svg this one I tested more. I noticed that if I pick one of the first characters, the FPS is ok (around 59), but if I pick for instance Wells, which has the 2 spinning blades animation, it dips to 55 for the round. Running again with frameskip = 2 makes the FPS go up again to 58-59.

I re-tested sfiii2 with frameskip = 1 and looked at the FPS, seems to be around 58, still very playable to me (I have to learn to block though, I got kicked out from the first match). Game was still in widescreen mode.

@edmaul69 Thank you, problem solved. Hopefully this will help people in the future.

@mitu I don't have that with the Saturn emulator but I do witht he PSX emulator. Luckily the game was made for PSX as well as Saturn so I;m playing the same game on the PSX now. Disc swap works fine.

@hermit That's not how it works. If the ROM in question worked with an older version of the snes9x Libretro core, but the same ROM has an error now, we should report this to the upstream project - so it gets fixed in the future.
You already have a topic opened on the Snes9x board - you can report this regression there, mentioning the ROM name (and checksum) and the versions implied - the one working and the non-working one.

@cyperghost I'm sure you're right! Thanks, but I don't think I have a need for the other tool...the SaveStateManager was the very last thing I missed having on my Pi. :)

Edit: I actually installed it anyway..a gamepad compatible file manager can always come in handy. :) Thanks again!

@mitu
No i didn't,
and thank u

Maybe you can choose the system where you need this info for .
If you change retroarch.cfg in "all" directory, this is for all emulators.
Maybe you can change Settings only for selectec systems by editing /opt/retropie/configs/SYSTEMNAME/retroarch.cfg

@mitu As the 16.04 still has support until 2021 I will still keep with it a little bit and continue reading the comments, if in a while there is nothing very negative about the 18.04 I upgrade. Even because this pc is an old Dual-Core Celeron that I use as a retro console and to watch some videos.

@rmills55 Post your /boot/config.txt file to check for any overclock settings.

and it can see i have about 60gb available.

I was referring to the RAM allocated to the system, not the space on the card.

@mitu
Yes I can access the share no problem if I mount it manually with the pi user. It's just not mounting at boot.
I'll have a check of mount later as I'm out all day.
Thanks
Rob

2 years later... thank you so much. I would have never figured that one out.

@ClassicGMR Aha. I suppose that happened some time ago, because right now the scraper doesn't work with the new TDGB API/Site. You might want to re-scrape those entries (or the whole list) using another source site (ScreenScraper) or - if you have a recent Emulationstation - scrape them using the internal ES scraper (from either TGDB or Screenscraper).

@oleguer said in Config .rc to can load rom on advance mame:

I read on the wiki of advance mame the rom need a .rc file to can be load with advance mame

Where exactly is that ? AdvanceMame has extensive documentation over at https://www.advancemame.it/doc-advmame.

@hfgx1 This is not an error, but just a progress indicator for you to know what's Emulationstation doing during startup. If you find that ES stays a long time ago at this stage, then it means you have a lot of ROMs and it takes ES a long time to scan the ROM folders.
How many ROM do you have ?

My advice is to not use 'Save on Exit' and use Core/Game overrides for changes you want to add to the controls. If you want to have a global configuration setting applied to all Libretro cores, open RetroArch from the RetroPie system in Emulationstation, make your changes there (it will modify the global RetroArch config file) and use Save Configuration to save those changes. More details about the configuration structure used by RetroArch in RetroPie can be found here.

You my friend are a genius! I set controls on player 1 to "Select" = "Start" and "Start" = Nothing and player 2 "Select" = Nothing and "Start" = "Start". Works like a champ! I wish it was a little more intuitive, but it seems to work great.

Thanks again for all your help!

@mitu Thank you.
For now I didn't find any game title which behaved unresponsive, so I'll keep it on 5 for now.