Theme problem
-
@tmntturtlguy hmmm I think the themes are updated as well because I updated all installed packages a day ago. Also, the themes I'm using are Comic book (yours) :) , and the new magazine theme (can't remember the exact name). When I switch to the magazine theme is when it starts with these errors. Also does it with the comicbook wheelart theme.
-
@giga I think you need to update themes independent of all packages. Try that and see if it works.
-
@tmntturtlguy Ok I'll give it a shot tomorrow. Thanks for the replies.
-
I had this exact thing happen when I was playing around with the VRAM setting. I believe I had cranked the VRAM limit up to 200 (may have been less). Really messed things up.
Change the VRAM limit to 80. Advice from @pjft that has solved some of my ES issues. -
@giga said in Theme problem:
And if I go to console I see a bunch of errors:
glGetError 0x505
glGetError 0x505
I have the same problem on a different RPI3/SD card that has the same image on it.
Everything installed is updated to the current versions.
I have to restart ES to fix the problem.
Does anyone know what the problem is, and if I can fix it? Any help would be appreciated, thanks.Correct. I've seen mentions of this font corruption in the past, definitely related to bad memory allocation.
EDIT: https://retropie.org.uk/forum/topic/4014/weird-font-issue and others which I'm not finding right now.
Lowering VRAM may help, but in previous occasions there was also a case of a wrong memory split in /boot/config.txt .
Did you change the VRAM setting on your Pi? Did you change the memory split on your Pi?
What image are you using - as you mention "the same image" but don't give us any more details to work with. You might just have a wrong image.
-
@pjft Hey, thanks for the reply.
The only thing I've change in the /boot/config.txt file is this overclock:
arm_freq=1300
gpu_freq=500
core_freq=500
sdram_freq=500
sdram_schmoo=0x02000020
over_voltage=2
sdram_over_voltage=2Using a FLIRC case and haven't had any overheating or anything.
But I've tried it with no overclock, and I still get the white screens and font corruption.My VRAM LIMIT in ES is set to 170Mb (I think that's default, but I have played around with it before).
The image is a 21GB image on a 32GB SD with 12 systems that I made by adding the roms/boxart/videos.
-
@giga The default is 100MB, so 170 is setting yourself up for failure :)
Make it 100 or even 80 and see if it fixes things. If not, send over the rest of your boot/config.txt file over PasteBin or equivalent.
-
@pjft Changed it to 80 and it's running a lot better. No issues yet. Not sure why I thought 170 was the default.
On a side note, should I turn "USE OMX PLAYER (HW ACCELERATED)" on or off? -
@giga It's up to you, and up to the theme and videos you have.
I use it "on" as it performs a lot better on the Pi than the standard VLC player, and doesn't lead to overheating.
However, it doesn't support layering things on top of it, and it may not play some video formats or encodings.
I recommend trying it out. If you use the video screensaver, it's the same player that is used for it, so if it works well for you, you're probably good to go.
Worst case scenario, if some videos don't play, I'd personally re-encode them with Handbrake or something so you can use OMX Player.
-
@pjft Awesome, thanks for all the help.
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.