JaredN

Hello @AstroBob Unfortunately, “unexpected” crashes are still a common occurrence for me in this version when I use FFmpeg. They've been happening ever since FFmpeg was implemented. On my old PC with an RTX 3060 Ti, on my “new” PC with a clean install—sharing no components with the first one—and an RTX 5060 Ti, and on my Legion GO, which shares NOTHING in terms of hardware or peripherals with my desktop PCs (AMD vs. Intel/Nvidia), with or without antivirus enabled (BitDefender). I also reinstalled LB “from scratch,” without using my old config files and by reimporting all my ROMs. I have no plugins installed other than those ‘required’ by LB/BB for emulator management, and I don’t use any “exotic” themes—only those provided by BB. Other than that, my system (Windows 11 Home) is up to date, as are my drivers. I’m using an external Crucial SSD on my desktop PC, but I also tried installing LB/BB on my main internal SSD (Samsung 990 PRO), and it didn’t make any difference! I’m switching back to WMP, which seems to be working pretty well for now. Thanks anyway for all your hard work ! BB.evtx

Hello! Thanks for this beta! As noted by @Rlad, the auto-import wizard launches at startup whether or not it's checked in the options. BUT if it's not checked, it doesn't seem to be “actually” active! It's brief, and in my case, it doesn't detect a ROM that's been added. On the other hand, if I check the option, it seems to perform a proper scan, detects the added ROM... and crashes for no apparent reason in that case. See attached video. And I didn’t look into it (the crash) further because that wasn’t the point. However, the added ROM was a different version (in another language) of a ROM that was already present. Maybe that’s related? As for the fanart backgrounds, I get the same crash as @Rlad when I try to view them in BB using the “View images fullscreen” option. No problem in LB, though. BUT I don't have this problem only with fanart backgrounds. Here is the log of an error that occurred with a Disc image, without any fanart background present : The calling thread cannot access this object because a different thread owns it. App: Big Box Version: 13.27-beta-4 Theme: VisioN Type: System.InvalidOperationException Site: Void <VerifyAccess>g__ThrowVerifyAccess|7_0() Source: WindowsBase at System.Windows.Threading.Dispatcher.<VerifyAccess>g__ThrowVerifyAccess|7_0() at System.Windows.DependencyObject.GetValue(DependencyProperty dp) at System.Windows.Controls.Image.get_Source() at Unbroken.LaunchBox.Windows.Controls.PixelPerfectImageScaler.InsertServerController() at RandomCompressorAggregator.ReadExplorerList(Object, RandomCompressorAggregator) at Unbroken.LaunchBox.Windows.Controls.PixelPerfectImageScaler.ResetScale() at PassiveDicAggregator.ReadExplorerList(Object, PassiveDicAggregator) at Unbroken.LaunchBox.Windows.Controls.PixelPerfectImageScaler.set_ScaleMode(PixelPerfectImageScaleMode value) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.ImagesViewModel.AssembleReg() at AggregatorBuilderPredictor.SumCustomizableProgram(Object, AggregatorBuilderPredictor) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.ImagesViewModel.ConvertRandomSubscriber() at ConverterDictionary.SumCustomizableProgram(Object, ConverterDictionary) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.ImagesViewModel.OnRight(Boolean held, Boolean onlyRightPressed) at Unbroken.LaunchBox.Windows.BigBox.NavigationManager.OnRight(Boolean held, Boolean onlyPressed) at RemoteResolverAggregator.SumCustomizableProgram(Object, Boolean held, Boolean onlyPressed, RemoteResolverAggregator) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.OnRight(Boolean onlyRightPressed) at AggregatorTaskTransformer.SumCustomizableProgram(Object, Boolean onlyRightPressed, AggregatorTaskTransformer) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.InterruptDecorator(Guid setup) at (Object, Guid) at TransferableSetAggregator.SumCustomizableProgram(Object, Guid setup, TransferableSetAggregator) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.<>c__DisplayClass261_1.ReceiveGroupedObserver() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) Recent Log: 09:16:04 Exception --------------------- As for FFmpeg, it still seems just as unstable to me, since LB shut down without an error message a few minutes after I switched to FFmpeg instead of WMP. I haven't retested it in BB, but I imagine the problem must be the same. Thanks anyway for this update! Enregistrement de l'écran 2026-05-05 084028.mp4

More annoying bug: When I try to download logos, the download only starts for the first 2 or 3, or doesn't start, if I chose to limit the number of downloads for the category. If I don't limit it anymore, it works again. I only tested it for the Gamecube, the only platform I needed to update. Enregistrement de l'écran 2026-04-28 205047.mp4

Minor bug: The "Close" button in Manage Storefronts causes the app to crash. Closing the app without using the button does not. No target found for method Close. App: LaunchBox Version: 13.27-beta-3 Theme: Default Type: System.Exception Site: Void Invoke(System.Object) Source: Caliburn.Micro.Platform at Caliburn.Micro.ActionMessage.Invoke(Object eventArgs) at Microsoft.Xaml.Behaviors.TriggerBase.InvokeActions(Object parameter) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.Controls.Primitives.ButtonBase.OnClick() at System.Windows.Controls.Button.OnClick() at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel) at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Enregistrement de l'écran 2026-04-28 145427.mp4

Hello, I have a new issue to report: Ctrl-A to select all games in LB no longer works since version 13.27 beta 2. Correction: It works, BUT only under certain conditions. If I press CTRL-A after selecting a game, nothing happens! If I left-click on that game again—not too close, so as not to launch it—CTRL-A works afterward. The same goes if I want to select another game from my list by typing a letter. Or delete one with DEL. There’s an older issue that’s been present for quite a few versions now, but which I hadn’t reported. Selecting “text-list with details” from another view in BB doesn’t work with the 3-DIMENSIONS theme. I have to switch themes and then switch back to this one, as shown in the video. Otherwise, I can also confirm that I’ve encountered these two bugs reported by @Rlad: - The three menus—Manage Themes, Startup, and Pause Themes—are empty. - Related Games is only showing artwork from the database, not local files. Thanks for your work anyway! 👍😉 Enregistrement de l'écran 2026-04-20 065703.mp4

Unfortunately, I haven't seen any improvement with FFmpeg. It still crashes and returns to the desktop on BB and LB, in an apparently random manner, with no error message. I'm switching back to WMP... 260403_BB_1.evtx 260403_BB_2.evtx 260403_LB_1.evtx

Yes, me too. I reinstalled Windows this weekend, so there are no old codecs or drivers lying around, but I'm still getting crashes without error messages that take me back to the desktop, very frequently when the video is set to FFmpeg, less often with WMP, but still present (Launchbox and Bigbox).

First of all, thank you very much for this quick update, which fixes a lot of problems! However, I have noticed two small issues: 1. Unchecking “Play Video Audio with Background Music” has no effect if “Prioritize Soundtrack Music over Video Audio” is not also checked. If “Prioritize ...” is not also checked, the video audio remains present, regardless of the status of “Play Video Audio with Background Music.” 2. When background music is selected, launching the screensaver (automatically or with a key) causes it to skip to the next track. Once again, thank you very much for your responsiveness in releasing this beta!

Same here! I switched back to 13.25 beta 3. Honestly, couldn't you test your changes in beta before breaking everything in a final release? I love BigBox and have a lot of respect for your work, but I feel that lately, adding new features has taken priority over stability, and that's a real problem for me.

Hello, I am encountering multiple bugs in version 13.25. 1. Background images are not displayed with the BigBox “3-DIMENSIONS” theme. They appear fine with “VisioN.” All the themes are up to date. 2. I use music tracks that I prioritize over the sound of the videos. When the first track ends, BigBox does not move on to the next one. I no longer have any sound. 3. Problem already reported but not fixed: When I use the screen saver, when the video uses WMP AND when my soundtrack is prioritized over the video sound, I have no sound in the screen saver! Neither the soundtrack nor the video sound. If I play the video in FFmpeg OR disable prioritization, I no longer have a soundtrack in the screensaver BUT the sound from the videos is present. 4. Just a question here, I haven't had the opportunity to test it sufficiently, but has the “spontaneous shutdown” issue been investigated? The latest beta didn't fix the problem for me. It was less prevalent in WMP than in FFmpeg, but still present. I didn't see anything in the announcement about this issue, hence my question. I have an RTX 3060 Ti and will soon be switching to an RTX 5060 Ti, so if it's due to my card model (which is a guess I've seen sometimes), I'll soon find out. Finally, I must say, unfortunately, that even though I love Launchbox/Bigbox and have the utmost respect for your work, I am increasingly disappointed with its development. The software for which I purchased a license at the time certainly had fewer features, BUT lit was more reliable. The more time passes, the more I feel that you are adding features, such as importing via stores, an android version, etc. but the less it works... Personally, I would prefer that you focus on stability. Honestly, I don't understand how it's possible to have a version 13.25 full of bugs that were not present in version 13.25 beta 3... I hope that these issues will be resolved over time, but honestly, I'm starting to consider alternatives, which saddens me, in addition to forcing me to abandon the extensive customization work I've done on LB/BB.

This problem still occurs for me as well. I encounter it very frequently in LaunchBox AND BigBox when the video is set to FFmpeg. Switching video playback to WMP virtually eliminates the problem on LaunchBox and reduces it on BigBox for me, but does not make it disappear completely.

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