The script code for detection can look like this if (/usr/bin/tvservice -s | /bin/egrep '4:3') ; then sudo cp -f /etc/splashscreen.list.monitor /etc/splashscreen.list else sudo cp -f /etc/splashscreen.list.tv /etc/splashscreen.list fi which you can use at the beginning of the splashscreen script. Have 2 files with different video paths /etc/splashscreen.list.monitor - containing the full path to the video you'd like to show on your 4:3 monitor /etc/splashscreen.list.tv - containing the full path to the video that will be shown otherwise (on TV). Note that the splashscreen script will be overwritten on upgrades, so make a backup of your script after you get it working.

Did you notice if you turned force_turbo off? I think you would have stated if you were using a usb. I haven't used romsets, I don't know how everything handles a huge job, but you say it was rather suddenly that you noticed and not after you add roms. If you use ssh, you could login and type htop to display the processes to see if there is something slowing down.

@furtin As long as you use Emulators beginning with „lr“ (for libretro), you can use the hotkeys from RetroArch for loading, saving, and choosing the save slot. See https://retropie.org.uk/docs/RetroArch-Configuration/#hotkeys

@mitu Yes. I accidentally disabled it. Re-enabling it fixed it all. Thank you so much :)

@etownAndy What has changed was the ES version - which was bumped recently. And while it may have worked for you with 64 RAM in the past (I don't know how) - this was never something that was tested or recommended, see https://retropie.org.uk/docs/Memory-Split/. You didn't mention what Raspberry Pi model you have - are you using a Pi 1/0 ?

@camjrp Those errors seem related to your Xorg installation or desktop environment.

@camjrp You need to install it first, then follow the documentation on how to configure your es_systems.cfg so that it starts RetroArch with the right cores on the SNES/PSX games. As an example, RetroPie uses something like retroarch -L <PATH_TO_CORES>/snes9x_libretro.so %ROM%" to start RetroArch with the right Libretro core for the SNES system.

ah.. saw the news on the main page here, thanks Buzz. Mitu - I tried what you suggested, and it worked, only now it's also asking for VLC, and the latest image won't install properly using the manual method. BUT, forcing the rapidjson-dev to install, and then going to re-install the emulator (not the dev) hung up on VLC, so I finally figured out which VLC to install, and everything worked. Thanks for the tips.

@rubberdinghy You'll need to ask the seller to provide the Raspberry Pi version - https://www.lexaloffle.com/pico-8.php?#getpico8 - and then follow the instruction on their site to add a new system in Emulationstation.

@dudleydes woohoo, THANK YOU!

@mitu LOL Wiseass. :) Yeah I did use Selph's scraper. I like the videos. I did check that es_systems.cfg file before I posted just to make sure. Love the search function for problems. Had MANY I didn't have to post for because it's already on here... usually with your name on it. :) EDIT: Yep. my gamelist.xml file has a bin and a cue entry. Shaved out everything that said WWF and it only shows one in ES now. I just re-scraped that one game. Thanks. :)

@littlehui said in emulationstation can not lauche: lima driver only support opengl es. Is this the problem? No, actually is the other way around - Emulationstation needs OpenGL ES for your system to work, but it relies on SDL2 to offer that. If your SDL2 library is not compiled with OpenGL ES support, then it won't work. The RetroPie-Setup script takes care of compiling or installing such SDL2 version (for Raspberry PI at least), I'm not sure your system provided SDL2 library has GL ES support and - also important - accelerated GLES support from the Lima driver.

@robertvb83 said in Screensaver shows hidden games and freezes emulationstation: but still I am interested about that fix... That fix would apply only to @scocasso's case (where he had empty video tags), in your case the behavior would be the same - the screensaver would read the video path, check the video existance, not find it, then go to the next - a few tens/hundred times until it will give up or actually find a valid video file.

Hey! A bit late haha So... I don't know much of cmake, but I ALWAYS like to start by the official website and documentation. I found an official tutorial on the official website: https://cmake.org/cmake-tutorial/ Not the BEST answer but I hope it helps... Cya!

Version 2.7.6 I have an image all set up for my RPi, but I recently got an odroid XU4 and am looking at porting as much custom esthetic as possible. I do see that the RetroPie branch does not have the converted .cpp folder. Honestly this whole project for me is about learning how these systems work. Thank you again for your quick response :)

Nevermind, figured it out all on my own. :) It was a literal issue. When I looked at the files directly, the ones I was having this issue with all had filesizes of 1k lol. I replaced them and everything's working again. Thanks anyway for looking!