Goodbye fbalpha, welcome fbneo
-
@roslof
A clever use of grep and cut will produce a one word per line list of strictly the rom names.After that there are probably numerous ways to compare them. I would likely use Excel (Calc) to paste the two lists into two columns and then use a formula with a combination of IF and VLOOKUP to display a blank cell in column 3 if the value in column 2 is found within column 1, else display the rom name in column 3.
Alternate method might be if you already use clrmamepro you can just insert the new .dat file and let it tell you what you are missing. I believe wholly missing roms show up differently than roms with a file or two mismatch indicating they have been redumped.
-
This was quick and dirty for fun as I had something close already written in Python but there might be mistakes. :) I did a straight compare between the DAT from may 1st, 2021 and the current one (3 days ago). Game ROM names only no BIOS files, if they changed even.
I came up with 352 additions (that does count games that were renamed so the real number might be a bit lower). Something for example like
bloodstm10renamed tobloodstm104, it's going to count it as new.Comparing them in reverse I came up with a list of 25. I would assume these are the games that were renamed or possibly removed from FBNeo. The lists are below.
New and renamed games:
3in1semia aa akatana aliens4 alpha1v armwarb astyanaxa asukaja asurabusj asurabusja asurabusjr atombjt bace batsugunc blastero blazstarcm bloodbrom bloodstm104 bloodstm110 bloodstm210 bloodstm220 bloodstm221 bloxeedc bloxeedu borench borencha borenchj brkthrubl brkthrut bronx bublbust bucanera cadashgo chinhero chinhero2 chinhero3 chinherot cityatta cnbe2018 colt column2j columns2 columnsj columnsu crashh crshrace2a crush3 ctower cybotsam cyclemb cyclshtg dderby ddpdfk ddpdfk10 ddpsdoj deathsml devilfshg devilfshgb dfkbl dicegame dietgoea discoboy discoboyp dkfreerun dkongbp dkongbp1 dkongchm dkongchm1 dkongitd dkongss dkongst dkongst2 dkongtj docastle2 docastleo dogyuunb dokaben2 dorunrun2 dorunrunc dorunrunca doubledrsp douni dsmbl dynamski earthjkrb emeraldah espgal2 espgal2a exerion exerionb exeriont finalap2 finalap2j finalap3 finalap3a finalap3bl finalap3j finalap3jc finallap finallapc finallapd finallapjb finallapjc finger floritas floritasm fourtrax fourtraxa fourtraxj futari10 futari15 futari15a futaribl futariblj galpaniex galpaniska harem headonch heiankyo hiryuken hotminda hsf2pp hypernoid ibara ibarablk ibarablka ichir ichirbl ichirj ichirjbl ichirk irion jojobanrb kangarool kchamptec kf2k3ps2sp killbld100 kof2001ru kof2002ps2 kof2k1rp kof2kxxx kof97ip kof97tp kof98bc2nd kof98eckg kof98ecky kof98ratio kof99eur2 kov21022 kov2dzxx kovassge kovassgn kovlsqho kovplus12dw kovplus20tx ktiger2p lazybug legionj2 looptris magicstk magmaxa majest12ua majest12ub marblmd2 megrescu midres2 mirninjaa missile missile1 missile2 mmpork mooncreg2 mototoura mrsdyna mslug2unity mslug3unity mslug4a mslug4lw mslug4unity mslug5unity mslug5wd mslughb mslugunity mslugxunity mspacmanlai mspactwin mushisam mushisama mushisamb mushitam mushitama namenayo neopang nitrobalb nostromo nsub nycaptor oldsplusok olibug ooparts orlegendea outfxiesja pacminer painter pcktgal pcktgal2 pcktgal2j pcktgalb pengo6 pinkswts pinkswtsa pinkswtsb pinkswtssc pinkswtsx playball potopoto powerbal punisherhr punisherly puyo puyobl puyoj puyoja puyopuy2 pzlbreaka radarscpc raflesiau redclash redclashs redclasht redclashta redhawksa redufob3 ribbit ribbitj roboarmya rodlandjb2 route16d ryourano samuraij saurobl sdojak seawolft sengoku3eb sf2amf10 sf2amf9 sf2rk2 sfiii2h sformulaa sfz2alr1 sfz3mix shangkid shoottv silkwormb2 skydest skysharkb sokoban soniccar sonicfgt sotsugyok spcmission speccies spf2xpri spiero spinlbrkup spool3 spool3i sqij ssf2us2 ssf2xjr1trn ssonicbr stkclmns stkclmnsj striderfix supershp suprmatk suprmatkd suzuk8h2 suzuk8h2j suzuka8h suzuka8hj svghk tail2nosa tantr tantrbl tantrbl2 tantrbl3 tantrbl4 tantrkor tdragonb3 tempall temped temptwst tfrceac tfrceacb tfrceacj tfrceacjpb timekill120 twinsqua umk3uk vbrakout vsbattlecity vscastlevania vsclucluland vsdrmario vsduckhunt vsexcitebike vsfreedomforce vsfrombelow vsgoonies vsgradius vsgumshoe vshogansalley vsiceclimber vsmachrider vsmightybomjack vsninjajkun vspinball vsplatoon vsraidbbay vsrbibbal vsslalom vssmb vssmgolf vssmgolfla vssoccer vsstarluster vssuperskykid vssuperxevious vstetris vstkoboxing vstopgun wavybug wbmlbg wbmlbge wbmld wbmljod wbmlvcd wofabla wrallyc wwallyja3p wwfmanac wwmarine xenocrisis xmvsfcph xsleenab xsleenaba zerohour zerohoura zerohouri zolapac zunkyouReverse compare (possible renamed games or removed from FBNeo altogether):
asurabusa devilfsg kf2k2ps2b kinst kinst13 kinst14 kinst15ai kinst2 kinst210 kinst211 kinst213 kinst214ai kof97inv kof97t2020 kof98eck20 kof98eckvs kof99rp2f kovassga kovplus2020tx ltorb1 roboarma spcdraga spinlbrkjp umk3pb1 umk3uc -
@Riverstorm Let's continue the discussion from mame2003+'s topic here, i did a few changes and the raster/vector info is now available in our dats. FYI i added the geometry info last year by user's request.
Afaik Killer Instinct is the only game that was ever removed from FB, so i'd assume the other games were renamed.
-
@barbudreadmon & @Riverstorm Sorry to interrupt - but for a personal project of mine (started aeons ago) where I am converting mame/FBN xmls t via python into csv/xlsx into human readable columns I am interested in... (short rant: ever changing xml struct, I never found a reliable source for the changes, and what each entry really mean...), but I am curious - ever since (listxml was possible) in mame - they differed in screen vector or raster, later lcd,svg and maybe others where added... but whenever mamedat/xml is refering to screen = vector, width and heigth (x/y pixel resolution) is ommited (makes sense IMHO), but FBN is providing such (well, maybe an artifact before type vector was added, as it was provided before for vector games)... is the (previous) x/y-data for vector games of any use and how could it be utilized? Or was it just a necessity out of not differing between raster/vector?
-
@barbudreadmon - That looks amazing! You're amazing!! I very much appreciate the addition and completeness of the geometry information I know you don't need to look inside a DAT to utilize it but I find myself always looking inside DAT's. There is always extraneous information that is useful beyond the core info. needed to build sets.
I did a quick once over and the only thing that flagged for me was
aztarac. It's listed video type is raster. I've played it several times and always think of it as a vector game but you never know.@Ashpool - Yeah that threw me too like LCD, on and on etc. but some actually had an LCD along with the regular screen.
With vector games I basically think--infinite resolution (no pixels). They had a start and end point for each line but not a resolution. You probably know all that though since you been digging through DATs a long time.
Barbudreadmon might know better since emulated vector games truly aren't running on vector monitors for most of us (I would assume). So with that thought they probably needs some type of "boundary" defined with the (pixel) resolution or something to that effect. That's just a guess at best but I know what you mean with it being omitted in MAME. I am curious myself now.
@barbudreadmon - Thanks again cheers to you and the team--we have to get you a beer or two or three or a 6 pack for the amazing emulator and support! :)
-
Yeah I think they have just been renamed (besides Killer Instinct & Killer Instinct 2). Just a few examples of the short list of 25 comparing the 2021-05-01 to the current DAT.
Old name:
kof98eck20 kof98eckvs kof99rp2f umk3pb1 umk3ucNew name:
kof98eckg kof98ecky kof99rp umk3p umk3uk -
@Ashpool this is the default width/height at which we emulate those vector games (meaning if you don't turn on the hires dips), i intend to keep it like this for now.
@Riverstorm said in Goodbye fbalpha, welcome fbneo:
I did a quick once over and the only thing that flagged for me was aztarac. It's listed video type is raster. I've played it several times and always think of it as a vector game but you never know.
And you are absolutely right, i added the
GBF_VECTORflag to several dozens of games yesterday but it seems i missed 2 boards, it should be ok now, thanks for the report ! -
@barbudreadmon said in Goodbye fbalpha, welcome fbneo:
@Ashpool this is the default width/height at which we emulate those vector games (meaning if you don't turn on the hires dips), i intend to keep it like this for now.
:up: as it has a real meaning, I am all in for keeping that information "\o/"
Edit: As I, so far just used (with a few exceptions) FBA/FBNeo just for Neogeo roms and due to your discussion with @Riverstorm over at the other thread and here (M2k3+), I am inclined to reconsider my personal evaluation/stereotype of speed over accuracy in regards to FBN and I 'am therefore stepping back from those thoughts of preferring mame cores over FBN ones by now because of accuracy assumed.
Now to that hires dip ;> I've read about it on the FBNEo libretro pages, but I am missing further informations beyond the "1080p" datum. Does it mean that previous 800x600/600x800 / 640x480/480x640 information should be treated as 1440x1080 for 4:3(H) and 810x1080 for 3:4(V) in Applications which are utilizing/queriieng that info (usable then with an option of true/false dipswitch set: aka -> use dat size, or 1080p one)? -
@barbudreadmon - Cheers, it looks spot on now! If I see anything else that looks off I let you know and many--many thanks for adding that last bit of geometry information. It looks spectacular and will come in very handy! :)
-
@Ashpool - I don't know if it would help, but jump into a few of them and poke around in the menus. The resolution is in there somewhere. Then turn on a hires dip and check it again. I had a few questions and it really helped in understanding what was going on.
I agree I would definitely lean toward accuracy over speed in an emulator but if the accuracy is hindering performance enough maybe a performance based emulator might be preferred. I had a bunch of games that I was on the fence about and finally just tried them in both to help make a decision.
I wish there was a slam dunk emulator for every game but some games you have to use alternative emulators if you want to play...well, hmmm, at least until FBNeo emulates them all... ;)
-
@Ashpool said in Goodbye fbalpha, welcome fbneo:
Does it mean that previous 800x600/600x800 / 640x480/480x640 information should be treated as 1440x1080 for 4:3(H) and 810x1080 for 3:4(V) in Applications which are utilizing/queriieng that info (usable then with an option of true/false dipswitch set: aka -> use dat size, or 1080p one)?
Indeed, but i wouldn't recommend using the hires dips on pi4 with FBNeo, you'll likely run into performance issues.
Advmame is the recommended emulator for vector games on retropie, it does a far better job at performance and has features we don't for customizing visuals.
-
@Folly @barbudreadmon @Riverstorm Awesome this is great information to have, much appreciated! I'm definitely going to update fbneo and my romset, but it's great to know which new game additions to look for and play around with. I have never played some of these CAVE shooters and look forward to trying them out. Thanks for helping out with this!
-
@barbudreadmon Don't know if this should go here or in its own thread/report, but I discovered something weird: in
snowbro2, when I change the dipswitches for the coinage settings (through RGUI), then save, exit and relaunch the game, the left direction on my joystick stops working. Changing the dips back and relaunching solves the issue. Is it a bug? -
@WeirdH Thanks for the report, i have one good news and one bad news. The good news is that the issue should be fixed. The bad news is that this game is one of the few using conditional dipswitches (in this case, "Territory" is supposed to control which pair of "Coin A" / "Coin B" is available), and i never found a way to make those work properly due to how the libretro api works.
-
@barbudreadmon Well, as long as things still work without having to endure the god awful US/EU character selection screen, you won't hear me complaining.
Coinage options also aren't really that important to me, but I just stumbled upon this little quirk while fiddling around, so I thought I'd mention it.
EDIT: Confirmed fixed and working for me. Region was set to SE-Asia (gives English text and original character select), changed player 1 coinage setting, smooth sailing.
-
@WeirdH I was thinking about those conditional dips for the past few days and finally managed to get them working. It's still kinda awkward though with that libretro core option list working somehow asynchronously, and the conditional dips sometimes requiring a restart to work properly. But that's the best i can achieve with the tools i have at my disposal.
-
So I updated to the latest binary for the libretro version, and I notice none of my CV1K games save their diagnostic settings. IE, lowered difficulty, 9 credits instead of 1, etc.
I know that a month or so back, the driver was updated to add speed hacks. Did something break in the meantime, or do I need to delete save files somewhere?
-
@dodonpachi due to multiple requests about this, i recently migrated FBNeo nvrams from the older headered/compressed format to a raw format closer to MAME's, it turns out my migration process didn't handle several cv1k games properly due to some unusual nvram behavior.
The fix is on git, thanks for the report. -
@barbudreadmon just downloaded the latest binary from retropie setup, and can confirm the in-game options are saving again! Thank you for the swift fix!
-
Regarding CV1000 games, I'm experiencing a strange behavior.
The first time I run a CV1000 game, it works as expected: near full speed with default 100% cpu in the core options, and almost perfect full speed if I change the core cpu % by the suggested value.
However, the second time I run the same game, fps are halved (around 33 fps) and audio drops are extreme. Also, core cpu settings do not seem to have any visible effect. I have tried saving per game core settings or not, but the problem remains. The only thing that remedies the problem is removing the .fs file for that game in the fbneo directory. Then, the game runs well again, until I run it a second time (after fbneo creates again the .fs file).
I'm using the latest fbneo binary, but I have experienced this problem in previous versions too, since when CV1000 support was added. I'm also running the latest Retropie version on a Pi 4, 4Gb.
Does anyone encountered a similar problem?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.