Streets of Rage Remake (latest retropie 2019)

[RetroNerdman]

Hijacking the topic, I literally quit trying running the game this past weekend due to exactly the same reason.
When opening the log, it said some line had fragmentation fault.
I tried updating and upgrading the installation to make sure I wasn't missing any dependencies, then I tried re-installing and re-transfering the SoRR data to the RaspberryPi.
I double checked the CRC to make sure there were no issues from unpacking from the RAR I've had for years to the file in the SD card.

Edit:
I have no idea what happened. I've downloaded the 333 version, but couldn't make it run (error message said I didn't have the right permissions). Then I tried loading the game again with the 330 version and it worked? I've uninstalled everything and re-installed again. It works. It's just working. And I have absolutely no idea why. Nothing else has changed in my setup.

[mrbee]

I will try to get that 333 version and run it, perhaps then it sort of changes some cached setting (no idea what i am talking about by the way) and when you run the 330 version it has "refreshed".

One thing also, what would be causing emulationstation to say "no config found in system ports" Ive checked the es systems config and all seems correct, even changed it to find ports in the opt/retropie/ports/ folder (and not the roms/ports folder)

[mrbee]

i tried to download the other version but it says error 404 not found on that file page

[mrbee]

What is the best thing for me to do?
I think i will make an entirely new retropie image from scratch and just load sorr on it.

i will follow the floobs guide on youtube and record here what steps work and what doesnt so can get a definitive way to get this working step by step

[Solid One]

Sorry the delay. Was kinda busy these days.

Anyway, I took a look on some files in my desktop, and my RPi2's sd card files. I'm using RetroPie 4.1, from 2016, which is based on Raspbian Jessie, I guess.

Back then, I've installed SORR through RetroPie-Extra, which still uses bgdi-330 in order to run it. The last time I run SORR on my RPi2, it worked just fine.

However, even if there's the possibility of making SORR work if you downgrade to RetroPie 4.1 and try installing it via RetroPie-Extra, I don't think that's impossible to run SORR on newer RetroPie versions. There's still the possibility that bgdi-333 can make SORR work. You still should test it, before trying the downgrade approach.

And talking about bgdi-333, I was able to download that version just fine from their forums. They're there as a forum attachment on the first topic, and you won't be able to see / download them without having logged in, so you should create an account in there, in order to see the link:

[ExarKunIv]

i did messing around to see if i could be any help, but i cant. i just did a clean load with the latests version updated to the latest build which is 4.5.1 on my pi3b and SORR works fine for me. and im useing the bgdi-330 file.

ill try to help if i can.
quesion are you only putting the SORR.dat file or are you putting others also?

[mrbee]

i pretty much dragged the whole contents of the sorr folder over into the pi so it has the sorr.exe and sormaker.exe and all of that in there.
Thanks for the help with all of this.

I tried to create an account to download the link but they havent sent me a response to verify the account so am unable to log in.

So what ive done is followed this guide to the letter -

I get as far as 4:31 in the video and it says no file location in the command line. It seems that with the latest retropie and the install from the extras in the config has changed the paths from retropie/roms/ports to retropie/ports.

So I got confused then. I presume that the sorr script is looking for the files in opt/retropie/ports (not home/pi/retropie/roms/ports.

I then dragged the whole contents of the sorr folder from my pc into opt/retropie/ports/
I had to chmod 777 in the command line to get root access to add it to this location.

The game shows up in the emulationstation menu but when i select it all i get is a black screen which says "no config found for system ports" and throws me back to the menu.
Is this because I have too many files/unwanted files in the sorr folder?

I want to get this working and then make a step by step guide video on how to get this done.
I really appreciate the help. Its got to be something im just doing stupidly wrong!

[ExarKunIv]

@mrbee do you happen to know what version you have of sorr. I know I have 5.1

[cyperghost]

@mrbee SorR seems to be broken on RetroPie 4.5.1 - I know I was able to run it on 4.2, 4.1 but not on 4.5.x.
I also tried to reactivate and it does not work with precompiled binaries. There must be more work done in this... Likely a PANDORA build with sources from gamemaker2k
https://github.com/GameMaker2k/BennuGD - here it is pushed to version 3.5.3

Or here a guy named butcher made the port for the Raspberry.
http://forum.bennugd.org/index.php/topic,4196.0.html

[Solid One]

@cyperghost Which bennugd binary have you tested on RetroPie 4.5.1? If it's bgdi-330, then maybe it's not the latest one.

Try bgdi-333 from here. Maybe it can work on RetroPie 4.5.1. Remember to create an account to see the attachment, as shown above.

If I'm not mistaken, both binaries were compiled by butcher. He seems to be a veteran user from bennugd forums. Even if you have no success running SORR on RetroPie 4.5.1 with both binaries, then we should try contacting butcher (probably in spanish, according to the bennugd forum messages) and ask him to provide newer BennuGD Raspberry Pi binaries for the latest raspbian versions.

[mitu]

It could be that the binary was compiled for another Raspbian version and some of its dependencies (dll's) are not present by default on a newer version.
If it's not running, take a look at /dev/shm/runcommand.log and see if any error message appears.

[cyperghost]

@mitu @Solid-One Okay, I should be more precise here.

1. It does not matter if I use bgdi-330 or 333
2. The binaries do run, if I start them without argument they give out text message
3. if I use ldd command all dlls are found
4. If I want to start with SorR.dat with extracted /palletes and /mod dir then I receive a error segmentation fault
   4.1 I used Unix 5.1 version
   4.2 Windows 5.0 version
   4.3 Windows 5.1 version

I give you checksum of files okay?

; Generated by Hasher (www.den4b.com) 
File	Path			Size		CRC32		MD5					SHA1
1	C:\temp\u51\SorR.dat	253,705,339	F47541FC	577809a769451da2a13cf728231d3de6	6016577c530c099d1b03b801b378f121879e47da
2	C:\temp\w50\SorR.dat	253,064,906	8F993FD0	cb72d11f60b603682eee0687b6578fb1	f16eabb41b0d077ffa2696f86a3ccc4a57ca6972
3	C:\temp\w51\SorR.dat	253,705,647	3A19D4C2	2e10aec879bdb9c398ffdab9e44433be	2b1c536f9878dad4fab3a781e7539925a8b8f78e

[Solid One]

@cyperghost So, both 330 or 333 are giving segmentation fault on RetroPie 4.5.1? And they run fine on older RetroPie versions, such as 4.1 or 4.2?

If that's the case, then I think that's what happened:

• RetroPie 4.5.1 is based on the latest Raspbian versions, with codename Stretch or Buster, dated between 2017 and 2018;
• Retropie 4.1 and 4.2 are based on a previous Raspbian version, the one with codename Jessie, dated from 2016;
• Both binaries compiled by butcher are dated from 2016, which match Raspbian Jessie, thus explaining why it works on RetroPie 4.1 / 4.2;
• Since RetroPie 4.5.1 updated Raspbian version from Jessie to Stretch or Buster, the BennuGD binaries from 2016 won't work anymore, due to architecture differences, thus explaining why the segmentation fault ocurred. That being the case, the BennuGD binaries must be recompiled based on Raspbian Stretch or Buster in order to work.

That being the case, there is three solutions / workarounds I can think of:

1. Try compiling BennuGD binaries from source by itself (if there's any);
2. Go to BennuGD forums and ask butcher to recompile the binaries for Raspbian Stretch / Buster. You'll probably have to speak in spanish in there;
3. Downgrade RetroPie from 4.5.1 to 4.1 or 4.2.

Wow, after that discovery, guess I won't update RetroPie on my RPi2 too soon. Having SORR working on my device is a big plus that I don't wanna lose yet.

[mitu]

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

Since RetroPie 4.5.1 updated Raspbian version from Jessie to Stretch or Buster, the BennuGD binaries from 2016 won't work anymore, due to architecture differences, thus explaining why the segmentation fault ocurred. That being the case, the BennuGD binaries must be recompiled based on Raspbian Stretch or Buster in order to work.

what architecture difference ? It's the same system, just with updated software, the architecture is the same (armhf).

[Solid One]

@mitu my bad. By architecture, I mean "debian distro version differences". Indeed all raspbian and retropie versions share the same architecture (armhf), but different distro versions tend to have some package differences. That's why all default packages are recompiled on each new version or a distro.

[cyperghost]

@Solid-One The source codes are available ... I mentioned this already. I rather think it's the SDL framework. There were some massive changes through 4.2 up to 4.5.x

Can you compare checksums of DAT files, too?

[mitu]

@cyperghost The source doesn't compile on Raspbian Stretch - some of the used functions call OpenSSL DES functions, which have been long gone from regular OpenSSL distro builds.

[cyperghost]

@mitu Hello ;)
If you compile then there are 2 binares build....
bgdi-xxx and bgdc-xxx
We need only the bgdi one, the bgdc(??) spits on an error SSL.
So I assume OpenSSL is not needed....

But don't ask me why there were only binaries released. Not so a nice habbit :) Not future proof

[mitu]

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

We need only the bgdi one, the bgdc(??) spits on an error SSL.
So I assume OpenSSL is not needed....

I can't get to compile either one, both targets are not building under Raspbian Stretch.

[cyperghost]

@mitu Yes I tried, too.
From Pandora build script after setting some compiler calls gcc and g++
But I quickly failed in compling... the sources.

But for me, I don't have time to take a deeper look in this. Maybe if @Solid-One will post the checksums of his DAT file, then we can exlude user errors.

But I think that the prebuild binaries simply do not run (full) on Raspbian stretch!