Working Dreamcast games

barbudreadmon

@quicksilver Maybe a long time ago when there was no arm dynarec, no threaded rendering, no frameskip, ... Or perhaps are you talking about the crazy question everyone asked, aka "The oit renderer will be available on raspberry ?".

Now that all of this is togglable in lr-reicast through core options, there is barely any reason for it to perform worse than standalone.

quicksilver

@barbudreadmon thank you for your explanation. Is there a way to install lr-recaist manually? I would be happy to test it's performance on my pi.

BJRetro

@quicksilver I would be willing to test too if easy to install lr-reicast. I have had good success with standalone and have two setups so could leave one with standalone so I could pretty easily check how different if at all lr-reicast is with whatever settings are deemed proper.

hooperre

This post is deleted!

mitu

@quicksilver Since lr-reicast is already a scriptmodule, if you're willing to give it a try, this is what you need to modify

replace the rp_module_flags with

rp_module_flags=""

in the build_lr-reicast function, replace the single make line with

make platform=rpi3

Try to install from source, the lr-reicast scriptmodule should be in the experimental section.

At some point, I think the lr core was requiring GLES 3, so that's why it was excluded for the Pi, but maybe I'm mistaken.

EDIT: forgot to say, you'll have to modify the $HOME/RetroPie-Setup/scripts/libretro/lr-reicast.sh file. With the modifications from before, the compilation works (GG NO RE), but I havent' got time to test it with a game.

barbudreadmon

Btw, here are the settings that are good for speed :

Enable Threaded rendering
Set Alpha sorting to per-strip
Decrease resolution
Disable Texture Upscaling
Disable Modifier Volumes
Enable Div Matching
Disable DSP
Increase frameskip

quicksilver

@mitu build was successful but any game I launch just sends me back to ES.

@barbudreadmon is lr-recaist compatible with .chd files?

mitu

@quicksilver said in Working Dreamcast games:

build was successful but any game I launch just sends me back to ES.

Looks like a BIOS issue. Launch with verbose logging and look at the log file (/dev/shm/runcommand.log) and see where it's looking for them.

is lr-recaist compatible with .chd files?

It should be - https://github.com/libretro/reicast-emulator/pull/367.

pjft

Even with a CDI file it doesn't run.

https://pastebin.com/21U0SF8d

The last few lines suggest

[INFO] Environ UNSUPPORTED (#65585).
/opt/retropie/supplementary/runcommand/runcommand.sh: line 1006:  5554 Segmentation fault

barbudreadmon

Yes it is compatible with chd, the bioses go into [system]/dc/, [system] being your bios folder for RA cores, same dc_flash.bin and dc_boot.bin as standalone. For naomi support, the bioses are naomi.zip, awbios.zip, f355bios.zip, f355dlx.zip, hod2bios.zip and airlbios.zip from mame romset.

barbudreadmon

@pjft Seems like a no-bios issue too, at the very least i can reproduce a crash at the same moment if i delete my bioses. It might be a good idea to update your RA too, yours might be too old (cf. the Environ UNSUPPORTED messages)

pjft

@barbudreadmon ah, that's fair. My RA is indeed a bit outdated by today's standards.

The BIOS did seem to load in lines 192 and 194 but it might be RA related.

Thanks!

WarC0zes

I tested lr-reicast, but no games are launched, it comes back emulationstation.
I have the bios in Retropie/Bios/dc/
I have this as error : /opt/retropie/supplementary/runcommand/runcommand.sh : ligne 1003 : 5513 Segmentation error

https://pastebin.com/LqnvXhmU

My settings:
Retropie 4.4.8
Rpi 3 B
ES 1.8.1
RA 1.7.6

quicksilver

@barbudreadmon so I updated retroarch to latest version and made sure my bioses are in /BIOS/dc but after launching a game it still kicks me back to emulation station

mitu

I had the same crash while testing, but followed This comment on the Issue tracker and now the core starts.
Only tested Ikaruga (from a .chd) and started a game, looks a bit choppier than the standalone. Note that I didn't apply all the settings that @barbudreadmon mentioned, I only made sure Enable Threaded rendering and put a frameskip of 1 just to check. I suspect lowering the resolution would also help, but remains to be tested further.

Febbweiss

Same thing for me, backing to emulationstation. But lr-reicast works. If you copy/paste the command line in the /dev/shm/rucommand.log and execute it (after quitting or killing emulationstation) the emulator works even Wacky Races.
I don't know why it crashes using emulationstation launcher...

barbudreadmon

I tried the core on my rpi3b+ and didn't experience this issue (i'm using my own custom setup not based on retropie/debian though). You might try what @mitu suggested, aka adding < /dev/null at the end of the command line in your es_system.cfg.

About performances, it was playable in the few games i tried (i tried a few naomi/atomiswave games like "hokuto no ken" too), same as standalone.

mitu

Forgot to mention I'm using a 3B model (non B+). To complete what @barbudreadmon suggested, I've modified the entry for lr-reicast in /opt/retropie/configs/dreamcast/emulators.cfg to get lr-reicast starting.

lr-reicast = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-reicast/reicast_libretro.so --config /opt/retropie/configs/dreamcast/retroarch.cfg %ROM% </dev/null"

WarC0zes

@mitu Thanks, the games are launching now :)

after test, works better reicast than lr-reicast for rpi 3B.

barbudreadmon

@WarC0zes said in Working Dreamcast games:

after test, works better reicast than lr-reicast for rpi 3B.

You probably mean faster (it is, slightly), because lr-reicast is better in terms of compatibility and features, one example is that the dead zone thing mentioned by @backstander is in core options.