@TPR Nice to hear it, 1080p should be fine for most TVs today, but there are still those with max. at 1280x720 (HD Ready) and other display types (e.g. computer monitors) may be a totally different story (That's why it would be nice if the PI5 could also switch cmdlines by edid :/ )

@mitu I've recompiled it with the SLD1 version and the speed is up again (hooray!) but it doesn't seem to want to output as opengl, so the screen size isn't playing ball again, sadly.

Please add some more details about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Pressing A when the game is loading and changing the resolution for the emulator. Can't seem to find the right one.

Just remove any custom resolution and leave the game/emulator running with the default resolution. Check if you haven't got a 'render resolution' configuration and remove it also.

I saw an answer somewhere to run the command sudo raspi-config. Is that the command, nothing else?

raspi-config sets the global resolution, used when starting the Pi, but it doesn't affect the individual game/emulator resolution if you're changing it from the runcommand menu.

I also saw an answer to go to Settings and choose "Adjust Resolution" but can't seem to find that.

Maybe in the Configuration Editor ?

@richard-baker please provide the information and files requested

We don't support 3rd party images - as outlined in https://retropie.org.uk/forum/topic/3/read-this-first.

Why don't you start with a clean image ?

@mitu thanks,it looks like xinit wasn't launching but in any case changing to SDL2 has made it much better! Much appreciated.

@fishermanbill said in Making 'overscan' work on an LCD screen:

@dankcushions so you'd need to set up a config for every arcade that has a overscan output? There's an awful lot of them - eek!

unfortunately it’s probably necessary. it’s possible to automate some of this stuff - i believe i experimented with letting them overrun by a certain tolerance when developing https://retropie.org.uk/forum/topic/4046/crt-pi-shader-users-reduce-scaling-artifacts-with-these-configs-in-lr-mame2003-lr-fbalpha-lr-nestopia-and-more-to-come

the issue is that arcade machines, unlike console games, had CRTs that were manually configured for the game. so they often have crucial gameplay info (eg score) running right to the edge of the image, because they knew an engineer/arcade operator would be adjusting the CRT to suit.

for this reason it’s probably not safe to automate an amount of ‘overscan’ in arcade games.

You allude to being able to figure out the custom resolution but how would you do that from config files?

you have to manually do it whilst the game is running

Also how do you see your change where it outputs the resolution on screen?

when you adjust the resolution in the menu it should be visible behind, no? the menu is translucent.

@mitu Thanks. I think I found the problem.
This is my retroarch.cfg (taked from the previous version of my Retropie (4.3.1.2.):

# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line input_remapping_directory = "/opt/retropie/configs/gb/" # 19 = Config, 20 = 1:1 PAR, 21 = Core Provided, 22 = Custom Viewport aspect_ratio_index = "22" # these two define the pixel size of the emulated screen # keep this in the same ratio as the original console # eg: GBA 240x160 * 3 = 720 x 480 custom_viewport_width = "480" custom_viewport_height = "432" # the following two decide how far from the left and top the game screen is shown # to centre the game display use your original resolution, minus the screen size, divided by two # this example for 1080p screen (1920x1080) # (1920 - 720) / 2 = 600 custom_viewport_x = "400" # (1080 - 480) / 2 = 300 custom_viewport_y = "324" #include "/opt/retropie/configs/all/retroarch.cfg"

I modify Custom Viewport aspect_ratio_index from 22 to 23 and now screen size is correct.

Thank you very much.

@nharrer
Did you make any progress with this issue?

I'm facing exactly the same problem now.

Ok, seems it only happens with Damaso images. I have tried a different one, and no troubles so far. :( Sorry for bothering everyone in here

@mitu it’s the little mini screen that shows the game. I’d send a pic but it won’t let me on here. It only shows the top left corner of the game

Please add more info about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.
What resolution does the GamePi20 support ? You can try using raspi-config and specify the boot resolution to match the one supported by the display.

@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!

@sirhenrythe5th said in Amiberry screen position:

Done, works great!
Thanks again for supoort @davidgrohl

Great! I’m glad it helps.

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.

the only way i can see is using the overscan settings to add some overscan to give you a vertical border. eg: https://elinux.org/R-Pi_Troubleshooting#Big_black_borders_around_small_image_on_HD_monitors
you'd want something like

disable_overscan=0 overscan_top=20 overscan_bottom=20 overscan_scale=1

increase the 20 for _top and _bottom until you get the right amount of border.

however that will
a) mess up the aspect ratio of the games, making them look fatter. i guess you could add

overscan_left=X overscan_right=X

where X is the same as the number you're using above.
b) give you some pretty brutal scaling artefacts, since you're fairly low resolution to begin with.

maybe there's another way...

Thanks for the tip @dankcushions. This was driving me insane. I'll update from source when Mario Kart 64 misbehaves from now on :)