And of course adafruit put 4gb pi's up not an hour after I posted this. So of course I jumped on it. Now, an hour after that, they are out of stock of 4gb, but the 2gb is in stock.
Oh well, 4gb is overkill, but it's better than scalping prices off elsewhere.
@good_punk Not sure what tweaks Dosbian added to their Dosbox versions, one thing I see is that they've disabled the KMS GPU driver in their config
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
Either Dosbox or Dosbox-Staging should be ok, start with the default configuration and try to find a fixed cycles value that's suitable for each game (on ARM, cycles = auto doesn't work so well). You can ask in the Dosbox-Staging topic or look in the Dosbox Staging wiki for pointers.
It was due to bad dumps. I had bin files and a .zip romset solved the problem.
The control issue came from the 8bitdo controller. I connected it like a switch pro controller and everything is fine again.
I went further and replaced some of the original roms with dreamcast ports in order to use Redream. Really good perfs now !
As of now, I set up lr-mame2003 as I need it with a few options, saved the retroarch.cfg once and turned off "save on exit". It's now pulling the video parameters of every game I throw at it based on what I have listed in the file I posted to you.
i guess i'm not totally clear on what you want to achieve. retropie at the basic level has a global retroarch.cfg (/all/retroarch.cfg) which has the baseline settings for all libretro (lr-) emulators. then beyond that there's per-directory configs (eg /mame-libretro/retroarch.cfg) which by default point to an input_remapping_directory, and then defer back to the global config, as you've shown above.
then additionally you can have per-game overrides, per-core overrides, and gamename.ext.cfg overrides. to set up any of these you don't need to ever set 'save on exit' on. it's probably safest to manually create them, actually.
so i'm not sure exactly what hierarchy of configs you want to end up with, and what you currently have.
Ultimately... to not have this happen the next time I choose to upgrade any core part of the build... LOL. I thought I was doing something good by updating RA from 1.8.8 to 1.9.4 then .5. But my build has apparently become so convoluted that I disrupted areas I wasn't aware of.
I'm going to say by adding in the scriptmodules I added more issues than I was aware of. Just the idea that I turn off a shader and I loose performance means something is crossed somewhere.
I'll keep poking around my config files and hopefully find out what's causing some of this. What you and mitu offered was insightful and helped a lot.. but I think this is something that will ultimately leave me with a "it's working good enough" scenario.
@greenhawk84 Sorry currently my pc has broken down so i backed up Retropie and installed Raspbean so i could continue to work from the home office, so all i got left for gaming momentarily is my RPI0 which i turned into a Sega mini :-(
That happened also in 4.6 and it's not specific to RetroPie.
Since the Pi4 supports 4k, by default it will use the video mode advertised as 'preferred' by the TV. If that's 4k, then this is what it will use. Previous models didn't have this issue, since they didn't support 4k. You can check with tvservice -m CEA what video modes your TV supports and what is the preferred mode.
Well, i doubt that's gonna happen soon, netlist emulation has been around for 10 years and always required a somehow good cpu. It'll probably take some time before they make another breakthrough performance-wise, and i'm not sure the MAME team even care about performance in the first place.
Actually, this driver is the only vector games driver we are missing. In my previous post i was talking about netlist emulation in general, since it's used in most 70s and early 80s games, i guess we'll keep using samples for now.