RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    overscan_ NOT WORK AFTER UPDATE! 4.5 in EmulationStation.

    Scheduled Pinned Locked Moved Help and Support
    4.5updateoverscan
    33 Posts 5 Posters 5.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • saccublendaS
      saccublenda @mitu
      last edited by

      @mitu said in overscan_ NOT WORK AFTER UPDATE! 4.5 in EmulationStation.:

      Can you run fbset to see what's the screen size of the console and compare it to the TV's resolution ?
      You can try adding disable_overscan=1 to remove any overscan borders altogether.

      With disable_overscan=1 I get from fbset

      mode "1920x1080"
          geometry 1920 1080 1920 1080 32
          timings 0 0 0 0 0 0 0
          rgba 8/16,8/8,8/0,8/24
      endmode
      

      With this configuration the console fits the screen and ES goes off screen.

      With #disable_overscan=1 and

      overscan_left=10
      overscan_right=10
      overscan_top=10
      overscan_bottom=10
      

      I get from fbset

      mode "1804x964"
          geometry 1804 964 1804 964 32
          timings 0 0 0 0 0 0 0
          rgba 8/16,8/8,8/0,8/24
      endmode
      

      With this configuration both console and ES have black borders, but the console has significantly larger borders than ES.

      S 1 Reply Last reply Reply Quote 0
      • S
        SergioPoverony @saccublenda
        last edited by SergioPoverony

        @saccublenda

        #disable_overscan=1  
        overscan_left=10
        overscan_right=10
        overscan_top=10
        overscan_bottom=10
        
        mode "800x600"
            geometry 800 600 800 600 32
            timings 0 0 0 0 0 0 0
            rgba 8/16,8/8,8/0,8/24
        endmode
        

        and

        disable_overscan=1  
        #overscan_left=10
        #overscan_right=10
        #overscan_top=10
        #overscan_bottom=10
        
        
        mode "800x600"
            geometry 800 600 800 600 32
            timings 0 0 0 0 0 0 0
            rgba 8/16,8/8,8/0,8/24
        endmode
        

        I tell NOT WORK tested Pi3A+ and Zero W

        Any edit work ONLY TERMINAL/CONSOLE and not work in ES

        1 Reply Last reply Reply Quote 0
        • matchamanM
          matchaman
          last edited by

          I can confirm this, the exact same settings on 4.4 vs 4.5.

          mituM 1 Reply Last reply Reply Quote 0
          • mituM
            mitu Global Moderator @matchaman
            last edited by mitu

            @matchaman Are you also using a TV through HDMI ? Do you have explicit overscan_left/right/etc. settings in the config file.

            For the ones using a TV, can you try commenting/removing any overscan settings and leave just

            disable_overscan=1
            

            If this will behave like in @saccublenda's case, the console output would fill the screen, but Emulationstation would be off. Try using the TV settings and put the HDMI connecting into Game mode (or PC mode, I know my TV has a PC label for the HDMI connection which changes the output settings) or set it to stretch the image (fit-to-screen ?).

            EDIT: I assume you already have overscan_scale=1 in your config (which worked before 4.5).

            saccublendaS 1 Reply Last reply Reply Quote 0
            • saccublendaS
              saccublenda @mitu
              last edited by

              @mitu said in overscan_ NOT WORK AFTER UPDATE! 4.5 in EmulationStation.:

              EDIT: I assume you already have overscan_scale=1 in your config (which worked before 4.5).

              I do.

              1 Reply Last reply Reply Quote 0
              • ?
                A Former User
                last edited by

                I have problem with overscan settings too, but only, when i am in the terminal or during boot. In ES everything is fine.

                I'm using the following settings in rasbian stretch/buster, retropie 4.4 without overscan problems:

                 .***.     Friday,  5 July 2019, 08:44:51 PM
                     *****     Linux 4.19.50-v7+ armv7l GNU/Linux
                     `***'
                      |*|      Filesystem      Size  Used Avail Use% Mounted on
                      |*|      /dev/root       6.7G  2.6G  3.8G  40% /
                    ..|*|..    Uptime.............: 0 days, 00h00m40s
                  .*** * ***.  Memory.............: 630396kB (Free) / 765608kB (Total)
                  *******@@**  Running Processes..: 118
                  `*****@@**'  IP Address.........: 192.168.1.2
                   `*******'   Temperature........: CPU: 53°C/127°F GPU: 54°C/129°F
                     `"""'     The RetroPie Project, https://retropie.org.uk
                
                pi@retropie:~ $ sudo nano /boot/config.txt
                  GNU nano 2.7.4                File: /boot/config.txt
                
                # For more options and information see
                # http://rpf.io/configtxt
                # Some settings may impact device functionality. See link above for details
                
                # uncomment if you get no picture on HDMI for a default "safe" mode
                #hdmi_safe=1
                
                # uncomment this if your display has a black border of unused pixels visible
                # and your display can output without overscan
                #disable_overscan=1
                
                # uncomment the following to adjust overscan. Use positive numbers if console
                # goes off screen, and negative if there is too much border
                overscan_left=-33
                overscan_right=-33
                overscan_top=-18
                overscan_bottom=-18
                
                # uncomment to force a console size. By default it will be display's size minus
                

                results from fbset:

                mode "1250x660"
                    geometry 1250 660 1250 660 32
                    timings 0 0 0 0 0 0 0
                    rgba 8/16,8/8,8/0,8/24
                endmode
                
                saccublendaS 1 Reply Last reply Reply Quote 0
                • saccublendaS
                  saccublenda @A Former User
                  last edited by

                  @alphag Same here. Either I can make ES fit the screen or console/splashscreen, but not both. I was able to have both fit the screen on 4.4.

                  1 Reply Last reply Reply Quote 0
                  • matchamanM
                    matchaman
                    last edited by

                    @mitu yes, I'm experiencing the exact same issue with @saccublenda. I understand what's going on but I assume it should be fixed, it shouldn't be like that...

                    1 Reply Last reply Reply Quote 0
                    • saccublendaS
                      saccublenda
                      last edited by saccublenda

                      As a check I downgraded the kernel as explained here and now the overscan settings apply both to ES and console, so they can now both fit the screen.
                      I think it is then a problem with the new kernel.

                      matchamanM 1 Reply Last reply Reply Quote 2
                      • saccublendaS
                        saccublenda
                        last edited by saccublenda

                        Maybe everyone already knows that, but I've found out that disable_overscan=1 does not actually disable overscan (so ignoring the overscan settings), but instead disables some "default" overscan settings. In fact, with

                        #disable_overscan=1
                        #overscan_left=0
                        #overscan_right=0
                        #overscan_top=0
                        #overscan_bottom=0
                        

                        I get from fbset

                        mode "1824x984"
                            geometry 1824 984 1824 984 32
                            timings 0 0 0 0 0 0 0
                            rgba 8/16,8/8,8/0,8/24
                        endmode
                        

                        meaning that without disable_overscan=1 I get a "default" border of 48 on top, bottom, left and right (my display size is 1920x1080). Any additional overscan border explicitly set in /boot/config.txt would add to this default values, in fact with

                        #disable_overscan=1
                        overscan_left=10
                        overscan_right=10
                        overscan_top=10
                        overscan_bottom=10
                        

                        I get

                        mode "1804x964"
                            geometry 1804 964 1804 964 32
                            timings 0 0 0 0 0 0 0
                            rgba 8/16,8/8,8/0,8/24
                        endmode
                        

                        Instead with

                        disable_overscan=1
                        overscan_left=10
                        overscan_right=10
                        overscan_top=10
                        overscan_bottom=10
                        

                        I get

                        mode "1900x1060"
                            geometry 1900 1060 1900 1060 32
                            timings 0 0 0 0 0 0 0
                            rgba 8/16,8/8,8/0,8/24
                        endmode
                        
                        1 Reply Last reply Reply Quote 1
                        • S
                          SergioPoverony
                          last edited by

                          @mitu need add this in isssue on github

                          mituM 1 Reply Last reply Reply Quote 1
                          • matchamanM
                            matchaman @saccublenda
                            last edited by

                            @saccublenda said in overscan_ NOT WORK AFTER UPDATE! 4.5 in EmulationStation.:

                            As a check I downgraded the kernel as explained here and now the overscan settings apply both to ES and console, so they can now both fit the screen.
                            I thin it is then a problem with the new kernel.

                            Same here. I'll wait for a while till I upgrade again.

                            1 Reply Last reply Reply Quote 1
                            • mituM
                              mitu Global Moderator @SergioPoverony
                              last edited by

                              @SergioPoverony Feel free to add it - github.com/raspberrypi/linux.

                              S 1 Reply Last reply Reply Quote 0
                              • S
                                SergioPoverony @mitu
                                last edited by

                                @mitu more rules. i bad understand

                                mituM 1 Reply Last reply Reply Quote 0
                                • mituM
                                  mitu Global Moderator @SergioPoverony
                                  last edited by

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • saccublendaS
                                    saccublenda
                                    last edited by saccublenda

                                    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
                                    
                                    1 Reply Last reply Reply Quote 1
                                    • First post
                                      Last post

                                    Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                                    Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.