Gauntlet and Gauntlet 2 on lr-fbneo possible bug

stoo

After a bit of effort I managed to build a full lr-fbneo 0.2.97.44 set that scans as 100% complete in CMP.

I've been going through trying out various games and I discovered that Gauntlet and Gauntlet II seem to have a serious bug in the RetroPie build of lr-fbneo:

If you attempt to move to another floor, the new floor will have a corrupt layout and either the player will be stuck in a wall or in an unexitable room, or the game will crash after a short time on the new floor.

This problem seems to be limited to the Pi version of lr-fbneo, as the exact same roms work perfectly in lr-fbneo on RetroArch in Windows 10.

Can anyone confirm this bug? Is it some weird ARM compile optimisation error?

I'm using an RPi3B.

N.B. - I'm aware I can just play Gauntlet and Gauntlet II in pretty much any version of MAME - if it wasn't for the bug being present on Pi but not Windows I wouldn't even post about it.

barbudreadmon

@stoo update your fbneo core from sources and you'll be ok, those bugs were actually fixed 2 weeks ago when @roslof reported them on github : https://github.com/libretro/FBNeo/issues/392 and https://github.com/libretro/FBNeo/issues/393

PS : you'll have to check your romsets again though, since new and/or updated romsets are added every week.

stoo

@barbudreadmon Awesome, thanks.

Is there a changelog anywhere that lists the specific romsets changed since the last "official" release build?

Actually, nvm I'll just scan against the existing set and see what pops up.

stoo

@barbudreadmon All good, rebuilding lr-fbneo from source fixed it as you said. Found the changed/missing roms and got my set scanning perfectly again.

If you don't mind answering one more question:

Cyclone. I see your post from 2018 indicating that it's an m68k dynarec.

I noticed that G-Loc was one of the sets that had changed recently and I'd tried G-Loc just a couple of days ago and found it was kinda slow and needed quite a lot of frameskip.

I just tried enabling Cyclone in G-Loc and wow.. the difference is pretty amazing!

On my overclocked Pi3B:

Cyclone disabled: G-Loc needs heavy frameskip at all times to maintain full speed.

Cyclone enabled: G-Loc runs at a smooth 60fps with no frameskip in most scenes. It drops slightly in the scenes with the cliffs on either side - presumably because there are more sprites to scale - but it's still totally playable.

Is there any downside to using Cyclone all the time? Are there titles that don't work with it?

Edit: I can partly answer my own question: the Sega System-24 games don't start with Cyclone enabled. Which is a shame, because they'd probably benefit greatly from the speedup.

barbudreadmon

@stoo said in Gauntlet and Gauntlet 2 on lr-fbneo possible bug:

Are there titles that don't work with it?

Yeah there are, i don't have a full list but i can mention some :

sega system 24 (you found this one) and probably any other arcade systems using several m68k
sega system 18 and megadrive (m68k worked differently on those systems, so you need another version of cyclone which apparently wouldn't work with "normal" 68k games)
some neogeo games in mvs/unibios, they seem to work with aes though