-
Posts
33 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
JaredN's Achievements
8-Bit Processor (3/7)
21
Reputation
-
Thanks for the advice, but that's already what I did. đ€·ââïž
-
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! đđ
-
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. đ€·ââïž
-
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. Enregistrement de l'Ă©cran 2025-10-24 163638.mp4
-
Hello, Here is a list of a few issues I noticed in beta 1 and beta 2. All of them are shown in the video I'm attaching, except for the last one. - The screensaver no longer systematically âskipsâ a game, BUT it still does so for the first game it displays when it launches. No big deal, really, but I'm reporting it in case it helps. - An issue I had already reported but which has not been corrected here: When the video format is set to WMP, the prioritization of the soundtrack music over the video audio blocks the video sound in the screensaver. This is not the case when I use FFmpeg (which unfortunately continues to cause me trouble). - Prioritizing the soundtrack music over the video audio is not respected in the screensaver. I don't know if this is an issue or ânormalâ behavior, but I would like to be able to keep this option in the screensaver as well. - And finally, the only issue I can't show in the video is that LaunchBox AND BigBox freeze and close randomly and without error messages when I use FFmpeg. I'm using an RTX 3060 Ti with the latest official NVIDIA drivers (GeForce Game Ready 581.57). Thanks again for all your hard work! LaunchBox is amazing! Enregistrement 2025-10-24 103335.mp4
-
Hi @AstroBob Here's another problem I'm having with the screensaver that I didn't notice right away. It only happens with WMP. (As mentioned in another post, I'm still having random crashes with FFmpeg. The application, BB or LB, closes without any error message.) I use a playlist as background music (LaunchBox\Music\Background) and I have configured BigBox to give it priority over the sound from videos. The problem is that when I launch the screensaver, the music stops, BUT the video sound does not take over. When I exit the screensaver, a new song from my playlist starts playing. So the screensaver stops the music, but the video sound remains muted. When I disable the option to prioritize the soundtrack over the video sound, or when I use FFmpeg, the video sound plays normally. Personally, I would prefer my background music to continue playing, taking priority over the video sound, as I have chosen (I think this was the case in version 13.23), but the worst thing is to have neither music nor video sound... Thank you again for your answers and all the work you have done! LaunchBox/BigBox is incredible! Enregistrement de l'écran 2025-10-06 071700.mp4
-
Thanks ! đđ
-
LB and BB (13.24) keep randomly crashing with FFmpeg (RTX 3060 Ti)
JaredN replied to JaredN's topic in Troubleshooting
One of two video decoding options provided by LB and BB, the other being Windows Media Player. đ -
The screensaver systematically skips one game before displaying the next. Always just one game. This behavior is consistent regardless of the selected theme or video format. This is illustrated at the beginning of the attached video and at approximately 30 seconds. Screensaver issue.mp4
-
Big Box Crashing After Around 2 Minutes of scrolling....
JaredN replied to DonellHD's topic in Troubleshooting
Same problem here, different theme. đ«€ -
Hello @djweevil666 Sorry, I'm not very present on the forum and I only see your question now. First of all, you need to have faeran's VisioN theme installed. Then, there are two possibilities. The simplest: In LaunchBox, via the âeditâ menu of the playlist (or platform or platform category), use the right-hand pane (+) to add the desired image, identifying it as âfanartâ and the logo as âclear logoâ. This works very well, but the fanart will also be used for other themes, if you use others, and the dimensions are not necessarily suitable. And if you have several fanarts for the same playlist, they'll be chosen randomly in BigBox, and personally, I don't like the effect when scrolling. On the other hand, this is the method I use for logos. The other method, the one I use, is to copy the fanarts you're interested in directly into Launchbox's âLaunchBox\Themes\VisioN\Images\Playlists\Fanartâ folder, making sure to rename the files so that they have exactly the same name as your playlists. Ditto for platforms or platform categories by choosing these sub-folders in âLaunchBox\Themes\VisioN\Imagesâ. This also works for logos, if you want a finer customization, depending on the theme you're using. Any fanart or logos you place in these folders will automatically be imposed and the theme will use them instead of those you might have added using the first method. The fanarts can of course be used for other themes, but they are specifically cropped for the âplatform wheel 1â display of faeran's VisioN theme on a 16/9 screen. In short, you can use logos and fanarts with any playlist (however you created it and whatever its content), platform or category of platforms, provided you either use the first method to import fanarts and logos, or match names and folders if you use the second. There you have it, I hope this answer helps, and I apologize again for the late reply.
- 5 comments
-
- 1
-
-
- playlists
- collections
-
(and 3 more)
Tagged with:
-
I love this theme, which has become my main theme since it came out. Many thanks for this incredible work, @faeran ! For those who might be interested, I've just uploaded to the âplaylist backgroundsâ section a huge number of images I use to customize the theme (250 game collections, some arcade game styles and new illustrations for platforms and platform categories).
-
I love this theme, which has become my main theme since it came out. Many thanks for this incredible work, @faeran! For those who might be interested, I've just uploaded to the âplaylist backgroundsâ section a huge number of images I use to customize the theme (250 game collections, some arcade game styles and new illustrations for platforms and platform categories).