What is your favorite Shoot-em-up?

pjft

@mediamogul @quicksilver so, to close this Ikaruga detour off, just one more comment:

The game plays great in that build as it doesn't seem to have the issue (did any of you per chance test it?), and asides some visual issues like the borders (outside the game area) not being black, and a few visual effects missing (fog/clouds on the beginning of stage 2), I'm super happy for having gotten to play it!

One comment: don't run it from a CHD version of the ROM but rather a proper CDI or perhaps GDI. It might be that the ROM I compressed to CHD had an issue itself, but the CDI version I have runs at normal speed, while the compressed CHD version I put together from a GDI one I downloaded runs slower (gameplay) while the audio runs at normal speed. It is quite noticeable when set pieces have audio climaxing with specific on screen animation or action, but in the CHD version is not at all in sync, and the audio track finishes a while before the end of level 1 boss. I'll test out the actual original GDI source, as it might be faulty, and report back if I find that the original GDI I used has the same issue. If not, consider that when choosing the ROM version to keep.

quicksilver

@pjft I have not had a chance to test it yet. But my copy of the game is .chd so I'll have to look for an alternative copy.

pjft

@quicksilver well, let me confirm this tomorrow. It might certainly be the source ROM I got to compress into CHD that's faulty. I'll report back.

pjft

@quicksilver might have been a false alarm. It also happens in the source GDI ROM, so I'm thinking it's a faulty dump here. I'll look further into it.

It's ready to check with the audio sync behavior. This is how it should be like, and you should be able to play this video at the same time as your game, with both the audio and the gameplay being in sync with the emulation. My CDI version does so. The others have the audio in sync but gameplay stays behind. See just the sync in the intro sequence for chapter 1.

mediamogul

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

did any of you per chance test it?

I let a friend borrow my Dreamcast collection after Christmas to test out a hardware mod. However, I'll likely get it back this weekend. I look forward to trying it out.

detron

I loved Raptor on DOS, and Raiden Trad on Genesis, but my unpopular favorite is an arcade game "19XX"
maybe it is because I played this in my Barrack while in the Navy, but I genuinely love it.

gomisensei

@ultrakev9 agreed. I actually own a RaidenDX cabinet, though it was a conversion from Mercs, and the monitor has burnin. i converted it to a jamma mame cabinet and still go to my garage to play RaidenDX on it once in a while.

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

@sp I second this. Raiden DX is perfect in nearly every way.
No other game in this genre has ever allowed the player to do such catastrophic damage to the environment and no other schmup that I've ever played has allowed you to shoot down flying enemies and have them crash in to the ground and land on and destroy ground-based enemies. The attention to detail, design, sound, everything has never been matched, even by Raiden 3, 4 or 5.

quicksilver

@pjft Just got around to trying this out. Unfortunately it just dumps me back to ES with each game I tested. It looks like the BIOS files were in a different directory with your version of reicast but even once I moved them to the right directory it still didnt work.

nans1906

Capcom's 1942 on arcade and Thunderforce IV on sega megadrive.

pjft

@quicksilver oh, oh my! You’re absolutely right. The BIOS files in this case should be in RetroPie/BIOS directly, instead of in RetroPie/BIOS/dc/ . This is the new path - in the version I had they were still there.

dc_flash.bin and dc_boot.bin , I believe.

There should be absolutely no other change other than that. What error does runcommand.log show?

EDIT: sorry, just noted the original path I mentioned isn’t the right one.

It should be

/opt/retropie/emulators/reicast/bin

To confirm, it’s executable (sudo chmod +x reicast) and is it the right MD5 on the pi after copying it there?

MD5(/opt/retropie/emulators/reicast/bin/reicast)= 94a76466e3cfd63581c3b99981537268

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.