kiteretro / Circuit-Sword

GNU General Public License v3.0
135 stars 27 forks source link

Overscan problem on 640x480 display #98

Closed Joe2824 closed 4 years ago

Joe2824 commented 4 years ago

If I change the overscan left or right the display starts to flicker. Overscan top and bottom have no issues.

I'm using the newest board with the new 640x480 display.

bin101 commented 4 years ago

I am facing the same issue but at my side I get the flickering also if I set top/bottom overscan.

kiteretro commented 4 years ago

Hi why are you trying to use overscan? Does anything get cut off in normal use?

bin101 commented 4 years ago

For my part I wanted to cut off some pixel on the bottom because my glass lens printing is covering some space of the display. But now I think overscan is the wrong approach for this.

kiteretro commented 4 years ago

Overscan isn't very good for this need because it will compress the image making the whole thing blurry, it doesn't reduce the visible screen area (e.g. if you set overscan bottom as 20px, it will still output 640x480 into a 'window' at 640x460, BUT the overscan doesn't scale quite like that, it usually ends up doing a linear scale so it will narrow the sides too..). You may have better luck editing the HDMI settings line, which is the long one that you have to uncomment to get the LCD to work, and adjust the '480' value lower, that MIGHT work but it will likely not.. the best solution is to make the visible area visible.. or you can adjust these things per app better in the SELECT + Y menu thing and set the scaling and offset per app instead

Joe2824 commented 4 years ago

The tipp with the HDMI settings does not work. The boot looks not nice because the text is hidden from display glass. Also the battery and wifi icons are hidden. Is it possible to change the location of these icons?

img

kiteretro commented 4 years ago

Currently there isn't a way, i'll have a look to see if I can find some settings that may help

kiteretro commented 4 years ago

Closing as this will be fixed as part of #67