Welcome!
Final Burn Neo => FBN Discussion => Topic started by: antiriad on August 29, 2021, 05:54:03 PM
-
Hi,
I'm running Lakka 3.3 on my RPi4, and I get a "driver initialization error" when I try to run Growl/Runark in FB-Neo.
My romset should be OK (verified in Romcenter with latest DAT) maybe there's an issue with the Taito F2 driver?
Thank you so much.
-
Hi antiraid,
Growl/Runark is working fine here. Please take a look at the log file, it should give some more info on what is wrong. The 2 main things that would cause init to fail are: unable to allocate memory for the system and a missing file in your romset.
best regards,
- dink
-
Hmm that's strange, ROM should be OK and RPi4 should have enough memory to run it.
I'll test it also on Windows stand-alone ASAP. Meanwhile may I ask what's the log path for the libretro core?
BTW: latest official release is 1002 or 1003? Thank you so much.
-
I get a "driver initialization error" when I try to run Growl/Runark in FB-Neo.
Do you mean "Failed initializing driver" ? I think that error message can only happen on a failed memory allocation (usually meaning not enough ram). A bad romset would give another error message. But there is also the very rare case where the romset is detected as "good" (crcs/sizes can be read and match) but somehow the archive can't be read properly when the emulator actually try to load the roms into memory, i remember it happened to a user once, it would probably gives the same error message.
Other possibility : there is some bug with the old FBNeo version lakka is using.
Current WIP is 1.0.0.03 (odd numbers are WIP), latest release is 1.0.0.02 (even numbers are releases).
-
Current WIP is 1.0.0.03 (odd numbers are WIP), latest release is 1.0.0.02 (even numbers are releases).
That's strange, I remember that the core in Lakka (with no changes on my part) is 1.0.0.03, but is it possible that Lakka uses WIPs?
I will check again tonight and I'll also try the same romset on Windows.
-
is it possible that Lakka uses WIPs?
Yes, the WIPs they are using are always a bit outdated though, and it doesn't seem there is an easy way to update to our latest version, which is a bit annoying since we regularily get reports about lakka bugs that already got fixed in our current builds.
-
Yes, the WIPs they are using are always a bit outdated though, and it doesn't seem there is an easy way to update to our latest version, which is a bit annoying since we regularily get reports about lakka bugs that already got fixed in our current builds.
May I download the source from https://github.com/libretro/FBNeo and build with make -j5 -C src/burner/libretro/ platform=rpi4 ?
Thank you so much.
-
Sure - give it a try.
best regards,
- dink
-
Great!
The optimizations you suggested in the other thread are also valid for the RPi4?
CFLAGS += -O2 -DNDEBUG
CXXFLAGS += -O2 -DNDEBUG
and change to:
CFLAGS += -O3 -DNDEBUG
CXXFLAGS += -O3 -DNDEBUG
Do they break compatibility with some titles?
Golden Axe 2 Revenge of the Death Adder seems slow even on RPi4 so I'd like to squeeze as much as possible!
Thanks.
-
-O3 is already the default optimization for the libretro core, no need to change it.
For FBNeo's segas32 on pi4, you'll need to overclock it and maybe enable some frameskip too.
-
I built the latest version of lr-fbneo for RPi4 and fixed also the problem with Growl (one rom was corrupt indeed!).
Thank you so much! :biggrin:
-
glad it worked out :)
best regards,
- dink