The question I would ask myself in your place is if I'd rather do without or rewrite my scripts than trying to adapt many unfamiliar scripts that may break again with the next update.

@Agustinb14 said in Controls don't work in retroarch or in console games: I can't seem to be able to bind 2 different hotkey keys for my controls but that's ok. At least I can play now. Only Player1 is able to access the hotkeys' functions - P2 cannot control them (including opening the menu). Glad you got it working in the end.

@Efriim yes that is where it goes. You change the line to: emulationstation --no-splash #auto

@mitu Which folder can I find the code to edit? Would you please describe it in detail? Thanks! @mitu said in How to modify the description of EmulationStation?: @Leonard-Lin You'll have to edit the code and change it, then recompile.

@mitu @BuZz @Efriim I finally got it working! :D local bin_file local bin_files local default local id local index local version ... some other code ... for index in "${!bin_files[@]}"; do default=0 [[ "$index" -eq "${#bin_files[@]}-1" ]] && default=1 # Default to the last item in 'bin_files'. version="${bin_files[$index]}" version="$(echo $version | cut -d'_' -f 2)" addEmulator "$default" "$md_id-$version-$id" "godot-engine" "$md_inst/${bin_files[$index]} --main-pack %ROM%" done So it seems like the error had something to do with the index variable (previously it was named i). Either it needed to be initialized as a local variable or the script didn't like that it was called i... I really don't know. But I got it working :) Another thing that I found and maybe it's worth mentioning (and correct me if I'm wrong) is that when I run: sudo ./retropie_packages.sh godot-engine configure the config file: /opt/retropie/configs/godot-engine/emulators.cfg seems to just add the new stuff on top of the previous configs that were already there. I mean, it doesn't delete the file and creates it again with the new configs. Shouldn't "deleting the old file and creating a new one" be the "correct" thing to do? Thanks! :)

@johny8 How did you determine that ? You claim is rather ridiculous. 'Sabotage' ?

@alkah3st which premade image are you using?

@maplestory Correct. It doesn't matter. Those lines relate to the extra folders - nvram, etc. Thanks for reporting! Hope you're having fun.

@Hex Thanks for the info!

@m0h most joypad extractions are handled through retropad with retroarch, I know they had some plans at some point to make the retropad more visual but I don't now where they are at with it.

All set! Thanks again!

@jdrassa said in Request: Option To Disable Carousel in ES UI Options: FYI, Someone submitted something similar to this previously that was rejected. https://github.com/RetroPie/EmulationStation/pull/85 It looks to be rejected mainly based on how rudimentary the request was that was submitted. The guy who originally submitted this push did so by simply making a flag that disabled the back button in ES, which is too simple of an implementation for buzz, he wrote that he wanted to make sure it was a better coded function. @Hex, i promise I'll get to the next step soon, perhaps tonight if i get a lull, hahaha! Too many adult, work and parenting responsibilities come first. Damn these 30's.

@dmmarti awesome thanks man!!

@jdrassa This method seems to work great if the UI modes are not in use but if it's set into Kiosk mode the es_settings.cfg reverts to an unmodified state after reboot. Does enabling the Kiosk mode overwrite the es_settings.cfg file? If so can I modify the Kiosk mode to include the splash screen setting?

Hi @Capeman! I'd like to resume your work. What do you think? Can I start from your semifinished piece? Can you share the partial theme package? thank you so much

@jdrassa I just encountered a big flaw while using ${system.theme} in an <include> tag. If it can't find the specific file, e.g. if someone uses an custom collection, it breaks the whole theme for that selection. All theme settings are suddenly ignored. I had the idea to create some sort of external metadata library for systems that could be simply used by theme makers just by including a single file which further imports the metadata from ${system.theme}.xml files and also provides labels. It also imports a file which is used to theme those text elements. I integrated that into my Flatline Theme here for testing purposes and noticed that behaviour. To make the process clear again: theme.xml includes _assets/mds_include.xml mds_include.xml includes mds_data/${system.theme}.xml and mds_style.xml It would be great if you could take a look at it and tell me if I made something wrong or if that is unavoidable for now. I mean I know that ES will fall back to the default theme if it can't find an include file. Maybe there's an way to ignore that error. Edit: I just had another idea, would it be possible that ${system.theme} returns default if an unknown system is selected? Then we could use files like default.jpg or default.xml.