@ectoone

very strange , would of thought by now it would of been implemented. Sometimes like with the current consoles...I wonder what year I'm in ! lol

@anassassinsblade that's just a video splash. They either disabled the ES splash or just changed it so it was a more seamless transition between the retropie boot splash and the ES splash. It's just a hack.

@SuperCatFooz at that point you may as well use lakka with the xmb interface

@steve51184 please use Google for your issue. Mac Windows and Linux use different "invisible" control characters to enter new lines in texts. Use Notepad++ for ex and you see the difference.

@jdrassa Thanks, it worked!

@TMNTturtlguy said in Best background option for system view/gamelist:

hat happens after 512kb? I didnt know the memory could exceed 256?

Then it will use 1024kb.

Extracted info about memory split on github: https://github.com/RetroPie/RetroPie-Setup/wiki/Memory-Split

"note that in order to ensure sensible memory splits across Pi models, RetroPie utilises the gpu_mem_256, gpu_mem_512 and gpu_mem_1024 overrides, which apply to Pis with that amount of memory (for example, the Pi 2 has 1024MB memory, so will use the gpu_mem_1024 setting). This setting overrides the gpu_mem setting"

In this topic you can find a lot of info: https://retropie.org.uk/forum/topic/2389/solution-for-white-screen-of-death/12

Keep in mind this info it's before white screen fix was released:

@Rookervik said in Solution for " White Screen of Death ":

@edmaul69

There's a minimum amount of VRAM required to display certain size wallpapers. If you have just 1, 1920x0180 wallpaper, you MUST have 256 meg RAM split. But that 256 RAM split will take you up to 10 or so wallpapers. The next jump is probably 512 split. Which should still be just fine with most of the emulators that the Pi can handle.

You can make sure your theme wallpapers are 720p and that will help you with the RAM issues. ES was not designed for the Pi, but it works.

The Carbon theme was designed for the Pi's limited video RAM just for the white screen problems. If you're going to make some custom themes, try thinking in 'parts' instead of 'wallpapers.' Several 512x512 images take less VRAM than a 1920x1080 wallpaper. Try to re-use elements so ES doesn't have to fill VRAM with a massive picture.

@Rookervik said in Solution for " White Screen of Death ":

@edmaul69

That is very strange. A 10x10 pixel image will take the VRAM of a 16x16 image. Everything unwraps to a power of 2. As long as these images are not SVGs. An SVG stretched to full screen takes a canvas to display, and that canvas takes the full VRAM of that area. So even if the SVG has a single line in it, and the file size is 0.5kb, it will take the same VRAM as a 1080p PNG uncompressed. Fonts shouldn't take too much RAM, and they are regular RAM.

@TMNTturtlguy and for this last thing it's because I told you don't use so many svg files... Rpi can handle pngs very well, I only use svg for system logo, you have 3 svg on each system folder.
But we still can read a bit more of interesting info:

@Rookervik said in Solution for " White Screen of Death ":

Also, keep in mind that the RAM splits should stay in powers of 2. Just like any images you use in the theme. 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096... Your 1x343 image uses the same RAM a 512x512 image would take, as does the 350x350 image. They all unfold to a power of 2 in VRAM.

I hope this helps to understand things a bit better.

@TMNTturtlguy

When using riot, if just adjust the slider you can see the final size before saving on top of right image, where you can read "optimized image". That's what I do.

Regards.

@Stuart2773 That's what I said.

@synack If you have a solution that would be amazing!

@najkks: EmulationStation has 3 main views: System, Basic and Detailed.

System view is the first view with the white carousel that displays the game system logos. Basic view is the simple GameList view that you get before you scrape any roms. Detailed view is the one that displays all of a games metadata (image, description, playcount, genre, developer, last played, number of players, publisher) that you get once you have scraped your roms.

When a person makes a theme they can specify a different background image for each system (eg: NES can have a picture of Mario, Genesis can have a picture of Sonic), and each View can have a different background image (eg: NES System view can have a picture of Mario jumping, NES Basic view can have a picture of Mario throwing a fireball and NES Detailed view can have a picture of invincible Mario).

However, what you can't have is a different background picture for each game in the GameList (eg: NES Mario Bros. with a picture of Mario, NES Battletoads with a picture of Zitz).

You also have to take into account how much RAM all these images are using. The original Simple theme used large background images for each system like this:
EmulationStation

While using this theme, a person could only have about 10 different systems before it was too much for the Pi and the whole thing would whitescreen.

So, while you can have a different image for each system, and a different image for each view, you need to do a lot of testing to make sure your theme isn't too much for the Pi to handle.

That is why most themes just use a simple repeating pattern (like Carbon) or a simple image with a colour overlay (like Pixel).

Now, having said all of that, if you personally only use a handful of systems (eg: NES, SNES, Genesis, MAME and PSX) then there shouldn't be any problem using a different image for each system. If you want to know how to do this for yourself, there is a How-To in the wiki that you can use to either make your own theme, or just modify an existing one.