What is your favorite Shoot-em-up?

quicksilver

@pjft I confirmed it has the proper permissions. Not sure how to check the MD5. Here is the runcommand.log:

Parameters: 
Executing: /opt/retropie/emulators/reicast/bin/reicast.sh omx "/home/pi/RetroPie/roms/dreamcast/Ikaruga (Japan).chd"
/opt/retropie/emulators/reicast/bin/reicast: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /opt/retropie/emulators/reicast/bin/reicast)

mitu

@quicksilver What version of RetroPie are you running ? Looks like a mismatch of binary versions.

quicksilver

@mitu Ah! should have thought of that. I believe Im still on 4.3. Havent taken the time yet to migrate to 4.4.

mitu

@quicksilver Try updating from source, this should eliminate any issues with binary compatibility.

quicksilver

@mitu Wouldnt that overwrite /opt/retropie/emulators/reicast/bin? I have reicast working, I just couldnt get it to work with pjft's version.

mitu

@quicksilver I see. So you actually copied the other version - which was probably compiled for Raspbian Stretch - that's why the error occurs. If your original version doesn't work with this ROM , then there's no point in re-compiling (although it wouldn't hurt to get the last version).

quicksilver

@mitu Yea Im still on Jessie. Reicast works fine I just cant get anything to load using the older version of reicast that pjft linked to. If its a binary mismatch then I will just have start working on getting retropie 4.4 setup on my spare SD card.

Would updating from source actually improve anything? I had thought that reicast was basically dead as far as development goes. Or that the branch that retropie uses is?

Anyway thank you for your help. As always you are a gentleman and a scholar!

mitu

@quicksilver said in What is your favorite Shoot-em-up?:

Would updating from source actually improve anything? I had thought that reicast was basically dead as far as development goes. Or that the branch that retropie uses is?

It's not really dead, but their requirements have gone up (AFAIR) and the developments seem to happen first on the associated Libtretro core (not the standalone emulator).

pjft

Ah, you’re on Jessie. Sorry about that then - I didn’t think about that!

My bad. Can you recover your old binary at least then? If not, I will help you recompile it and recover it.

I can also try to find out, from the Reicast RetroPie repository, what version would be the one I have, and I can then share instructions to compile it yourself. That would probably have been a wiser decision from the get go, just a bit more time consuming.

Sorry about that.

quicksilver

@pjft Its no problem! I backed up my old binary first so everything is back to the way it was. Ive been needing to update to retropie 4.4 so maybe this is the motivation I needed to start on that.

pjft

@quicksilver Well, if you'd be going for 4.4 altogether, I imagine this is the binary that comes with the 4.4 image.

But if you have a proper working setup, I am not sure I'd risk messing things up :)

pjft

@quicksilver Well, just to update, I've been at it for a few hours now but I'm struggling to compile older version of Reicast on Stretch, which kind of makes sense as the last commit updates the library names to be compatible with stretch and SDL 2, so that's as far as I can go without a lot of trial and error.

I imagine that, if you're feeling lucky and you're comfortable with the Linux shell and Git, you could compile Reicast yourself, reverting some commits until you get to a version that actually works.

Just a thought. I'm happy to share commands for that to get you started, but hey, if you're considering moving to Stretch, that can also help :)

Sorry about that.

EDIT: Also, to be very pragmatic and, in all honesty, publicly puzzled, I don't have an idea about why this binary works, or how do I have it/where does it come from, if the last commit from the RetroPie repository is in 2017, but RetroPie 4.4 was launched in Apr 14, 2018, which would kind of suggest that the binary I have cannot be different from the one we'd get when compiling from source.

Just putting that out there, as it makes very little sense to me. If only I could find a version/build date for this binary, it'd make me a lot more comfortable, but there seems to be no command-line option to get that either. At this stage I don't even know if somehow I got it from compiling the official reicast repository (unlikely), or if there was a time when the reicast setup scripts were pointing to other branches.

So that's that, really, very honestly speaking. I'm sorry I can't be much more help - it'd also make me somewhat more comfortable if someone actually managed to run this version and confirm whether it does fix things for them or not.

Just to reassure myself that I'm not going crazy. :)

quicksilver

@pjft it's definitely odd. Partly because of how it moves the bios location. I don't ever remember a change like that.

pjft

@quicksilver well, that one did happen though.:)

The new BIOS location only came to be in August 2018:

https://github.com/RetroPie/RetroPie-Setup/wiki/Dreamcast/_history

The BIOS folder is where it had been prior to that. I had come from a 4.2 setup (maybe older? It was 2016 or so) and that's where I kept my Dreamcast BIOS files before.

quicksilver

@pjft I'm so confused...was there a commit that automatically moved the bios to /bios/dc/? Because that's where mine are located but I don't ever remember having to move them into the dc folder. And I setup Dreamcast on my pi over a year ago. I guess it doesn't really matter, I just need to finally get set up on RP 4.4. I appreciate all your help with this. When I am done with the migration I'll report back if it works.

pjft

@quicksilver I'm not sure if that happened - only if RetroPie-Setup did that in an upgrade hook. But I'm not sure that would have happened.

In my case, I reinstalled a fresh 4.4 image on a SD card I had lying around and surprisingly (or not), Reicast does not come installed, so the thought of it being the binary that came with 4.4 goes up in smoke.

However, that led me to something different: if I install Reicast from binary, it seems to work just like I have it. If I compile from source, it doesn't. I'm looking into the source of this to check whether that is 100% accurate, or whether there's something else at play here.

So, instead of monkeying around with the file I just shared, for now you can just try to update Reicast from binary in 4.4 and see if that works.

EDIT: confirmed. I installed from source and stopped working. I installed from binary and it works, so mistery err... postponed. @mediamogul if you want to solve your Ikaruga issues, try updating Reicast from binary instead of from source and let me know how it goes. @quicksilver you might as well try to do it on your current setup, though there is the chance that the jessie binaries are from a different codebase.

zefolhadela

Aero Fighters 3 it is a arcade game, game is good, stunning soundtracks.

quicksilver

@pjft just wanted to report that updating from binary fixed the issue with ikaruga. So it must be the correct binary even for Jessie.

pjft

@quicksilver well, that's a great turn of events.:) You fixed Ikaruga AND avoided an upgrade. And as a bonus, I'm not crazy.

Happy Sunday!

AndersHP

But wasn't Ikaruga supposed to be unplayable on the Pi3?
Is Dreamcast now emulatable, or?