lr-flycast binary file update 8 mar

kounabi22

I update the emulator from binary and it say 8 mar why so outdated?

Folly

@kounabi22

Have you seen the commits over here ? :
https://github.com/libretro/flycast
Probably the reason.

windg

I remember the newer verision introdused some issues and for now we are using this version.

Folly

@kounabi22

Here are the facts, you can read it over here, see these 2 commits :

Commits on Dec 27, 2021
Commits on Jan 12, 2022

On :
https://github.com/RetroPie/RetroPie-Setup/commits/master/scriptmodules/libretrocores/lr-flycast

kounabi22

i mean this version

https://github.com/flyinghead/flycast

Folly

@kounabi22

You have to read the commits, it is saying it all !

Just like @windg said the newer lr-flycast from flyinghead didn't work correctly so they reverted to the older lr-flycast from libretro.
So the binary, most likely, isn't from the flyinghead repository anymore but from the libretro repository.
There is no need to update that binary as the source is not updated anymore.
So it's stuck on an old one and that is what you see.

If you use an older module-script, which still uses the flyinghead repository, then you have to install from source in order to use the latest from flyinghead.
(and hope when it works that it works better on a raspberry-pi now)

kounabi22

i see ,thanks.

barbudreadmon

@windg @folly It's still kind of a mystery to me why reverting to the dead repo was the chosen solution for all platforms, when the issue was apparently something that only happened on pi3 (which can barely run this at playable speed anyway) due to a bug in the userland gpu drivers. It should have been possible to build from the correct repo on pi4 and from the dead repo on pi3, or maybe to rename current script to flycast2021 (i'll bring up the subject of renaming that repo to libretro mods) and make a pi4-only new script.

Folly

@barbudreadmon

Ok, If that is the case, good idea renaming and suggesting a separate module-script for pi4 and higher.

windg

@barbudreadmon If i remember correct, the issue affect and RPi4. It was something to do with some games that was crashing back to ES. This old topic has few info : https://retropie.org.uk/forum/topic/32070/sega-smash-pack-vol-1-for-dreamcast . Thanks

barbudreadmon

@windg the only related issue i found is https://github.com/flyinghead/flycast/issues/559 : a commit was made to offload palette calculation to the gpu, and it seems to have caused issues with a few gpus with poor drivers.

The topic you linked seems to be about a regression on a winCE game (which might have been fixed since then if it was properly reported to flyinghead ?). My understanding from reading https://retropie.org.uk/forum/post/272277 is that support for winCE games was totally dropped when it was decided to revert to the old/dead repo.

Darksavior

@barbudreadmon Ah, no wonder it won't run on a pi5. It's an older build. I'm using redream for now.

retropieuser555

@Darksavior did you get your pi 5 already? How you finding it? Can you do significant resolution boosts on redream?

Darksavior

@retropieuser555 I don't want to derail the thread so you can ask further questions in the pi5 thread or another, but I preordered it on the 28th and it arrived yesterday. I haven't tried redream's internal resolution boost. I think you need to pay for it. I would rather try flycast instead and see if I can use a crt shader on it without any slowdowns.

retropieuser555

@Darksavior Oh also, I tried standalone Flycast on my pi4B bookworm 64bit, it builds fine. Crazy Taxi was pretty solid, dipped to around 45fps when had loads going on. Resident Evil 2 is a big slideshow (around 13fps).

So it doesn't build at all on pi5? I only used the standard cmake, make instructions from the standalone Flycast github, nothing special

Darksavior

@retropieuser555 lr-flycast? It builds. It crashes when loading a game with some message "debugbreak" or something. Retropie isn't made for the pi5 yet so I'll wait.

I know of the standalone flycast but the script I tried a while back was never finished so games won't directly load from ES.

retropieuser555

@Darksavior So this was what I did to build flycast on pi 4 64 bit bookworm. Wonder if it'll work for you on pi5:-

cd RetroPie-Setup

git clone https://github.com/flyinghead/flycast.git

cd flycast

git submodule update --init --recursive

mkdir build && cd build

cmake ..

make

I then took the flycast file I'd built and moved it into /opt/retropie/emulators/flycast/bin/ to tidy that up, then changed the dreamcast emulators.cfg config and added this line in

flycast = " /opt/retropie/emulators/flycast/bin/flycast -config window:fullscreen=yes %ROM%"

Lastly I went into /home/pi/.local/share/flycast and added the Dreamcast bios files into there. You could probably create a symlink to there from your DC Bios folder if you wanted to clean that up.

Now standalone flycast worked for me from EmulationStation, if you hit tab on a keyboard you'll get the settings menu up and can edit lightguns, video resolution, vsync and all that good stuff.

Darksavior

@retropieuser555 I got some errors running cmake. It's fine. I'll use cmitu's incomplete script.