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

    RetroPie Setup script not taking up full screen (showing in top left) but everything else is (games/ emulations station menus are)

    Scheduled Pinned Locked Moved Help and Support
    launching imageretropie setupretropie 4.8.4configure
    17 Posts 2 Posters 2.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.
    • W
      wtstreetglow1 @mitu
      last edited by

      @mitu not sure if it matters or helps either but this behavior existed when I had the pi hooked up to my normal television when I was just getting started on the build also. At this time, I did not have the pimarquee stuff installed.

      I'll still give your precious idea a go for sure as I have no clue how to fix this one on my own, but just wanted to add that as something I remembered from the beginning of this process.

      1 Reply Last reply Reply Quote 0
      • W
        wtstreetglow1 @mitu
        last edited by mitu

        @mitu said in RetroPie Setup script not taking up full screen (showing in top left) but everything else is (games/ emulations station menus are):

        Comment out the following line from config.txt:

        fbset -fb /dev/fb0 -g 1280 720 1280 720 16

        and reboot. See if the problem persist after this change.

        @mitu I gave this a test and the problem does still persist. (Not full screen on the launching image and anything involving a blue background terminal style screen)

        As I saw no other changes, I will still leave that setting commented out.

        Do you have any other thoughts? (I sure hope so because I've got nothing)

        This is now my autostart.sh

        #sudo mount -t cifs -o username=WESTON,password=****,nounix,noserverino //WESTONSPC/roms /home/pi/RetroPie/roms
bash $HOME/RetroPie-BGM-Player/bgm_system.sh -i --autostart
/usr/bin/python /opt/retropie/configs/all/PieMarquee2/PieMarquee2.py > /dev/null 2>&1 &
#fbset -fb /dev/fb0 -g 1280 720 1280 720 16

#hurstysthemedownloader

#/home/pi/scripts/themerandom.sh

emulationstation #auto
        1 Reply Last reply Reply Quote 0
        • mituM
          mitu Global Moderator
          last edited by

          What's your display resolution ? Does the issue still persist if you leave only EmulationStation starting up in autostart.sh ?

          W 2 Replies Last reply Reply Quote 0
          • W
            wtstreetglow1 @mitu
            last edited by

            @mitu Let me test what you ask here in the next 5 min

            My physical display resolution is 1280x960. As in, the actual physical screen size.

            In my config.txt (posted earlier), I have resolutions set to: It looks like mode 16?

            # 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=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
 
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
 
# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1
 
# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=1
#hdmi_group=2
hdmi_mode=16
#hdmi_mode=87
#hdmi_timings=1280 0 8 128 64 390 0 1 3 24 0 0 0 67 0 42009500 8
 
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2
 
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4
 
# uncomment for composite PAL
#sdtv_mode=2
 
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
 
# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on
 
# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18
 
# Additional overlays and parameters are documented /boot/overlays/README
 
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
 
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
 
[all]
#dtoverlay=vc4-fkms-v3d
overscan_scale=1
 
disable_splash=1
            mituM 1 Reply Last reply Reply Quote 0
            • mituM
              mitu Global Moderator @wtstreetglow1
              last edited by

              My physical display resolution is 1280x960. As in, the actual physical screen size.

              In my config.txt (posted earlier), I have resolutions set to: It looks like mode 16?

              Why ? There's no need to modify config.txt except in particular cases where the resolution of the display is not correctly detected. Is your display not working without configuring the resolution in config.txt ?

              W 2 Replies Last reply Reply Quote 0
              • W
                wtstreetglow1 @mitu
                last edited by wtstreetglow1

                @mitu said in RetroPie Setup script not taking up full screen (showing in top left) but everything else is (games/ emulations station menus are):

                Why ? There's no need to modify config.txt except in particular cases where the resolution of the display is not correctly detected. Is your display not working without configuring the resolution in config.txt ?
                @mitu

                That is what was happening when I moved the pi to the arcade screen, it was not showing a display at all until I started screwing with that stuff. (I started out with "safe mode" as in the docs and it came back so then I started from there with modifications)

                Would you like me to start back with this file as "baseline" and test again? (I am definitely not against this) And if so, can you direct me to where I can get a "base" file (unscrewed with)

                My whole file is in the previous post (with pastebin and system information)

                1 Reply Last reply Reply Quote 0
                • W
                  wtstreetglow1 @mitu
                  last edited by wtstreetglow1

                  @mitu With everything commented out of the autostart.sh

                  It is doing the same thing on the launching image (runcommand) screen and all screens involving terminal.

                  Is see a backup config.txt, let me start back with it and see what happens. I really don't think anything is going to change. If it were all screens through the whole system, it would make sense.

                  It just makes no sense to me that this is only occuring on terminal based screens (and the launching image which is runcommand, so terminal based also I guess)

                  UPDATE:

                  Started back from default config.txt:

                  All video went to the small marquee at the top of the screen, no video on main screen.

                  Now re- enabling info that was in autostart.sh (update shortly)

                  UPDATE2:
                  Marquee working properly but now has black bars around edges.
                  Still nothing showing on main display

                  So with default config.txt, nothing shows on main display

                  UPDATE3:

                  Enabled "hdmi_safe=1" only.
                  Both screens have black bars around all 4 sides
                  Launching image looks to be centered not but has black bars also.

                  Below is not my current 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=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

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

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
overscan_scale=1

                  Photo of current situation (while in game):

                  IMG_3197.jpg

                  Photo of launching image (still looks a little off-bigger borders top and bottom than side but that may be nothing, it is centered which is a good thing):

                  IMG_3198.jpg

                  I would definitely say this is trending positively.

                  1 Reply Last reply Reply Quote 0
                  • W
                    wtstreetglow1 @mitu
                    last edited by

                    @mitu Now I think we're getting somewhere for sure (after the updates above).

                    Can you give me some guidance on properly editing this config.txt file from my current state of safe mode.

                    I know my marquee is seen by pcs at 1280x720 virtually (even though physically, the screen size is 1280x390) and I know my main display is physically and virtually 1280x960.

                    Thank you for your guidance on all of this from the very beginning!!

                    W 1 Reply Last reply Reply Quote 0
                    • W
                      wtstreetglow1 @wtstreetglow1
                      last edited by wtstreetglow1

                      @wtstreetglow1 My attempt at editing the config.txt

                      ATTEMPT 1:

                      Uncommented hdmi_drive=2, uncommented "disable overscan=1",and commented safe mode back out.

                      Result: Marquee takes up full screen now on marquee screen, no video on the main display (also no audio- using hdmi so this makes sense)

                      ATTEMPT2:

                      uncommented hdmi force hot plug, uncommented hdmi drive.
                      Sound and Video are back and full screen on main display
                      Marquee is display full screen

                      All is working properly. Below is my final config.txt (for anyone else that runs into similar issues:

                      # 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=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1
 
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

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

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
overscan_scale=1

                      Thank you @mitu for all of your help lately!!

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

                        @wtstreetglow1 said in RetroPie Setup script not taking up full screen (showing in top left) but everything else is (games/ emulations station menus are):

                        All is working properly. Below is my final config.txt (for anyone else that runs into similar issues:

                        Which means the resolution settings were not necessary in the end. Did you connect the main display (not the marquee) on the 1st HDMI port (the one next to the USB-C power port) ?

                        W 1 Reply Last reply Reply Quote 0
                        • W
                          wtstreetglow1 @mitu
                          last edited by

                          @mitu Completely agree. As usual, I mess with stuff too much sometimes. It is hooked up as you have said, the primary display is hooked up to the HDMI directly beside the USB-C power port.

                          1 Reply Last reply Reply Quote 0
                          • 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.