Goodbye fbalpha, welcome fbneo

barbudreadmon

@g30ff Only the support for "Vs. Unisystem" was added, support for the few games running on "Vs. Dualsystem" (2 linked nes) wasn't implemented, i doubt it will in the near future because it'll require some major rewrite of our nes driver (current driver doesn't allow to run 2 nes instances at once).

G30FF

@barbudreadmon Aah. I actually didn't realize those were separate things, but yeah, all of the games I see missing have two screens. Thanks for that!

I've tried out all of the games, and these are the only issues I noticed.

vstetris: Player 1 controls don't seem to work. If I start up a 1 player game, I have to set my input to player 2 for the game to register my inputs.
vsfreedomforce: I got a game over, and the game hung. It didn't take me back to the title screen. However this only happened once, and I couldn't get it to happen again.

Overall, excellent work!

barbudreadmon

@g30ff Thanks for the reports !

I fixed the issue for vstetris.

For vsfreedomforce, are you talking about a black screen where you can still move gun cursor ? Did it happen right after inserting coins ? I got a bug like this, but i'm not yet sure what this is about, it could even be something happening on original game.

G30FF

@barbudreadmon I tested the fix for vstetris, and it works now!

For vsfreedomforce, it was the same experience you described, but after the game over screen disappeared, not right after inserting coins. Not sure if it's a bug with the actual original game or not. Sorry I can't be more helpful, I wasn't able to reproduce it after the first time it happened.

barbudreadmon

@g30ff most likely, the random issue with vsfreedomforce is fixed.

G30FF

@barbudreadmon Updated. If it happens again, I'll let you know.

WeirdH

Two Konami beat 'em ups exhibit fairly isolated performance issues on my Pi 3B+:

asterix becomes stuttery in level 2, maybe due to the background effect of air swirling in the heat

moomesa does the same when the attract mode gets to a boss fight with a floating platform

Apart from these instances, the games seem to run fine, so are these emulation issues, or is the 3B+ just too slow and obsolete by now?

barbudreadmon

@weirdh those are called raster effects and are usually quite demanding, their proper emulation is one of the main reasons recent'ish arcade cores are slower than the old ones

WeirdH

@barbudreadmon Okay, good to know, thanks. Will a Pi4 have trouble with these effects as well? Or is it all different on a per-game basis? I remember tophuntr having issues with the bonus level transition effect on Mame2003-plus, but it works fine on FBNeo.

G30FF

@weirdh Tried it out on my Pi 4, and I don't see any problems with the games you mentioned. I don't have any overclock settings, and am using default FBNeo settings for them. Most games I've tried work in FBNeo on the Pi 4 stock, some (like Sega system 32 games) require a frameskip setting of 1 frame enabled to play at full speed, and there are a few games I've tried that are just too laggy to play even with frameskip, but work in lr-mame2016 instead (for example, gametngk and tetrisp).

Addison

Hi.

Is it possible to load lua training scripts?

Here's a collection for many supported titles:

https://github.com/peon2/fbneo-training-mode

barbudreadmon

@addison No, that stuff only works on FBNeo standalone (windows), RetroArch doesn't offer any kind of support for lua.

barbudreadmon

Yet another very popular system was added to FBNeo : Sega C/C2. Original announcement at https://neo-source.com/index.php?topic=980.msg33258#msg33258. This one is especially known for its puzzle game classics (Puyo Puyo, Columns, ...).

G30FF

@barbudreadmon Very exciting news! I've taken a bunch of games from the set out for a spin, and haven't noticed any issues so far! Thanks!

dodonpachi

Updated from binary, and now ddpdojblk gives me a black screen with "ROM ERROR !" It worked fine prior to updating. What happened?

EDIT: deleting the ddpdojblk.fs file in roms/arcade/fbneo fixed it. Game works now.

barbudreadmon

@dodonpachi This romset was updated to a newer revision in https://github.com/finalburnneo/FBNeo/commit/1876e6d4ab373d224b1b450105fd173b3f42f0fe

The new one apparently uses a different protection for nvram, so loading a nvram from the older revision probably doesn't work, thanks for the heads-up.

Note : i don't recommend updating from binary.

sirhenrythe5th

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

@dodonpachi This romset was updated to a newer revision in https://github.com/finalburnneo/FBNeo/commit/1876e6d4ab373d224b1b450105fd173b3f42f0fe

For everyone searching this romset: the one for MAME 0.239 does the job ;)

Red_Trev

@sirhenrythe5th does any other ROM from MAME 0.239 work with finalburnNEO ?

barbudreadmon

@red_trev said in Goodbye fbalpha, welcome fbneo:

@sirhenrythe5th does any other ROM from MAME 0.239 work with finalburnNEO ?

read top post.

Red_Trev

@barbudreadmon said in Goodbye fbalpha, welcome fbneo:

See https://www.libretro.com/index.php/goodbye-fbalpha-welcome-fbneo/

New code is commited on a daily/weekly basis, which includes :

support for new games

better emulation for already supported games

fixes for reported issues

regular romsets syncing with latest known MAME dumps (MAME 0.210 at the time i write those lines, but it changes every few months)

Up-to-date clrmamepro dat files are always available at https://github.com/libretro/FBNeo/tree/master/dats

The best way to get valid romsets is to use clrmamepro with a previously valid FBNeo/FBAlpha full romset & the latest MAME dumps as sources.

If you are too lazy to keep your romsets up-to-date, never update your FBNeo core (ofc, never complain about issues either). People think it's time-consuming, honestly it's not : i would be surprised if i spent more than 1 hour a year to keep those updated, ofc you'll need a supply of fresh MAME dumps.

There is a FAQ at https://github.com/libretro/FBNeo/blob/master/src/burner/libretro/README.md

I installed RetroPie maybe 18 months ago and have not updated FBNeo since. I obtained my FBNeo compatible ROMs at the same time.

If I update FBNeo to the latest version, will these ROMs cease to work ?