JaredN

And by the way, since it’s nice to point out what we like—not just what we don’t—I really love how LB/BB handles startup and shutdown now! Thanks! 👍

Hello @faeran ! Is this update still planned? The way Launchbox currently detects ScummVM games prevents any game-specific settings from being applied via the ScummVM stand-alone too, other than global settings. Similarly, save files created via LB/BB do not point to the same ID and have names that prevent them from being detected by LB/BB, and vice versa. Personally, I’d like to be able to use ScummVM on a laptop that doesn’t handle LB/BB well and then transfer my saves to my main PC and LB/BB later. That’s impossible right now given how ScummVM games are handled. So for now, I’ve stopped using LB/BB for ScummVM games, which I’m running as stand-alone apps, but I’d like to be able to reintegrate them into my collection. Thanks for your great work anyway !

Thank you very much @Fursphere ! This confirms that the problem isn't caused by my settings and that it's a broader issue. I hope it will be fixed in the next beta releases. In the meantime, no crashes with WMP so far! It seems pretty stable.

Thanks @Fursphere ! WMP seems pretty stable on my end too. And honestly, as long as one of the video decoders works properly, I'm fine with that! But it's still very strange. I’ve had this issue with FFmpeg from the start, on my old PC (RTX 3060 Ti, Intel CPU, 16GB of RAM), a new machine (RTX 5060 Ti 16GB, different Intel CPU, 32GB of RAM), and on a Legion GO (AMD architecture). I haven’t retested on the old one (which I no longer have) or on the Legion GO recently, but it doesn’t seem to be a hardware issue. I’ve also tested with the files on an internal SSD, an external SSD, an SD card, with and without antivirus, with the default themes, without plugins... With the new installation, I started from scratch. I re-imported my ROMs, reconfigured LB and BB so they wouldn’t use my old config files… but no. Still random crashes with FFmpeg. AND sometimes with WMP, but less so. The only common factor across all of this is Windows 11 and certain settings shared between the machines. Windows is up to date and my drivers are up to date. And I tested it without applying scaling. And I’m well aware that not everyone is experiencing this issue and that the devs can’t reproduce it… so there’s something going on! But what? Fortunately, @faeran just confirmed that they haven’t tried to fix this issue in this beta yet, but that it’s in the works, so I imagine it’s coming! Thanks anyway for the suggestion, @Fursphere ! I’m sure some additional testing could help.

I spoke too soon... BB still crashes with FFmpeg, too. With FFmpeg, I'd say that LB and BB seem even more unstable than before. I'm switching back to WMP. I hope that goes better. 😕 BB 1.evtx

Launchbox is more unstable than ever with FFmpeg... 2 crashes in less than 5 minutes after the update. BigBox seems to be holding up better. To be confirmed. In any case, thanks for the update! 😉 LB 1.evtx LB 2.evtx

I'm also experiencing the same issues, which I've reported multiple times. I recently switched computers. My installation is “clean,” and I'm still having this problem. I had it before with an RTX 3060 Ti, and I still have it now with an RTX 5060 Ti (16GB) and 32GB of RAM. The CPUs for both setups were Intel. And I’m also having the same issues on a Legion Go with an AMD architecture... Windows 11 is up to date, and my drivers are up to date. And it crashes on all three machines, more often when using FFmpeg than WMP. The difference is that LB can crash with FFmpeg, but that hasn’t happened to me recently with WMP. BB crashes regularly with both, but more often with FFmpeg.

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!