Just as I posted this I managed to figure it out. It seams that when kodi in osmc starts a script it starts it in root directory where it has no privilages. Adding "cd /home/osmc" at the beginning of "/home/osmc/RetroPie/scripts/retropie.sh" solved the problem!

Awesome. I will check out that link. Thank you.

Hi all! I just wanted to say that I got an answer to my issue! My particular problem was due to my using a VGA to HDMI converter to use with my old VGA monitor. What fixed my problem was to edit the config.txt file and uncomment the line "hdmi_force_unplug=1". Works perfectly now. Again, thank you all for your time.

@mitu Thanks, that fixed it! Also, for anyone else who ends up here, it's important that you run raspi-config as sudo raspi-config from the pi user. If you're already root and you run it it won't know which user to configure for autologin.

someone asked about this on reddit a few weeks back, and i told them to add it to: /opt/retropie/configs/all/autostart.sh expressvpn connect & emulationstation it seemed to work for them. here's the thread for reference.

@mitu I made it! I have deleted whole scummvm folder, rebooted and the ES finallt works! Thank you everyone. The problem is officially solved.

@ericdave you should not edit that file but the autostart.sh. the file you edited is not meant to be user editable and will be overwritten.

I solved it! https://retropie.org.uk/forum/topic/4057/can-t-remove-text-in-bootscreen/14 Add "clear" as the first line in /opt/retropie/configs/all/autostart.sh. Never seen that tip anywhere other than that thread, but it worked!

@mitu I don’t have a usb keyboard I can use, I have been using VNC and my laptop to set up RetroPie.

Thanks both. Have added a 5 second delay, and it works now. Will look at adding a powered hub.

Ok... I think I know what's happening, and If I'm correct I'm a completly dumbass xD It seems that key taps are recognized and considered even in loading screen. With gamepad in hand (xbox 360), I usually tap A button repeatedly (an impatient one here...). It happens that the first emu in menu is the amiga one, and the first entry in Amiga's rooms is UAE4ALL, so, that's it. It's my "A" taps in loading screen that launch uae4all when screen becomes operative. Yep... totally dumbass xD Anyway, if I'm not a dumbass after all and the issue happens again (without "A" tapping :-P ) I'll let you know. Thanks and regards!

@AndersHP Yeah, since ES loads the artwork on the fly, the access speed is relevant for the user experience. Apart from slow USB drives, network drives are another bottleneck that can be avoided by putting the artwork on the internal SD.

Well I got it working :-) I have created a repo on git incase anyone else needs to do this: https://github.com/bruceiow/rPiVolumeControl

@Br4veSirR0bin these are nice!

@djjujuvi use etcher, it's simpler and doesn't require unzipping.

@eliteanorak Good luck!

@dhtsicmdnstej wiki is editable by anyone ;) Glad you got it sorted

Probably due to the way you are launching ES. Use the autostart feature from retropie-setup configuration to make it start automatically and it will work fine. It has to be launched attached to a terminal.

Hi @hhandsmt That sounds like normal behaviour. When you complete the setup, there are no other systems visible until you upload roms for the games to your Pi.