The OP said " setup the same direct launch for Moonlight and Steam Link." How is that the same thing? I was thinking you'd need ES to display a "system" called "Moonlight" and then have one "game" that automatically ran when it was listed. Now that I think about it, my idea probably wouldn't work without a second button press in current ES. ....unless you could list the app as "system" in ES and symlink "the directory" to a file that launched the desired app. I'm not sure about the limitations of symlinks in Linux though.

@BuZz thank you!!! really appreciate the help.

That's it, thanks.

@Lolonois said in ES Screensaver UX "puzzles" and suggestions: I like to talk to humans first. However, the commit with the if (input.value != 0) and the else dates back to 2016-06-25 and was made by Aloshi in a major refactoring/file move. So I guess this is of no use. I expected this to happen. I asked you to check git blame cos I dont remember who changed that code last and it they are still active on the forums. and if other devs welcome the feature. As in if any other dev is willing to work on the Feature. We do need someone to work on it for the initial implementation. No gate keeping there. If you are interested to work on it, that would be great too. Suggestion 2: not decided yet, @Hex do you have a opinion here? Actually I dont have any opinion on this. My priority is to make PowerSaver feature work as expected. UX change is not an issue as I am more of an Infra dev o this project. I think that decision should come from core devs responsible for UI/UX. I suggested you create a poll so we can get feedback from actual users and not just the subset of users frequenting the Ideas and Development section.

OK.. I fixed the issue, but this is a little odd. Apparently, Controller 1 (Player 1) has to be in USB1 on these 3040's, Controller 2 (Player 2) in USB2, etc, etc. Is this a unique situation for the 3040 or is this a universally known fact in RetroPie land? If it is, then I apologize for not doing more research. This may just me being a little more Windows oriented than Linux oriented, but does it really matter which slot the controllers are plugged into? I'd think that the programming of the controllers would follow the unique ID and not care about the USB Slot at all. Thoughts?

@mitu Thanks for the advice. I ended up re-installing on both cards. It worked just fine, set up the controllers, then tried to get back into ES, but the errors started again. Re-installed image again and worked fine, so far. So it's up and running, but not perfect. Thanks for your help!

To me is looks like the gamepad is not correctly detected and configured by the OS - so no amount of configuration will make this work if the kernel doesn't properly detect it. Hence the suggestion to try and see if you have the same issues with an older build.

@Ecks Ok, but is there any way to do this on emulationstation?

@Bluebotlabs I know what your original post was asking. If you want mouse support right NOW, you can use the pegasus frontend as an alternative. It uses emulationstation's scraped art/gamelist info except for logos/marquees.

@Hooded-Man said in Can't boot Emulationstation get a error from booting: Built from: Premade SD Card from Ebay got arcade machine. Link is right here: https://www.ebay.com/itm/224001822340 We don't support 3rd party images, especially the ones sold with ROMs and RetroPie. Ask the seller for support, we don't support scammers that sell RetroPie preloaded - it's against the project's license.

@bmoxey Having issues with GitHub. Says file is too big. Looking into at the moment. Rgds CCFox

@rayvearn always better out that in specially when you stuck with this lockdown!

@brand dude don't count yourself short so quickly. If you can setup Retropie you can edit a XML file and what not. Check out the docs on making your own theme. Reading the docs is always the first step. Also I would recommend a text editor that has syntax highlighting, like VS Code or Sublime Text. The highlighting makes reading the file much easier. One more thing to check out are the GitHub tutorials. Source control is super helpful is you make a mistake you can just go back to a previous version. Remember knowing is half the battle.

@mitu said in How can I point Emulation Station video clip references to where the clips are stored (and used by Attract Mode)?: Actually there is a configuration to make EmulationStation look automatically for media (video/boxart/marquee) - it's called 'Enable Local Art', in the Other settings. When enabled, EmulationStation it will look for images/<game>-image.png, images/<game>-video.mp4 and images/<game>-marquee.png (.jpg work also) and use the found media instead of looking in the gamelist.xml. Nice one mitu, this will save me quite a bit of time, as I am spending a lot more time on the retropie, than before, due to lockdown and furlouh. Sorry Vegasdude, didn't realise you knew about the paths and that, I probably read too much in your question. Never mind Mitu has given us both a good solution :-)

@mitu Thank you for the pointers :)

@mitu said in If I set "parse XML gamelist only " to "ON" Emulationstation doesn't start: emulationstation --debug Thanks! I found the error, but I think I will put that option back to "OFF" anyway because I noticed that now the lists have doubled some roms.

All Another update... Scraped quite a few systems and things are going well. Just a quick note tho... PSX ROMS that are in .chd format will not scrape for me however .pbp will. You can use a program called CHDMAN which will convert the .chd file back to .bin/.cue files. There is a good tutorial on YouTube. Once you have scraped them as .cue files then use Notepad++ to change the .cue extension with .chd with the find & replace all command by pressing CTRL-F. Works a charm. KR CCF

@DarkGlobe said in kodi - Retropie 4.6 - Raspberry Pi 4B: Could this issue be fixed by making customisations to the /etc/emulationstation/es_systems.cfg directly rather than creating a copy or would that put the customisations at risk of being overwritten & lost? The system file (in /etc) is maintained by the RetroPie-Setup script, so it might get changed by an update, so it shouldn't be used for custom systems.