SNES MSU-1 Guide
-
@mitu I had the folder name mixed up and it has been updated in my original post.
The command is being launched from the
./RetroPie/roms/snes
folder. The actualalttp_msu.sfc
and all the.pcm
files are located within the./RetroPie/roms/snes/.Legend of Zelda, The - A Link to the Past (USA)[MSU-1]
folder.I don't think it depends on the starting folder. If I just (from the command line) ran the
.sh
file containing either one of the blocks of code written above:
sudo bash home/pi/RetroPie/roms/snes/alttp_msu.sh
the file runs correctly, and with all the correct RetroArch configs, but this doesn't happen when launching from EmulationStation. I'm not sure if launching it from ES changes the way that RetroArch handles it somehow or something. -
@hooperre You can see the launch command used by Emulationstation by looking at the
/dev/shm/runcommand.log
- it should be the first line. That being said, the command you posted (usingruncommand
) seems like something similar to what Emulationstation would launch.
If the launching commands prove to be the same, try running with verbose logging when you launch from Emulationsation (by using theruncommand
launch menu) and maybe there's some clue in the detailed log about what's missing. -
Ah. It's calling for the actual
.sh
file itself when I use theruncommand
as opposed to the.sfc
. Dump:Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-snes9x/snes9x_libretro.so --config /opt/retropie/configs/snes/retroarch.cfg "/home/pi/RetroPie/roms/snes/alttp_msu.sh" --appendconfig /dev/shm/retroarch.cfg
Not sure how to get around that. I'll try the other one again.
The other script with verbose logging: https://pastebin.com/BuUJbxN9
Appears to be calling for the
.sh
file as well. That one makes less sense to me. -
@hooperre said in SNES MSU-1 Guide:
Ah. It's calling for the actual .sh file itself when I use the runcommandas opposed to the .sfc. Dump:
That's not correct. Did you customize the EmulationStation system config file (
es_systems.cfg
) and added the.sh
extension as a valid ROM ? By default,.sfc
is one of the included extensions, so if you have the.sfc
ROM file in the folder,runcommand
should invoke the correct emulator. -
I did not add
.sh .SH
to thees_systems.cfg
.The script works well in the
ports
folder/menu in emulationstation and will launch the MSU-1 version of the game. It appears thatruncommand
is ignoring the text within the file and just launching the.sh
file as an accepted rom. I can't figure out a way around this and suppose I'll just have to create an extremely messyMSU-1
folder. -
@hooperre Can you post the
es_systems.cfg
on pastebin.com to take a look ? Is your.sfc
file addd in thesnes
folder ? -
es_systems.cfg
: https://pastebin.com/3V4uAygYalttp_msu.sh
is located in//home/pi/RetroPie/roms/snes
containing:/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-snes9x/snes9x_libretro.so --config /opt/retropie/configs/snes/retroarch.cfg "/home/pi/RetroPie/roms/snes/.Legend of Zelda, The - A Link to the Past (USA)[MSU-1]/alttp_msu.sfc" --appendconfig /opt/retropie/configs/all/retroarch.cfg
And
alttp_msu.sfc
is located in//home/pi/RetroPie/roms/snes/.Legend of Zelda, The - A Link to the Past (USA)[MSU-1]
. -
According to your config file, the
snes
system doesn't launch.sh
files<system> <name>snes</name> <fullname>Super Nintendo</fullname> <path>/home/pi/RetroPie/roms/snes</path> <extension>.bin .smc .sfc .fig .swc .mgd .zip .7z .BIN .SMC .SFC .FIG .SWC .MGD .ZIP .7Z</extension> <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ snes %ROM%</command> <platform>snes</platform> <theme>snes</theme> </system>
but it should be able to launch
.sfc
files. I don't understand how it launchedruncommand
with a.sh
file. -
@hooperre I was trying to do the same thing and I recently got it all sorted out. I described what I did to get it all working nice and clean in another thread.
Check it out here: Load NON-PC rom with a script?
-
@joelkolb Nice! They've been in my
ports
folder! Thanks! -
Tagged for later reading.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.