I gave up and just re-flashed Retropie. It's working fine again.

@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.

Thanks for the advice everyone. I will pick up a cheap keyboard after work. Hopefully that works. Otherwise I will just have to start from scratch.

@caver01 , thanks heaps mate, that did the trick and now it's all good!

@Maynard your question indicates that you didn't map the core specific button configs usinf the core input remapping method.

Reset the changes you made and remap using that method. I think it'll make you happy. ;-)

@9acca9
It could be that sixad isn't running. You could try this quickly to see if it fixes the problem.

From the wiki entry:
For bluetooth pairing to persist between reboots you need to make sure sixad is executed during startup. Exit EmulationStation and and edit rc.local.

shell
sudo nano /etc/rc.local
Add sixad --start & before the line exit 0 and save (ctrl-x then y)

I was able to get the one player button working by assigning it to the # 1. Rp3 and latest retropie build as of 4/30.

What is important is the information you should include in your post (pi version, where you got Retropie from, what version, etc.).

MAME is a complex subject. It is a project that has been in development for many years and the supported filesets are updated with each release. You cannot just take a MAME ROM and throw it at a random MAME emulator, it has to match the version of MAME that the emulator is based on. On Retropie there are a number of different MAME packages and each supports a different romset.

If you want to play a specific game, you need to get the ROM in the right version for the emulator (a list of romset versions for each emulator are in the wiki).

Something got corrupted during the install. I did a fresh install and it works fine.

Thanks, I will do a bit more experimenting.

I have a Pi 3 model B, I will see if I can recreate the issues on that, if I can then they must be related to the image format

@rbaker I have now removed that post too. (@dankcushions please do not give exact instructions on how to use google to download roms). I have noticed recently people are doing this more and more. I don't see much of a difference from providing a link to telling people how to search to get a link. Feels like people are trying to bend the rules without breaking them, and I am not ok with it.

@BuZz i had no idea about NodeBB or the app you linked , I've downloaded the app on to my Droid phone but have no idea how to use it he heh , i can with a search find your post saying we are using nodeBb at Retropie .
I'll have a search for tutorials for it .
Cheers

Thanks again.

As the text tag list doesn't contain something like outline

Available tags:
pos, size, text, color, fontPath, fontSize, alignment, forceUppercase, lineSpacing
Source: https://github.com/Aloshi/EmulationStation/blob/master/THEMES.md#text

you have to use a font with a outline. Just search for a folder called "art" in the root of the theme you want to edit and replace the old font with the new one.
If you don't want to mess around with the XML files, rename the new font like the original one was called.

That's it. If you need more help or a finished solution, tell me.

EDIT: If a change of the font color would fix your problem to you could edit the "main" XML (it isn't called main in most cases), located at root of the theme folder. Edit the color hash in the <color> tag

You can stop emulationstation by pressing F4 on a keyboard or quiting it in the Quit section of the Menu (start button)

You should definetely make a backup first!

The install steps are listed here:
https://github.com/biscuits99/rp-video-manager

Otherwise here are instructions for a manual installation:
http://smartretro.co.uk/forums/viewtopic.php?f=3&t=8288

Great, okay thanks. I just wasn't sure if the whole "update selected packages" selection would look for the latest ver locally.

Thanks for your help !