hdmi_safe will set the resolution to 640x480, if your monitor supports a higher resolution, you can set it by using hdmi_group=2 and hdmi_mode set to one of the values detailed in https://www.raspberrypi.org/documentation/configuration/config-txt/video.md. You'll probably have to add hdmi_ignore_edid=0xa5000080, my guess is that your monitor supplies a wrong EDID and the Pi tries to set the video resolution to an unsupported value.
@lilbud basically it’ll just continue to boot then next part of the os without waiting for a WiFi signal and will connect when it’s ready in the background . Without it, It’ll wait either for an connection or just timeout and then continue to boot. No need to to have a solid WiFi connection on a retro pie setup. Where you would want it is if your project requires internet or WiFi to run your project so it has WiFi before the whole OS boots.
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!
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.
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.
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.