Here's a couple more.

Dave Gnukem

wget https://raw.githubusercontent.com/Exarkuniv/Dave-Gnukem-RPI/Master/gnukem.sh -P $HOME/RetroPie-Setup/scriptmodules/ports/

GL version of Hexen2 for Pi4

wget https://raw.githubusercontent.com/Exarkuniv/Hexen2-GL-RPi/Master/hexen2.sh -P $HOME/RetroPie-Setup/scriptmodules/ports/

Hheretic for the Pi4 GL version (i think)

wget https://raw.githubusercontent.com/Exarkuniv/Hheretic-RPi/Master/hheretic.sh -P $HOME/RetroPie-Setup/scriptmodules/ports/

Hhexen port GL version ( i think )

wget https://raw.githubusercontent.com/Exarkuniv/Hhexen-RPi/Master/hhexen.sh -P $HOME/RetroPie-Setup/scriptmodules/ports/

@mitu

Ok I see.
So, EmulationStation and its emulator cores use ALSA and not PulseAudio so I shouldn't be doing anything with PulseAudio to get the switching to Bluetooth output.

I should just focus on getting ALSA to work with my Bluetooth headphones.

@mitu since I copied the script contents into a working script file after clearing the previous contents, I have no non working scripts now. I have to recreate this issue to even be able to upload a script. I'll work on it this week and upload it the scripts.

UPDATE

well still dont have it working. but i have tried different ways to have the game ran and compiled and so for it all ends the same. The system just sitting at either the runcommnd window or black screen.

it depends on how the game is ran.

i name shell to lunch the game directly. so it was not running with runcommand. it just ends at a black screen.
i even compiled with opengl turned off. same thing.

so i think something it the code for the port it self does not like ES and its not restarting.
bummer since it work just fine with my Pi3

@mitu Thanks, I'll try that. As for the script. It needs to be run to start the lightgun service to get the lightgun working. Only needs to be run once though. I think this is just a work around at the moment. Hopefully, once the sinden lightgun gets established, it will be integrated better with retropie.

@cnoto I'm glad you have found a use for it. I had no idea it would help with the pi zero's performance, but I'm happy it does! Thanks for letting me know about it. I thought having an airplane-mode was a crucial feature that was just missing an option in EmulationStation.

@mitu I'm having this same issue.

I've ran sudo ufw disable to disable my linux firewall.

I'm thinking that the issue is with my OPNSENSE router.

Which ports should I forward to my retropie server?

@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.

Doesn't sound very positive.

Don't listen to naysayers. If your script works, then it's fine.

Hopefully your advice won't make it worse then.

You should be able to use a single emulator entry instead of passing the video res. via CLI or hardcoding it in the .ini file.

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.