Overscan issue

Mischief

on my system using overscan_scale=1 and positive over scan values, it affects both the framebuffer and the emulationstation output

For some reason not on mine and I have no idea why, I did a reinstall and ended up with the same issue.

BuZz

please paste (in a codeblock or via pastebin.com) your config.txt with this set, and also the output of uname -a and cat /etc/debian_version

Mischief

@BuZz said:

please paste (in a codeblock or via pastebin.com) your config.txt with this set, and also the output of uname -a and cat /etc/debian_version

Is there a guide for this, I am still new to all this and using guides for most of it. Ben using retroarch and emulationstation on my PC for a while and Retroarch for my PS3 just new to the Raspberry Pi.

I can make a video showing the issue if that helps?

BuZz

ssh into retropie

https://github.com/retropie/retropie-setup/wiki/ssh

and you can run those commands from the terminal. you can also get a copy of config.txt via cat /boot/config.txt

or use sftp to copy it off

I assumed as you were already editing this file you were using the terminal.

Mischief

@BuZz said:

ssh into retropie

https://github.com/retropie/retropie-setup/wiki/ssh

and you can run those commands from the terminal. you can also get a copy of config.txt via cat /boot/config.txt

or use sftp to copy it off

I assumed as you were already editing this file you were using the terminal.

Yes i'm using the terminal and learning as I go.

I have to apologise as I have solved it, for some reason I had overscan_scale=1 twice at the bottom of config.txt one had =1 the other had =0 strange as I never added this line myself I just adjusted the first one I saw. Suffice to say It is now solved and working as it should I have adjusted the overscan_(direction)= values and the screen has no black bars or cropped.

Thanks for the replies and help to all.

Drakaen391

Check to see if there are '#' signs before the overscan setting...

If there is, remove them

Mischief

@Drakaen391 said:

Check to see if there are '#' signs before the overscan setting...

If there is, remove them

There was none over the repeated lines at the bottom but as I said in my last post I have solved it now by removing one of the repeated overscan_scale lines, cheers.

jake74

fwiw, I've had exactly the same problem with a fresh apt-get updated retropie.

In the config.txt, the overscan_scale=1 was commented out, and the config had repeated the last 4 commands again, looking like this—

Additional overlays and parameters are documented /boot/overlays/README

Enable audio (loads snd_bcm2835)

dtparam=audio=on
gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=256
#overscan_scale=1
gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=256
#overscan_scale=1

And no matter how many times I edited the overscan settings in the Raspi-config in Retropie, it would not change the overscan.

So, I deleted the last 4 lines, and the end of my config now looks like this—

Additional overlays and parameters are documented /boot/overlays/README

Enable audio (loads snd_bcm2835)

dtparam=audio=on
gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=256
overscan_scale=1

and it works without overscan just fine. Bit of a bug if you ask me, as unless I ssh'd in, I could not unset Overscan.

regards

Drakaen391

I do think there is a bug in the overscan setting... I had to manually fix mine because it wouldn't work

Twitch0815

Just going to note this. I am using the BerryBoot version. Just grabbed the Berryboot image from the main site, chose the os Retropie 3.6 from other category.
I get much stabler overscan settings. And my screen is properly stretched to fit. Trying to determine which settings they are getting right will update you when I figure it out.