@mitu and @Thorr69

I found the TV setting. Thank you very much its perfect. Will also test out the cmdline.txt method since that setting was not easy to find on the TV!!

@mitu thank you very, very much for the help and information about kernel. :)

@sleve_mcdichael hello, I appreciate your help, I uploaded the files you requested here:
https://drive.google.com/drive/folders/1w5Q1e88_zQtoAH_Et1ACRX61zJqStqWi?usp=sharing

Update: Okay, not sure what reverted, but I just did a full system update this morning (usual routine every couple weeks) and the SNES bezels are fitting again.

@mitu
Ok. All clear now. Thanks for the clarification.
I'm not a dev guy, so it's beyond my knowledge to modify the source code. I guess I have to prepare two set of config.txt, and reboot into the proper video mode when needed.

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

@Peetem Can you share a snip of the files you edited and changes you made? I'm running into this same issue on a Frogger Arcade1Up cabinet I'm working on.

@buzz I've tried this before, but I've tried again just now, to make sure.

overscan_top=40 overscan_bottom=40 overscan_left=40 overscan_right=40 overscan_scale=0

While this does add the overscan on the console, it also adds it to EmulationStation and RetroArch while emulating.

@billy Simply by editing your 1st post and adding something like [Solved] to the title, though I am unsure whether there is a forums recommendation about the how ( @mitu ? ). Some seem to prefer adding it at the titles start, others add it to the end. Most use square brackets, some regular ones.

Well, 3 days later, no more weird out of frame picture! I think I can safely say that it solved it. Thanks again @mitu !

@mitu said in N64 emulator doesn't save any settings:

you need to save a game or core override after you've changed the parameters

Can you please tell me where I can find the Overrides-menu? Or which solution would be the best?
When I switch the "Use Global Core Options File" to OFF, then I still the the same problem.

If you're using berryboot, that has its own config.txt

Berryboot isn't supported btw, and we don't provide berryboot images for the rpi4. I wasn't sure if you meant above you installed the standard image to test after.

After downgrading the kernel to 1.20190401-1, I tried to run RetroPie-Setup which upgraded the kernel to 1.20190517-1. Now the overscan settings still apply to both console and ES. I don't know if this is because of the downgrade-upgrade procedure, or because of the changes I made to /boot/config.txt. Anyway I paste here the relevant settings I have in the file:

disable_overscan=1 overscan_left=20 overscan_right=20 overscan_top=11 overscan_bottom=11 overscan_scale=1

@Sakitoshi Awesome! I modified

/opt/retropie/configs/all/autostart.sh

so it calls

emulationstation --screensize 640 576 --screenoffset 37 79

when booting and when reseting ES from the menu, and it's working flawlessly!
IMG_20190701_210343.jpg

(I may tweak the offsets based on the final installation of the display, but it looks awesome already)

Thank you so much both of you!

@canispeaktodave that makes sense. once you use overscan you're not using the native resolution, so blurring/artefacts.

i believe the overscan settings are based on pixels, so assuming

overscan_left=-12 overscan_right=15 overscan_top=-30 overscan_bottom=20

you can work out the post-overscan resolution by applying the left and right numbers to the width (480), and the top and bottom numbers to the height (320)

it's a bit confusing to me that you have positive and negative numbers in your overscan settings, though. that would seem to shift the image when normally you'd want to shrink it, but it's been a while since i played with that stuff.

Well, thanks for coming back with the solution and happy gaming.

@mitu I have tried disabling it, it still doesn't work. I honestly don't know what the resolution is for my screen, I think it's 720x480. I'm actually using a car dvd player, the kind that straps onto the back of a headrest. I'm using the composite output.
EDIT: Ok then, I just rebooted without touching anything and it's working fine, so thank you for your help.

@dankcushions Ah! Wonderful. I'll look into that

@Gadgetguy yea I don't see a game mode listed in the manual for that tv. At least you got it figured out.

Huh. Now that's weird.

I tried what you described (thank you very much for that!), and while the script works like a charm, for some reason fbi fails to load the 1920x1200 splashscreen. It literally returns a black screen with

/home/pi/RetroPie/splashscreens/retropie-extra/rookervik-pixel-16x10.png: loading FAILED

written at the bottom. The weirdest thing is that if I run

sudo fbi -T 2 -once -t 20 -noverbose -a -l /etc/splashscreen.list >/dev/null 2>&1

after start up, mimicking the syntax in /opt/retropie/supplementary/splashscreen/asplashscreen.sh, the image is shown normally!

So close, yet so far! Any ideas?

EDIT: UN-FREAKING-BELIEVABLE! That was happening because I’m using USB auto-mount for loading roms into the system. For some reason, that option also overwrites the splash screens directory, but the pendrive is only mounted AFTER the splash screen is actually shown on startup. Hence, when I moved the stretched image into the directory, I was actually moving into the pendrive, which is ignored by the Pi on startup! All I had to do was unmount the pendrive, copy the file into the SD card and it worked! 😁 Thank you very much once again for all the help!