Streets of Rage Remake (latest retropie 2019)

cyperghost

@Solid-One said in Streets of Rage Remake (latest retropie 2019):

The pushd and popd commands before seems to be doing this exact same thing (although in a different way) and they're working this way on my RPi2. Are you sure that, when you said previously that the instructions I've written on this post didn't worked, they indeed didn't worked?

No, the pushd does not do the same thing as linking the game data.

The pushd can be descriped like this. You are working in an enviroment and don't know in which directory you currently are. So you save $PWD to a variable for later usage. Now you jump to a directory you know /opt/retropie/ports/sorr and save this directory to annother variable. Now you can call any of these values and know you are in the right path. This is the kind of way pushd works (not exactly but kind of)

I think we both misunderstood by this
you said:

The theory behind this: maybe the commands "pushd" and "popd" are making the difference here.

I said:

No... surly not ;)

The theory behind is, that SorR only works right if it's started by EmulationStation - out of SSH terminal it does not work (for me at least). And it does not matter if you use cd command or pushd command for changing pathes.

My system is 4GB sized SDcard all other data (music, roms, scrapes, art) is on a USB thumb drive. So I assume that linking the game data is a good way to be portable at all.
As I said: It was my fault in first instance to don't check the correct filenames and game call itself.
Btw: the 333 version is also working and it does not crash if you change video settings ;)

Hope this is solved now and happy brawling :)

mitu

@cyperghost said in Streets of Rage Remake (latest retropie 2019):

The theory behind is, that SorR only works right if it's started by EmulationStation - out of SSH terminal it does not work (for me at least). And it does not matter if you use cd command or pushd command for changing pathes.

SoRR uses SDL1, which needs that the controlling terminal (tty) has a FB (framebuffer) attached so it can access the video output, your SSH session doesn't have such thing, hence the crash. If you run the same command using a keyboard connected to the PI directly (after exiting Emulationstation), you won't have any errors.

cyperghost

@mitu Thank you for giving us a deeper insight on explaining the technical background :)

mrbee

@SinisterSpatula hey. I followed this and I always get to this stage where when i select it from ES i get this black screen that "says no config found for system ports" and throws be back into ES menu.

ive made sure that the systems.cfg is there. and even say if i rename the system to "streets of rage remake" instead of "sorr" itl show on es with the updated name change but will still throw be back regardless

mrbee

@cyperghost That is great news! I shall give this a go tonight.
Just wondering though is the way you have typed it here the exact way it should be corrected to? if i can get it running through command line then i can finally get to the fault with es not launching it

cyperghost

@mrbee No... usually if you install with zerojays Streets of Rage Remake then it should work

You can also check if your config in /opt/retropie/configs/ports/sorr/emulators.cfg does look like this
The gamedata, SorR.dat and the directories mod and palettes have to be next to the bgdi-330 file.

sorr = "pushd /opt/retropie/ports/sorr; ./bgdi-330 ./SorR.dat; popd"
default = sorr

mrbee

@Solid-One said in Streets of Rage Remake (latest retropie 2019):

$ cd /opt/retropie/ports
$ ./bgdi-330 ./SorR.dat
I FINALLY got it to run!!

Ok so I followed the guide linked above (https://sinisterspatula.github.io/RetroflagGpiGuides/sorr) and this time I made sure to have only the files from sorr.zip that is needed (no exe or .dll files). I ran the commandline above but it thew an error saying no such file.
Since the sorr installer puts the files in opt/retropie/ports/sorr I had to go to this directory and then run it.
so cd /opt/retropie/ports
./bgdi-330 ./SorR.dat

this makes it run through cmdline.

It will not run through SSH (putty) but the game runs through command line!

My issue I am having now is that i have a default systems.cfg. And my systems config for ports is-

<system>
<name>ports</name>
<fullname>Ports</fullname>
<path>/home/pi/RetroPie/roms/ports</path>
<extension>.7z .pce .ccd .chd .cue .zip .7Z .PCE .CCD .CHD .CUE .ZIP</extension>
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS ports %ROM%</command>
<platform>ports</platform>
<theme>ports</theme>
</system>

with this config, no streets of rage remake shows up (the system PORTS) does not show in the es system carousel so i cant select it to start.
This is because the config is set to look for the home/pi/retropie/roms/ports folder (of course the sorr installer and the instructions in the guide say to put the files in opt/retropie/ports folder.

So I change the config to say to look for ports in opt/retropie/ports in the systems config. It then shows up in the system carousel!

HOWEVER I am back at the error "No config found for system ports" when i select it through emulationstation.

So I can run it through cmd... but i cant get it to show up in emulationstation!

If i change the essystems.cfg it throws up the "no config found" when i launch it through es.. so am stuck on this final part now.

Would anyone mind pasting their essystems config to see if this is what is wrong? that i think this will then solve the issue I am having. I think!
Im not sure why this step is needed for me

mitu

@mrbee The problem is not the es_systems.cfg file, but the emulators.cfg from the /opt/retropie/configs/ports. If you followed the instructions from the page mentioned, that file would have been created - did you install SoRR from the RetroPie-Setup menu ?

mrbee

@mitu Thanks for the reply, yes I had followed the instructions. The file is there but still getting this issue.
I installed SoRR exactly as in the guide from the RetroPie-Setup menu.
What should it say inside of the emulators.cfg file that is making this throw up the error?

mitu

@mrbee It might be useful to post the contents of said file (it's actually /opt/retropie/configs/ports/sorr/emulators.cfg) and compare with a working configuration.

Solid One

@cyperghost Wow, I didn't noticed you were trying to run SorR through SSH. That being the case, it's exactly as @mitu said: Chances the app won't run properly are high.

So, it'd be interesting to redo the terminal tests, not through SSH, but directly with an USB keyboard attached on you RPi (press F4 and EmulationStation will be closed, and you'll be redirected to the terminal).

mrbee

@mitu Ok ive looked in the /opt/retropie/configs/ports/sorr/emulators.cfg and it is there and inside that sorr folder is a folder called pallets, emulators.cfg, savegame.sor
the contents of the emulators.cfg is sorr = "pushd /opt/retropie/ports/sorr; ./bgdi-330 ./SorR.dat; popd"
default = sorr

cyperghost

@Solid-One In ES terminal it would work

mrbee

@cyperghost Do you know why i keep getting the "no config found for system ports" in es? The game runs fine in commandline but wont run through es.

cyperghost

@mrbee said in Streets of Rage Remake (latest retropie 2019):

@cyperghost Do you know why i keep getting the "no config found for system ports" in es? The game runs fine in commandline but wont run through es.

Yes

<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ ports %ROM%</command>

All files in ports section are shell script files and they are executed by bash %ROM%your call would simply not work. You would need the help of a small script.

<command>/path/to/helper_script.sh %ROM%</command>

helper_script.sh

#!/bin/bash
extension=${1##*.}

case ${extension,,} in

    sh) #shell files
        bash "$1"
    ;;


    *) #rest of files
        /opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ ports "$1"
    ;;

esac

mrbee

@cyperghost im sorry im not sure what you mean with what you have pasted. im sounding really stupid here arent i. my level is so basic with this stuff.

what exactly should i paste in instead of what i have in my config for the runcommand? im so close to getting it to work. do i just paste in what you have put in your reply? im not sure what the helper_script.sh file is or where it is.

jlhorner1974

I know this may not be the right place to ask for help, but I couldn't find any topics on SoRR the HyperPie forums, and was hoping one of you could help. I have the Streets of Rage Remake running on HyperPie 2.5.1, but mapping controllers has been difficult for me. I have an arcade stick from Game Room Solutions (Xin-Mo USB controller, which shows up as two gamepads), and If I configure Streets of Rage Remake to use both gamepads, then the left side of my arcade controller controls Player 2 in the game, and the right side of the controller does nothing. I also have a keyboard connected.

It looks like SoRR is somehow enumerating the controllers in a way that I don't want. It appears that SoRR sees something else (the Keyboard maybe?) as the first plugged in gamepad, the left side of my arcade controller as the second plugged in Gamepad, and the right side of the controller as the third plugged in Gamepad. All of the buttons work properly when the arcade controller is connected to Windows and I look at the Gamepad properties.

Unplugging the keyboard and rebooting the Raspberry Pi does not seem to help.

Also, the arcade controller works fine with MAME and CPS2 games in Emulation Station on HyperPie (both 1P and 2P controls work fine for SSF2T, Alien vs Predator, and other games).

Is there a way I can configure SoRR somehow to enumerate the gamepads the way I expect so both 1P and 2P controls work?

cyperghost

@mrbee The script I posted can divide between shell scripts and ROMs. So this would help you to start SorR out of your ES-setup.

You need to edit your command line according the path you save the script.
`<command>/path/to/your/script/helper_script.sh</command>

Then make helper_script executable by typing chmod +x /path/to/your/script/helper_script.sh

That's all. If something goes wrong with the script start then you've likely used a wrong text editor in this case type unix2dos /path/to/your/script/helper_script.sh to convert the script in correct file format. You'll make it, don't worry. Maybe you can also just add a second "system" only for shell files?

mrbee

@cyperghost thanks for helping me understand. ive never made a shell script before so now is the time to do it! il follow your instruction tomorrow and give it a go!

just wondering though. of all the guides ive seen and people who have got this to work why didnt they have this no config found error and have to create a script for it to run? ive never seen this step.
perhaps it is just my technology curse haha

ExarKunIv

@mrbee hate to say it but might be the curse. I have had to redo my build more times then I like to say and once someone help me to get the data in the right place. I have never had a problem.

Very confused on this for you