NAOMI 2: Error selecting BIOS by LB/BB for Virtua Fighter 4 Final Tuned (Retroarch/Flycast core)

[JaredN]

Hello,

This is a problem I've been experiencing for quite a few versions of LB/BB, but I hadn't reported it because I thought the issue was with RetroArch and not LB/BB.

I noticed this problem after updating my RetroArch cores. Virtua Fighter 4 Final Tuned (Naomi 2), which had been working fine until then, displayed an error message when I started it up. I also noticed that the word “Network” was no longer displayed under the Naomi 2 logo. I solved this problem by reverting to an earlier version of the Flycast core.

Recently, I noticed that RetroArch launched Virtua Fighter 4 Final Tuned correctly with an updated Flycast core, BUT the problem occurred as soon as I launched the game from LB/BB.

Note that I don't have this problem with any other Naomi 2 games (nor have I noticed it on Dreamcast games, Naomi or Atomiswave). I also believe that VF4 Final Tuned is the only Naomi 2 game with network capabilities.

My interpretation is therefore that when LB/BB launches the game, the BIOS selection is not done via RetroArch and an incorrect BIOS is selected by LB/BB.

Shown in the video:

- RetroArch: information about the updated core (all bios present)
- Launching VF4 FT via RA: OK, Naomi2 Network logo
- LB: Displaying RA version info and plugins
- Launching VF4 FT via LB: Bios error, Naomi 2 logo (no “network”)
- Launching another Naomi 2 game: OK
- RA: Restoring an older Flycast core, core information
- Launching VF4 FT via LB: OK, Naomi 2 “Network” logo

Thank you very much for your work!
LB/BB is amazing.

[sundogak]

2 hours ago, JaredN said:

Hello,

This is a problem I've been experiencing for quite a few versions of LB/BB, but I hadn't reported it because I thought the issue was with RetroArch and not LB/BB.

I noticed this problem after updating my RetroArch cores. Virtua Fighter 4 Final Tuned (Naomi 2), which had been working fine until then, displayed an error message when I started it up. I also noticed that the word “Network” was no longer displayed under the Naomi 2 logo. I solved this problem by reverting to an earlier version of the Flycast core.

Recently, I noticed that RetroArch launched Virtua Fighter 4 Final Tuned correctly with an updated Flycast core, BUT the problem occurred as soon as I launched the game from LB/BB.

Note that I don't have this problem with any other Naomi 2 games (nor have I noticed it on Dreamcast games, Naomi or Atomiswave). I also believe that VF4 Final Tuned is the only Naomi 2 game with network capabilities.

My interpretation is therefore that when LB/BB launches the game, the BIOS selection is not done via RetroArch and an incorrect BIOS is selected by LB/BB.

Shown in the video:

- RetroArch: information about the updated core (all bios present)
- Launching VF4 FT via RA: OK, Naomi2 Network logo
- LB: Displaying RA version info and plugins
- Launching VF4 FT via LB: Bios error, Naomi 2 logo (no “network”)
- Launching another Naomi 2 game: OK
- RA: Restoring an older Flycast core, core information
- Launching VF4 FT via LB: OK, Naomi 2 “Network” logo

Thank you very much for your work!
LB/BB is amazing.

Two things to try.  

1) Make sure you have current NAOMI bios set (naomi.zip and naomi2.zip) in your RA system/DC directory. I know the standalone flycast recommends using current ROMs from MAME. I have 281 MAME set and no issues with VF4 Tuned.

2) Corrupt or incorrect nvmem file. Remove the nvmem file in RA and resave settings via Naomi (in game) system menu. If it was working with old core and not the new core maybe something changed in how core manages and/or corrupted (seen with MAME games on occasion). Admittedly, doesn't quite make sense that would be the issue as the bios should still be unaffected either way but worth shot.  Plus, re-saving the system settings will see if anything amiss there. 

 

I have network turned off in settings and still see the BIOS start with Naomi "Network" on logo. 

 

 

 

[JaredN]

1 hour ago, sundogak said:

Two things to try.  

1) Make sure you have current NAOMI bios set (naomi.zip and naomi2.zip) in your RA system/DC directory. I know the standalone flycast recommends using current ROMs from MAME. I have 281 MAME set and no issues with VF4 Tuned.

2) Corrupt or incorrect nvmem file. Remove the nvmem file in RA and resave settings via Naomi (in game) system menu. If it was working with old core and not the new core maybe something changed in how core manages and/or corrupted (seen with MAME games on occasion). Admittedly, doesn't quite make sense that would be the issue as the bios should still be unaffected either way but worth shot.  Plus, re-saving the system settings will see if anything amiss there. 

 

I have network turned off in settings and still see the BIOS start with Naomi "Network" on logo. 

 

 

 

Thanks for your reply! 👍😉

I just double-checked.

The BIOS files are correct and in the right place.

And I deleted the nvmem file, but there's no change to report.

VF4 Final Tuned works when I launch it directly from RetroArch, regardless of the Flycast core, old or new, without using LB or BB as a frontend.

The network option was already disabled in the game settings.

“Naomi 2 Network” appears when I launch it without the LB/BB frontend, and it works.

“Naomi 2” alone appears when I launch it through LB/BB, and the BIOS causes problems in this case.

For me, the logical explanation would be found in the way LB/BB interacts with RetroArch and the Flycast core during launch, which would cause problems with the new kernels but strangely not with the old ones.

But it's weird in this case that it works for you. 🤷‍♂️

Edited Friday at 08:04 PM by JaredN

[sundogak]

Well would try removing that game from LB and reimporting to make sure no spurious commands lurking. Also check that no spaces at end of path as seen LB do weird things there:

C:\game \game.zip

Barring that, not sure. However, I don't think it is an interaction issue within LB itself as Flycast RA core is relatively simple with no switches needed and no special commands for that game (and [non-helpfully] launches fine on my setup with current RA core, LB version, etc). I have only ever seen a similar DIMM error (although not identical to yours) and the network portion not showing in startup when there is nvram issue.

[JaredN]

2 hours ago, sundogak said:

Well would try removing that game from LB and reimporting to make sure no spurious commands lurking. Also check that no spaces at end of path as seen LB do weird things there:

C:\game \game.zip

Barring that, not sure. However, I don't think it is an interaction issue within LB itself as Flycast RA core is relatively simple with no switches needed and no special commands for that game (and [non-helpfully] launches fine on my setup with current RA core, LB version, etc). I have only ever seen a similar DIMM error (although not identical to yours) and the network portion not showing in startup when there is nvram issue.

I just tried removing the ROM and reimporting it, without success. I also checked the file path. Nothing to report. 🤔

Assuming that the problem could be caused by an interaction between LB and RA, with RA finding the “right” BIOS to use and LB not, I copied all the files from the two BIOS zip files into “vf4tuned.zip” and... surprise... it works! 🎉

I imagine that in this case, LB doesn't need to “find” the right BIOS in the “Naomi” and ‘Naomi2’ zip files in “retroarch\system\dc” since it has them all available in the ROM zip file.

If I just copy the files from “Naomi2,” it doesn't work. Just the ones from “Naomi” don't work either... I have to copy the contents of both!

And if I keep two files, “Naomi.zip” and “Naomi2.zip,” but merge their contents, creating two identical zip files in “retroarch\system\dc,” with all the BIOS files in each, it still doesn't work!

My ROMs and BIOS files were cleaned with Romcenter, using a Mame 0.220 DAT, without merging them.

One explanation for the fact that without this “manipulation,” VF4 FT does not detect a valid BIOS when I use Launchbox as a frontend, but that it works for you, could perhaps be that the necessary files are present in your original “vf4tuned.zip” and not in mine ? 🤔

In this case, it would indeed be a problem in the interaction between RA and LB when launching VF4 FT, since launching directly via RA, without going through LB, does not cause any problems with my original files.

In my opinion, this problem could be due to a change in the way the specific “network” BIOS of VF4 FT is managed in newer Flycast cores, since it does not occur on my system with older ones.

But I could be wrong ! 😅

Anyway, it's not a big deal since I found a solution, even if it's a bit of a “hack” ... 

In any case, thank you very much for taking the time to look into it and reply to me! 👍😉

Edited Friday at 10:57 PM by JaredN

[sundogak]

Glad you got it all working. RA, MAME files, and BIOS files are always a bit of dark art at times.