@Darksavior That's what I was referring to. If you have saved out your retroarch config on older version the offset will be wrong (the aspect ratio is a number which is an offset into a list - they added a new aspect ratio, but not at the end, so it broke old configs).
That was it! I must've changed that either by accident at some point, or sometime a while ago and not remembered. But either way, I went to the Runcommand menu and chose 'Remove video mode selection' and now it's working perfectly. Thanks!
i don't think there's a good way to do this. if you do a custom resolution in retroarch that includes some padding it
a) won't solve the issue in non-libretro games/emulationstation, etc.
b) will need to be done for each arcade game as they have many different resolutions.
@dontarrestme I don't know what the other emulators use off the top of my head but N64 uses 320x240 resolution by default. If you use the -highres plugins it makes the screen look a lot sharper. I only play my games on my 46 inch TV and it looks fine to me for how large the image is stretched compared to old crt TV's
In Raspi-Config, Select Advanced, Overscan and then Disable. That should allow your GUI to extend to the edges of your screen. if it's still not to your liking you'll need to change the Overscan value in Config.txt in the /boot partition on your MicroSD card.
@delirium_cordia RetroPie (and the Raspberry PI and other SBCs) are all about tinkering and learning new things. No need to rush things if you're not in a hurry - ask away in the forums if you cannot find the answer in the Docs.
I believe these are the lines you need to look at.
In this file --> dosbox-SVN.conf
Found here --> /opt/retropie/configs/pc
Use your monitor's native resolution for the first option.
Use aspect=true, if you want the correct aspect ratio - after scaling. False, if you want it stretched to fill your monitor.
scaler=XXXX - XXXX=your scaler of choice...none, normal2x, normal3x, advmame2x,....etc... Use this to scale the image.
BTW the vector games did work on the last binary so it may have been a core option affecting this. there has been some fixes since then though including some relating to the new vector code and the settings, but the last binary is not "old" (It's from the 11th October). I will update the binary though.
Thank you @BuZz if there are still problems with vectors in mame2003 after this binary update I will work to resolve them.
Of course that's buried in a bazillion other lines in the .CFG.
That's because you enabled 'Config Save on Exit' and all the configurations have been dumped in this file. You shouldn't do that, core options are saved by default (in a separate file) and for other options you use 'Save Core Override'.
Replace the retroarch.cfg file contents you have now in the gb folder with