@Clyde said in Create script to copy and overwrite romlist files in attract mode: Yes, this should copy all files in /home/pi/.attract/backup to /home/pi/.attract/romlists. Beware that this wouldn't copy any subdirectories in backup, for those you'd need the -R option for recursive copying: cp -R /home/pi/.attract/backup/* /home/pi/.attract/romlists/ But if there are only files in backup the -R option isn't needed. To make a script out of this, just put this in a text file. It is common to begin a Linux shell script with the shebang which defines the interpreter that should be used to run the script. Without the shebang, the shell will use its standard interpreter that, depending on the script, may cause problems if it handles some commands differently. RetroPie's standard interpreter is the bash, located in /bin. Although this shouldn't be an issue with your simple script, let's give it a shebang for sheer sake of completeness: #!/bin/bash cp /home/pi/.attract/backup/* /home/pi/.attract/romlists/ Put this into a text file (e.g. sometextfile) and make it executable with this command: chmod u+x sometextfile u+x means give the file's user (i.e. owner) execute permissions. Pro tip: If you put this file into a (new) directory /home/pi/bin, it will be found by the shell from any other directory. Otherwise you'd need to invoke it with its full or relative path. If it's in bin in the home directory of the current user, you can run it from anywhere just by its name in the command console. As for accessing the script from the Settings section of retropie, I will have to look that up myself since I don't know that off the cuff, but I have to go to work now, so I have to put you off for later. But maybe someone else can take over this part. Great info... I followed your steps and it works like a charm. I created file in notepadd++ - restore.romlists #!/bin/bash echo "" echo "Restoring Romlists..." echo "" sleep 5 cp /home/pi/.attract/backup/* /home/pi/.attract/romlists/ Put the file into /home/pi/RetroPie/retropiemenu chmod u+x the file Added the entry in the romlist file retropie.txt (attractmode) Created a wheel for it.. all good to go. Thanks for the help!

@XEntombmentX Make sure you understand what that entails - you'll have to maintain the custom configuration manually. Each time a new system is added (you install a new emulator) you'll have to manually copy the new system entries from the system config to the custom one.

@mitu Thanks! Definitely gives me something to work with. I will try with something that was easier to build and would have a higher level of interest for Retropie users such as Astromenace or Valyria Tear.

reason the png looks like that is because i made to fit into my updated theme.

ok i understand thank you ;)

I did get my .mp3 files to play inside the music folder. I am happy that .mp4s work as well. I could have sworn that one of the read me files said that you could also place these inside a video folder so that they will play randomly like the .mp3s. If this isn't the case, hopefully that option will be included in a future build. I have to say that these new options (grid view, video view, basic view) have been implemented nicely. The presentation of the themes looks more vibrant too :-).

Press Start to open the Emulationstation menu, then use the Input Configuration entry to re-configure your controller.

@kok00 don't know anything about the script but for the record there are some non working parents that are required to make clones work so if you delete them they may break more games depending on the type of rom set you have.

MODERATION NOTE: I merged the 2 topics you opened. If you find your posts flagged as spam, try removing the code blocks first when posting.

@mitu said in How does one make a script module for an emulator / branch: @HoJo215 said in How does one make a script module for an emulator / branch: DRI3 was the problem. Isn't this a runtime settings for your X.org configuration ? Actually I think it's part of the graphics or at least shader profile being used in mesa. I have padoka's bleeding edge repository in use.. Otherwise known as unstable. So things can go awry.. Like they did until I took a gander at the Makefile, saw some unused options, put 1 + 1 together and made some edits.. It worked a out beautifully. Especially on the Flycast-Wince emu with the same Makefile edits. I'm playing Sega Rally 2 on 2x internal resolution, 2x br and a 4x pass xbr shaders without one hiccup. Keep in mind this my first run with retropie x86. I decided to make small form factor emu box a month or so ago and gripped up a coffee lake NUC to guinea pig with. So everything is trial & error as I run with it.

@bleckman Look at how the Ports scripts are created - for instance Kodi - and you can replicate it to start the media player. Install Kodi, look at the kodi.sh script that it creates in the ports folder, and copy it and replace the Kodi start sequence with the command to start the program - from the author's instructions.

This discussion shows why options are preferable to suit the many different tastes, but they do require more effort in development. Thus the invitation to help creating the features requested. As a long-time Linux user who uses GUIs as naturally as the command line, I understand both sides. A pretty design doesn't contradict functionality per se, but in reality it tends to reduce the available options, since they have to fit into the design. And prettiness lies in the eye of the beholder anyhow. I often compare software design to cars: everyday controls are best placed on the dashboard, the rest goes under the hood. There will always be exceptions that depend on personal preferences rather than functionality, but even among car enthusiasts only a select few care about the visual design of the engine compartment. :) But I think we shouldn't shun the ones who do.

@dudleydes yes I tried that as well. UPDATE: everything is working perfect now. the trick was updating the binaries. :) Geez I should have started with that a week ago haha. -thread closed-

I figured out the issue. Problem was I got an error when I followed MSL's instructions to the letter. First time I got an error saying something like "this can not be a service", second time it said "Failed to execute operation: Bad Message". I mistyped. The script: [Unit] Description=RemotePi Board Shutdown Service Before=multi-user.target Conflicts=shutdown.target [Service] ExecStart=/bin/true ExecStop=/etc/shutdown.sh Type=oneshot RemainAfterExit=yes [Install] WantedBy=multi-user.target I had "Service" on a line by itself. Doh! It's fixed now, powering on off works perfectly now. Hooray!

@SuperMagicom said in switch between Emulation Station & Attract Mode: There are scripts for this in the Motion Blue base image. thanks for the help, are these scripts available without having to download the Motion Blue image? if so where can i get them?