@mitu Ah thanks for the advice. Turns out I only have the Pi3 so even if I could somehow set up the thing to recognise I had a Saturn emulator on it, it's like you said it more than likely wouldn't run very well or even at all. And to think I spent all afternoon browsing the thing's files to try and find a backdoor. Oh well. Sticking to pre 1995 consoles for now it seems.

@sleve_mcdichael

Thank you! That did it.

@zombie_ryushu said in Issues with local Screenshots and Migration:

AARM and Skraper appear to be Windows Specific Applications

Yes, but that doesn't mean they can't run on Linux. For Linux, you can try Skyscraper, has a lot more flexibility than the built-in EmulationStation scraper.

The font in the message blurb is not set by theme, it's the default EmulationStation font - the size is not configurable.
It would be nice if the size would be bumped on smaller resolutions, could be a nice addition.

@snapouille, have you found SVG files for all of the other controllers? Would you mind sharing where you got them? I can look at those and possibly create some SVG files for these that you are looking for...

I am currently rebuilding / verifying new images.

@theotherdan

Thank you. This was caused by the environment though. I was booting into PIXEL desktop before launching EmulationStation. This configuration prevents quite a few things to function as expected.

@nohitter151 There is also a different way. ES has script callouts for some events: https://retropie.org.uk/docs/EmulationStation/#scripting

Put your scripts in your favorite language in the respective folder. Make them executable (chmod a+x <script>) and you should be ready to go. With the values of %rom_path% %rom_name% (first and second parameter inputted to your script you can locate the respective entry in the gamelist.xml which leads you to the artwork.

PS: Welcome to this forum :)

Press "OK" and type reboot when the command line opens at the bottom. Worked for me.

@shotokan the script maps the gamepad inputs to keyboard codes. The inputs used are ['left', 'right', 'up', 'down', 'a', 'b', 'x', 'y', 'pageup', 'pagedown'] and are mapped to the codes given as parameters.
So left= kcub1, right= kcuf1, etc.
The parameter codes are given as terminfo values, listed in https://pubs.opengroup.org/onlinepubs/7908799/xcurses/terminfo.html.

@deguzler said in NES Roms not loading:

[libretro WARN] Not an iNES file!
[libretro INFO] FCEU_MakeFName: /home/pi/RetroPie/BIOS/disksys.rom
[libretro WARN] FDS BIOS ROM image missing!
[libretro WARN] An error occurred while loading the file.

It doesn't detect your rom file as a nes file, so it thinks it might be a fds file, for which you are missing the bios (it's not a fds game anyway, 10 yard fight was not released on fds). Your rom is probably corrupt, but if you are confident it's not then you can always try it with another nes emulator (nestopia or mesen are probably way better choices on a pi4 anyway since they are more accurate and pi4 should be able to handle them).

@kelvinator3300 I found this but the links are broken. This is exactly what we want. We should definitely look into this amazing tool!

https://opium2k.tumblr.com/retroarch-readers

@mitu said in TI99 Scraping problem:

It looks like ti99 is not a supported platform for the EmulationStation's scraper. It needs to be added in order for the scraping to work - so for now you can use Skyscraper or another external scraper for the TI99.

Thank you very much. This worked perfectly.

Just add your scripts to the retropie menu, very simple. i never had to make any edits to make it work, just some editing to get the script to have a picture in EmulationStation and description of the script.

If you want the scripts to appear within your Ports, you might need to include .sh with the filetypes that are supported with Ports even though from memory it should already be set up like that (i cant double checking this right now, currently making a backup of my SSD)

If you can see the scripts in EmulationStation but theyre just not executing after selecting them, then you will need to chmod +x your sh files.

I'm experiencing the same thing as OP and the "fix" from the other thread didn't work.

From the "read first", my answers:

read forum rules ✅ search the docs ✅ search the forum ✅ I found two, the one OP reference and this one; like OP, trying the change outlined in the other post did not work raspberry pi power supply ✅ I've got an official power supply for my pi 4 official image ✅ I flashed the base retropie image and the experience has been otherwise quite smoth

EmulationStation uses libSDL's joystick subsystem to recognize and work with joystick devices, maybe your device is not detected by libSDL as a gamepad/joystick.
In addition to jstest/evtest, install jstest-sdl2 (from https://github.com/Grumbel/sdl-jstest) and see if your device is working with it.

@mitu ahh ok, perfect, I'll give that a try today and hopefully that will work around the permissions.
Thanks again 😊

This diff should do the trick, clearing also any keyboard type controllers

diff --git a/es-app/src/main.cpp b/es-app/src/main.cpp index 26faeb2..26bc328 100644 --- a/es-app/src/main.cpp +++ b/es-app/src/main.cpp @@ -320,6 +320,9 @@ int main(int argc, char* argv[]) bool splashScreen = Settings::getInstance()->getBool("SplashScreen"); bool splashScreenProgress = Settings::getInstance()->getBool("SplashScreenProgress"); + //dont generate joystick events while we're loading (hopefully fixes "automatically started emulator" bug) + SDL_JoystickEventState(SDL_DISABLE); + if(!scrape_cmdline) { if(!window.init()) @@ -365,9 +368,6 @@ int main(int argc, char* argv[]) return run_scraper_cmdline(); } - //dont generate joystick events while we're loading (hopefully fixes "automatically started emulator" bug) - SDL_JoystickEventState(SDL_DISABLE); - // preload what we can right away instead of waiting for the user to select it // this makes for no delays when accessing content, but a longer startup time ViewController::get()->preload(); @@ -386,7 +386,10 @@ int main(int argc, char* argv[]) } } - //generate joystick events since we're done loading + //generate joystick events since we're done loading and clear the input event queue + SDL_PumpEvents(); + SDL_FlushEvent(SDL_KEYDOWN); + SDL_FlushEvent(SDL_KEYUP); SDL_JoystickEventState(SDL_ENABLE); int lastTime = SDL_GetTicks();

I don't think it's 100% correct, since any errors during startup would leave the joystick disabled, further testing is needed.

@bberlin1 said in Help! Won't boot Emulationstation!:

I'm still curious however-- if you have any insight into how to a) edit files from an ssh gui or b) access putty with my pi login, I would be very interested. I can only seem to do these things via the root login and would like to not have to run into these kinds of issues again.

If you use Putty, you can edit the files via nano. Most of the configuration files are also available via file shares (under \\retropie\configs), so you can use a decent text editor from your PC (Notepad++/TextEdit) to edit the files. None of them require the usage of the root account for editing.