@Jste84 I haven't tested this yet, but it should replicate the steps outlined in:

https://github.com/fofix/fofix/blob/master/doc/source/quickstart/Linux_Setup_Guide.md

...with some educated guesses in re: the md_ret_files and # symlink config dirs functions.

Make a backup, first. It wants to install pip from an external source (https://bootstrap.pypa.io/pip/2.7/get-pip.py -- seems legit, I guess? See also: https://github.com/pypa/get-pip#readme) and then use it to install some additional packages; also it wants to remove package libjack-jackd2-0 and replace with libjack0 as a dependency required to to install portaudio19-dev.

I haven't tested because I have no interest in playing this with a keyboard, and the GH controller I thought was in the back of my closet turned out to be for PlayStation (so, not USB), so I'm going to leave my system as-is. Let us know if it works for you, though, and I'll submit a PR; in any case, we should probably remove the old script, as it doesn't do anything useful (it builds glshim that isn't needed, and then it attempts to install a package that doesn't exist and configure a port that wasn't installed.)

To use, paste this code into your ~/RetroPie-Setup/ext/RetroPie-Extra/scriptmodules/ports/fofix.sh file, replacing all of its existing contents, and then reinstall fofix through RetroPie-Setup.

#!/usr/bin/env bash # This file is part of The RetroPie Project # # The RetroPie Project is the legal property of its developers, whose names are # too numerous to list here. Please refer to the COPYRIGHT.md file distributed with this source. # # See the LICENSE.md file at the top-level directory of this distribution and # at https://raw.githubusercontent.com/RetroPie/RetroPie-Setup/master/LICENSE.md # rp_module_id="fofix" rp_module_desc="Frets on Fire X - Guitar Hero and Rock Band clone" rp_module_licence="GPL2 https://raw.githubusercontent.com/fofix/fofix/master/COPYING" rp_module_repo="git https://github.com/fofix/fofix.git" rp_module_section="exp" rp_module_flags="noinstclean !mali !x86" function depends_fofix() { getDepends python2 libglu1-mesa-dev freeglut3-dev mesa-common-dev ffmpeg pkg-config libogg-dev libportmidi-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-ttf2.0-dev libsdl1.2-dev libsoundtouch-dev libswscale-dev libtheora-dev libvorbis-dev mesa-utils portaudio19-dev python-dev gettext xorg # install pip and packages local tmpdir="$(mktemp -d)" local url="https://bootstrap.pypa.io/pip/2.7/get-pip.py" local file="${url##*/} download "$url" "$tmpdir" python2 "$tmpdir/$file" rm -rf "$tmpdir" pip2 install - numpy pip2 install --upgrade cython pip2 install PyOpenGL PyOpenGL_accelerate } function sources_fofix() { gitPullOrClone } function build_fofix() { python setup.py build_ext --inplace --force python setup.py msgfmt pip install -r requirements.txt # ensure build completed md_ret_require="$md_build/build" } function install_fofix() { md_ret_files=( 'fofix' 'data' 'FoFiX.py' ) } function configure_fofix() { local script="$md_inst/$md_id.sh" local file="$md_inst/FoFiX.py" addPort "$md_id" "fofix" "FoFiX - Guitar Hero and Rock Band clone" "XINIT:$script" moveConfigDir "$home/.fofix" "$md_conf_root/$md_id" [[ "$md_mode" == "remove" ]] && return # chown install dir -- may not be necessary? #chown -R $user:$user "$md_inst" # symlink config dirs local dir for dir in mods shaders songs themes tutorials users; do moveConfigDir "$md_inst/data/$dir" "$md_conf_root/$md_id/$dir" done cat > "$script" << _EOF_ #!/bin/bash python "$file" _EOF_ chmod +x "$script" }

...if it installs but doesn't play (or if it plays but doesn't save, or crashes), try removing the # from line #chown -R $user:$user "$md_inst", and install again. This will make the install directory user-owned instead of admin, allowing files to be written to here by the normal user when the game is running.

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

@boolean im always wanting to make the games better
if you figure out a way to make the sound better.

post on how you did it and i can add it to my script so everyone can enjoy it.
plus it gives me something to figure out :)

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

@sleve_mcdichael said in Is there a guide somewhere to create install scripts if you can get a game to compile?:

What is the significance of the CMakeLists.txt param in ...

The correct way to invoke cmake is

cmake <PARAMS> <path_to_folder_containing_CMakeLists.txt>`

... the && cd build part didn't do anything, so it tried to cmake & make from the wrong dir and, predictably, failed.

Don't use && then, just have the 2 commands separately.

.. this one just built it right there in the main tmp/build/module folder. Do I want to leave it in or out? Does it make a difference?

No, but some programs enforce a separate build folder (out-of-tree build) so you may get an error when building directly in the source folder.

Also, it still made the same file, but it put it in the wrong place. So if I were to use retropie_packages.sh <module> install after this, it would be installing the old one from the "build" dir and not the new one I just built in the wrong place, so this isn't a solution.

If you change the build parameters, then do a cleanup first.

I think I could begin the build function with a [[ -d build ]] && rm -rf build to remove the dir if it exists?

I don't think that when building with cmake this step is necessary, so that's why is not enforced. This is an issue only when repeatedly re-building without cleaning up, so it's more of an artifact of re-trying the build with a 'dirty' state.
You should first compile the program separately - not as a scriptmodule - to get the cmake build options right, then add it to the build function and try it from retropie_packages.sh.

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.