Please test: Random Game selection/launch via Video Screensaver
-
@darknior Choose Yes. That's what you want. It's "on" by default.
EDIT: you will need to reset the system after that to that effect.
-
@pjft I want to remove Overscan, to have the Glitch and make the tests.
But i can't it is so strange bug i never see before :(I choose no to remove i reboot and always Overscan
I go edit the config.txtdisable_overscan=1
Setting is fine to remove Overscan but Overscan tay always !
It is a silly joke :(Like some time it mount my 1To Hard drive with videos and games without any problem, and some other i reboot 10 times and i never have my HDD :( :( :(
-
@darknior you're not following. The error happens when overscan is on :)
Trust me on that. Mark it yes (it should become 0) and then reboot. The glitch should come back.
It's just an unfortunate name for the option, with the negative label.
-
Like write in this doc : https://github.com/RetroPie/RetroPie-Setup/wiki/Overscan
My image is now croped and i can't read left menu :(
I want to add again the black borders to see all my image screen !
I try with and without Overscan and nothing change it is silly and it really boring me
I really don't understand, like when my PI don't want to auto mount my HDD !!!And i only have the BUG with the black borders, if i can't put them back i can't do any test :( :( :(
Now i want to take my PI and throw him by the window !
1 hour left for nothing :( -
@darknior let's take a moment here. We can get this back. The borders only show up if you have Overscan enabled.
If you edit the
/boot/config.txt
fileAnd set
disable_overscan=0
Or comment out the disable overscan=1 line, and reboot, you'll get the borders back.
If you don't yet, do send over your config.txt file's content via pastebin, as there are a few finer grained options we may need to add, namely the actual seeing for the size of the border, and I want to see what you have there before making any changes.
Are you booting from a USB Drive/PiDrive?
Thanks for testing and sorry for making you go through this, but we'll sort this!
-
Hi @darknior .
Did you manage to get your Pi back to the previous state? If not, send over the config.txt file - I want to make sure we sort that out. :)
-
Thanks for your help, i already try to use :
disable_overscan=0 or #disable_overscan=1
But noting is working, it is so strange ? :(
I'm booting on my 16 Go SD Card.
And i have enable auto-mount for my USB Hard Drive 1To Seagate with all the ROM, ISO, and VIDEOS ! -
@darknior send over the full file.
These are the following parameters you then want to adjust:
# 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
Start with those (uncomment them!) and adjust the values as needed :)
See if it makes a difference. In case of doubt, add very large numbers, to see if it's making an effect.
If not... we'll see. I recently heard of a case where we were editing the wrong boot/config.txt file :)
-
I also already try it last day when read the doc
http://elinux.org/R-Pi_Troubleshooting#Big_black_borders_around_small_image_on_HD_monitors
Today i try again with
overscan_left=40 overscan_right=40 overscan_top=40 overscan_bottom=40
But noting change, it is my problem :(
Maybe like you write there is an other file to edit ?
I modify : /boot/config.txt -
@darknior Well, try 400 - something meaningful. You'll notice immediately if you're editing the right file :) Comment the "disable_overscan" line, as you had it earlier.
If you're having problems on your left side, maybe just start with:
overscan_left=500
If anything happens, it'll be immediately visible. What TV brand and model are you using, by the way?
I don't see anything weird on your file, so I can't comment much more at the moment.
I was referring to this, but I don't think it's your case.
Let me know.
-
Hoooooo i finally understand something so strange LOL
Over scan are working fine but not every where !
I have them on the RETROPIE BOOT LOGO with the red pad. I can see the 16 black borders and now the 400 left border :)
But when ES is starting and when the carrousel of systems is show, the Over scan disappear :(
So strange ... how is it possible ??? -
@darknior Hm.
That is weird. Can you send over a picture?
Try doing 400 on all sides now, just for the sake of keeping it proportional.
Can you send over a picture of ES, for me to try to understand what may be happening?
What about when the video renders full screen, does it also not show the borders?
And you're certain that this wasn't happening in ES before?
What about when you go to the terminal, do you also see the borders?
-
You can see RETROPIE in mini size at beginning and end
ES normal size and some videos ...
I think videos are fine in full screen not cropped, we ca see life bars in games ...
I never have this problem before -
@darknior Huh.
That is weird.
See if using this app helps:
https://github.com/ukscone/set_overscan
Also, I found this thread:
How are you starting up ES? Via ssh? Does it start on boot on the Pi?
Weirdly (or interestingly), others have complained about the same in the past:
https://retropie.org.uk/forum/topic/82/overscan-issue
Did you per chance update RetroPie recently and the system as well?
Reading that thread, it seems that having double entries on the file may cause problems. Do you have any repeated entries there?
-
@darknior What if you uncomment overscan_scale=1 ?
EDIT: I read in a few places that this is what you may need. Please test. Raspi-config must have edited quite a few options when we used it, and now reversing them seems to be guesswork.
-
@pjft said in Please test: Random Game selection/launch via Video Screensaver:
How are you starting up ES? Via ssh? Does it start on boot on the Pi?
Did you per chance update RetroPie recently and the system as well?
Reading that thread, it seems that having double entries on the file may cause problems. Do you have any repeated entries there?- ES is starting alone after boot like on my video, i change nothing.
- I use the last Retropie version 4.2 and update it by Retropie-Setup
Last i update the last version of ES by source to test your code.
But i never have this problem before - I already verify this but no double entries.
-
@darknior can you set it up so you have the small loading screen, and add overlay scale = 1?
-
@pjft said in Please test: Random Game selection/launch via Video Screensaver:
scale
#disable_overscan=1 overscan_left=30 overscan_right=-10 overscan_top=5 overscan_bottom=5 overscan_scale=1
http://elinux.org/R-Pi_Troubleshooting#Big_black_borders_around_small_image_on_HD_monitors
This only affects the framebuffer (e.g. console or X). It doesn't affect hardware layers (like video/3D). You can make it apply to hardware layers with:
Woaw with the SCALE option you are real the screen is perfect :)
What is this option, i don't really understand the english notice ? :(Now all is perfect and the Video Glitch come back lol i can make the video tests for you :D
-
@darknior Whew.
More important than the tests, I'm happy that you have things back to where they were!
Please make a backup copy of that config.txt file, and sorry for this adventure. :)
I was reading the description of hdmi_boost on the config file:
# uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4
Now, if you do run into the issue, could you test it after uncommenting this and rebooting? Just curious if it'd have any effect.
Thanks.
-
@pjft said in Please test: Random Game selection/launch via Video Screensaver:
Say testing -z, -d, or -r and see if it changes anything.
--lines 1 is also an option.
--display <different number, 0 or 1 for instance>I use this line :
omxplayer --layer 10010 --no-osd --aspect-mode letterbox --subtitles test.srt '/home/pi/RetroPie/medias/gba/videos/Advance Guardian Heroes (USA).mp4'
- -z : Glitch
- -d: Glitch
- -r : Adjust framerate/resolution to video : NO Glitch but video no full screen
BUT crash ES ... Black screen ... ES is invisible but working behind ! - --line 1 : Number of lines in the subtitle buffer : NO Glitch -> I think the GOOD way for me !
- --display 0 / 1 : Glitch
--line 1 is the solution i think
I see some time a line or two of the glitch but it is really nothing.
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.