Some roms not working with lr-fbneo

luckyluca

I have fbneo 1.0.0.01 installed, and used clrmamepro to create a 1.0.0.01 romset using the corresponding .dat file found in the core retropie folder.

All is well, except that some roms are not working with lr-fbneo. For instance aliensyn.zip:

This game hangs on a black screen in retroarch.
Please note the content and crc checks match what the .dat requires. Any idea what might be wrong?

Please see the verbose printout below. (ironically the same rom works with lr-fbalpha2012 and most mame cores). Many thanks! L

video_refresh_rate = "60"
video_fullscreen = "true"
video_fullscreen_x = "1280"
video_fullscreen_y = "720"
arcade
lr-mame2003-plus
/home/pi/RetroPie/roms/arcade/aliensyn.zip
/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2003-plus/mame2003_plus_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/aliensyn.zip"
Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/aliensyn.zip" --verbose --appendconfig /dev/shm/retroarch.cfg
[INFO] RetroArch 1.8.8 (Git 9552f87)
[INFO] Redirecting save file to "/home/pi/RetroPie/roms/arcade/aliensyn.srm".
[INFO] Redirecting save state to "/home/pi/RetroPie/roms/arcade/aliensyn.state".
[INFO] === Build =======================================
[INFO] Capabilities: NEON VFPv3 VFPv4
[INFO] Built: Nov 2 2020
[INFO] Version: 1.8.8
[INFO] Git: 9552f87
[INFO] =================================================
[INFO] Loading dynamic libretro core from: "/opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so"
[INFO] [Overrides] no core-specific overrides found at /home/pi/.config/retroarch/config/FinalBurn Neo/FinalBurn Neo.cfg.
[INFO] [Overrides] no content-dir-specific overrides found at /home/pi/.config/retroarch/config/FinalBurn Neo/arcade.cfg.
[INFO] [Overrides] game-specific overrides found at /home/pi/.config/retroarch/config/FinalBurn Neo/aliensyn.cfg.
[INFO] Config: appending config "/home/pi/.config/retroarch/config/FinalBurn Neo/aliensyn.cfg"
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory

I'm using the following corresponding bios files:
bubsys.zip
cchip.zip
decocass.zip
isgsm.zip
midssio.zip
namcoc69.zip
namcoc70.zip
namcoc75.zip
neocdz.zip
neogeo.zip
nmk004.zip
pgm.zip
skns.zip
ym2608.zip

mitu

Looking at the log file, the core doesn't even get started and the error is solely in RetroArch - maybe a bad game override. Are you using a stock RetroPie image or some 3rd party pre-configured image ?

barbudreadmon

@luckyluca said in Some roms not working with lr-fbneo:

1.0.0.01 ... aliensyn

Turn off hiscores in core options or update to latest FBNeo (i recommend the later), the black screen issue with hiscore enabled on aliensyn was fixed in january.

johnodon

Which romset version should we be using? The Wiki still lists v0.2.97.44.

Clyde

@johnodon You'll have to build your own, since FBNeo is under constant development. @barbudreadmon explained it in this post.

johnodon

@clyde said in Some roms not working with lr-fbneo:

@johnodon You'll have to build your own, since FBNeo is under constant development. @barbudreadmon explained it in this post.

I've built my own set (1.0.0.3) but I thought the set version needs to match the emulator version (like MAME). So that is my question...what version is the the RP FBNEO core at? Is the FBNEO core constantly updated or does it remain static at a certain version?

Clyde

@johnodon As I understand it, the core version isn't as important as the rom's checksums matching the core's dat file. The version numbers of the romsets found on the net should just say that the set was built using the specified version's dat file.

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

New code is commited on a daily/weekly basis

and

the latest version is unofficially branded as 0.2.97.44, but keep in mind that it was already the case 9 months ago, a "full romsets" from 9 months ago is different from a "full romsets" today though.

So, if I understand it correctly, the fbneo core's version number doesn't say much about the romset currently needed.

But since all that is just my interpretation, I'll leave it to @barbudreadmon to clarify this. 🙂

barbudreadmon

@johnodon said in Some roms not working with lr-fbneo:

Is the FBNEO core constantly updated or does it remain static at a certain version?

It is constantly updated, so every time you update the core you have to verify your romsets. The version number is just something we bump from time to time : even numbers when we want to do a "snapshot official release", odd numbers when we go back to an ongoing wip, meaning 1.0.0.03 is the ongoing wip and as such get romset updates/additions every few days.

johnodon

@barbudreadmon said in Some roms not working with lr-fbneo:

@johnodon said in Some roms not working with lr-fbneo:

Is the FBNEO core constantly updated or does it remain static at a certain version?

It is constantly updated, so every time you update the core you have to verify your romsets. The version number is just something we bump from time to time : even numbers when we want to do a "snapshot official release", odd numbers when we go back to an ongoing wip, meaning 1.0.0.03 is the ongoing wip and as such get romset updates/additions every few days.

Talk about timing...

I was just testing random roms and was presented with this when trying to launch 1944:

That's a nice addition that I have not seen before (but I also haven't touched my cab in 6 months or so). I was still on the v0.2.97.44 romset. I dropped in my rom from my 1.0.0.03 set and working as expected.

I'll do the same with the remaining FBNEO roms and do a quick check with clrmamepro to see where I stand.

Thanks guys!

John

luckyluca

@clyde I went through the exact same process, the crmamepro compatible dat files can be found here: /opt/retropie/libretrocores/lr-fbneo/dats/ (thanks barbudreadmon). You can then use clrmamepro to rebuild a bespoke set for the exact version of lr-fbneo in use.

@barbudreadmon @mitu turning off highscores in the core options file solved it! thanks a lot for the tip.

The only reason why I haven't updated the core yet, is that I don't know if doing so might affect other systems I already built, and would necessitate updating their roms too (neogeocd for instance, and anything else I might not think of right now).

barbudreadmon

@johnodon said in Some roms not working with lr-fbneo:

That's a nice addition that I have not seen before

Yeah, i implemented that message 2-3 months ago, i believe that's a change for the better, even if some users still don't understand its meaning, or even complain about it.

barbudreadmon

@luckyluca said in Some roms not working with lr-fbneo:

The only reason why I haven't updated the core yet, is that I don't know if doing so might affect other systems I already built, and would necessitate updating their roms too (neogeocd for instance, and anything else I might not think of right now).

Your version is over 6 months old, so no doubt there will be romset updates/additions (we probably added over a dozen of new systems since then), neogeo cd won't be a problem though.