AstroBob

Thanks for the update, is it possible to paste the full output of that latest error rather than a screenshot, since most of the error logs are unfortunately cut off. Cheers,

Thanks, so it don't think this is related to the update or plugins given that you've been having these issues previously, and it only affects Big Box. To rule out an user environment issues, please try the following: - Go to your LaunchBox\Updates folder where you'll find the 13.19 installer - Run that installer, and install a new instance of LaunchBox to a location outside of your current location (this is important, you want to install to a different location to your main build) - Once complete, copy your license to this new build and try opening Big Box If the issue persists on this new build, then it indicates there is something specific to your system that is causing this. If not though, it indicates there is something within your specific LaunchBox build. Let me know and we can narrow it down further Cheers,

Hi there, Thanks for the report here, we'll do our best to get you sorted. Can you confirm are you having any issues opening the LaunchBox application, or is it just Big Box that won't load. Can you also share a screenshot of your LaunchBox\Plugins directory? Cheers,

Yeah, i think its the AddToGamesDb that is causing the issue. We've seen a few other reports of people who have that one installed. Can you try remove that plugin and then open LaunchBox. Let me know if that resolves the error

Hi there, This error is likely related to one of your 3rd party plugins having not been updated to .NET 9.0 which is required for 13.19. Can you please provide a list of the 3rd party plugins that you have installed?

Thanks for the report there. Yep that error indicates it's one of the plugins that hasn't been properly updated to .NET 9.0 which is likely causing the crash. I have a feeling it's the ThirdScreen plugin that's the one, I've seen other reports of users with that one causing the crash. It looks like they've addressed this though, so you may just need to update to their latest version Let me know if that fixes it up for you

Added section for known issues

Hi Folks, Thanks for the report here, we've confirmed this is a known issue with 13.19 right now. The DOS importer wizard was affected by the migration to .NET 9.0 and so isn't working as expected right now. We're working on fixing this up and it should be available in beta-1 for 13.20. In the meantime, if you want to import these you can revert back to 13.18 by running the old installer from LaunchBox\Updates I appreciate that's not an ideal solution, but I'll be sure to update this thread as soon as that beta version is available. Thanks for bearing with us and sorry for the issues here

Hi there, thanks for the report. The issue appears to be caused by the OmegaSettingsMenu plugin. With the update to .NET 9.0, some third-party plugins needed to be updated to remain compatible. However, this is at the discretion of the plugin developer. Can you try removing the plugin from your LaunchBox\Plugins directory and see if that resolves the error? If the issue disappears, it may be worth reaching out to the plugin developer via their support page to let them know that the plugin needs an update to work with LaunchBox 13.19 and .NET 9.0. Let us know if you need further assistance!

Version 1.17 - Released February 13th 2024 Release Summary Full Changelog: https://www.launchbox-app.com/android-about/change-log Check out the release video: New Features: Downloading bin/cue games over a network share now includes both downloading and deleting all associated files Introduced a new "Download Game" option for games imported from a network share, enabling users to download games independently of playing them Added the ability to delete the local version of a game while maintaining its availability over the network Improvements: The download pop-up for network share files is now more informative Filter Views that utilize background videos should better identify the correct video to play Increased network buffer size to potentially improve download speeds for game files from network shares Fixed: Default Nintendo 64 core for RetroArch has been updated due to the previous one being retired Resolved an issue where downloading EmuMovies videos could cause the application to crash Resolved an issue where importing files over a network share did not consistently handle bin/cue files as intended Addressed a problem where the selected platform or game information did not always update accurately when using touch controls Fixed an issue where LaunchBox would freeze when launching games if notifications were blocked The app no longer crashes if the user exits the network share username/password input dialog Fixed a rare crash that could occur when attempting to play a game Addressed a crash that could occur when attempting to import games from a network Fixed an uncommon crash that may occur when users navigate between the hamburger menu items Fixed a crash that could occur on devices whose API is 27 or lower Fixed a rare crash that could stop users from proceeding with the import process Fixed several minor crashes reported by our reporting system Resolved a crash that could occur while navigating within a Boxes Grid view Addressed a crash that might happen during the import of MAME files Fixed a crash that could occur when changing screen orientation while on a Filters View Resolved a rare crash that could occur when long-pressing on specific elements Corrected an issue where the background video element behaved incorrectly when a custom view file lacked a foreground video element Fixed an issue that prevented Platform and Game videos from looping correctly

Version 13.19 - Released February 13th 2025 Release Summary Full Changelog: https://www.launchbox-app.com/about/changelog Improvements: Improved speed at which the Game Details View loads in LaunchBox This update replaced LaunchBox's legacy XML-based local game database with a high-performance SQLite database. Expect a noticeably faster startup time, lower memory usage, and a solid foundation for even more performance gains in upcoming releases LaunchBox has now been upgraded to .NET 9.0 (from .NET 6.0) The LaunchBox Game Details Default view now features Related Games in a dedicated, easily accessible section, for a more performant and user-friendly experience The ability to disable individual Related Games sections has been added in LaunchBox, accessible under Options > Visuals > Game Details The included version of VLC has been updated to version 3.0.21, bringing performance improvements, bug fixes, and updated codec support Fixed: The auto-import feature for Playstation Vita games using the Vita3k emulator is now working correctly Restored the expected behaviour for the top background image in the Default theme's Game Details view. It will now prioritize images from your Background image group before using a Gameplay Screenshot as a fallback Resolved an issue where image loading could be disrupted by multi-threaded gremlins Corrected an error introduced in version 13.18 where dragging and dropping non-ROM game files would incorrectly assign an unassigned emulator value Eliminated the unnecessary prompt to select a RetroArch core for platforms that have already been imported Restoring saves on an Additional App could inadvertently overwrite the save data of the primary game Resolved an error that occurred under specific conditions when using UNC paths Known Issues Getting Crashes on Loading If you’re experiencing crashes with an error when opening LaunchBox or Big Box, please check any third-party plugins you have installed. We’ve received multiple reports from users encountering issues with plugins that haven’t been properly updated for .NET 9.0. To troubleshoot, try temporarily removing all plugins from your LaunchBox\Plugins directory. The plugin causing the issue will likely be referenced in the error report. See this post for more details: Importing DOS Games Crashes There is a known issue when using the DOS importer wizard. Unfortunately, there is no workaround at this time, but it will be addressed in a future beta update. If needed, you can revert to version 13.18 by running the installer found in your LaunchBox\Updates folder. Flickering Issues on Dolphin If you’re experiencing flickering when launching games via Dolphin, try the following: 1. Go to Tools > Manage > Emulators, then select Dolphin. 2. Under the Details tab, find the option “Attempt to hide console window on startup/shutdown.” 3. Uncheck this option and try launching the game again. We’re currently investigating a known issue related to this setting, but unchecking the box should resolve the flickering. Vita3K Not Launching If Vita3K is not launching properly, follow the same steps as Dolphin: Go to Tools > Manage > Emulators, select Vita3K, and ensure that “Attempt to hide console window on startup/shutdown” is unchecked.

Thanks for the kind words! Great to hear that the changes have been noticeable, and please don’t hesitate to keep reporting any areas that don’t meet your expectations so we can continue to improve

Thats right! Each purchase of LaunchBox premium comes with a 25% discount code for a lifetime EmuMovies membership. Hope that helps, give me a shout if you'd like to know anything else. Cheers,

Exactly as Joe said! Also adding a recently tutorial that walks through this process

@morbital can you please try the following: - Close LaunchBox - Go to your LaunchBox > Plugins directory - Delete the ScummVM LaunchBox Integration folder Reopen LaunchBox and let me know if the error still occurs Thanks,

Thanks for the update, so just so I’m clear, does that mean you’re not experiencing this on recent games that have that field blank? If not, could you please walk me through of an example of what you’re doing on a fresh build, and the specific game your trying to import that ends up with an incorrect value. Thanks,

Apologies, upon re-reading I realise you may be referring to playing a specific startup video in Big Box. However, I've also tested this and it appears to be working fine. To confirm, you need to have a folder in your LaunchBox > Videos directory called startup, which contains the video files to be used upon loading Big Box. Please let me know if your setup doesn't look like that, and if you can describe a bit more about your setup and where the videos are stored we'll do our best to assist. Cheers,

Hi there, Thanks for the report here. Right off the bat, that file path definitely seems a bit off. Can you confirm. - Go to Tools > Manage > Platforms, and then into your Neo Geo Pocket Color platform. - Under the Folders tab, what is the path listed there for Game Can you also take a single pocket color game and edit it's metadata, go to Launching and then provide an example of what the ROM File path looks like? Finally, can you confirm: - Does this error occur for other platforms, or just Neo Geo Pocket Color - Can you confirm where these affected games are stored? It looks like it's some sort of network or external drive. Please let us know and we'll try to get you sorted

Hi there, Thanks for the report here, it appears there's an issue with your attached error message. If it's possible to re-submit the error that your seeing we'll try to look into this. Can you also confirm if you're able to load LuanchBox at all, or if the error causes the app to quit completely? If you're able to open LaunchBox, go to Tools > Manager > Plugins and then under the ScummVM integration, click on the Repair option Keep me posted know.

Hi there, Thanks for the report here. I've just given this a test and it appears to be working fine on 13.19, would you mind confirming a bit more details so we can try and look into this, in particular: - Can you confirm what behaviour you're seeing regarding the startup screen? i.e it never shows but your game still starts? - What startup theme are you using? - Can you include a screenshot of your startup screen settings - Are you talking about startup screens in LaunchBox or Big Box If you can provide some more details we'll do our best to get you sorted. Cheers,

Thanks for the thorough explanation! It definitely makes sense when restoring a large library and wanting to ensure your saves are properly restored. That said, I’d like to note that since RetroArch is currently the only supported emulator for this, and assuming RetroArch is installed within your LaunchBox > Emulators folder, you should be able to copy the entire LaunchBox directory to a new location when setting up a new instance. This will carry over all saves, settings, and configurations seamlessly. I can see a strong use case for this once we support more emulators, as some don’t store user configurations in a portable way. If you’re interested in learning more about migrating LaunchBox to another PC, including save files, you can check out our full guide here: Thanks again for the feedback—we’ll definitely keep this in mind moving forward!

Thanks for the candid and transparent feedback! The team is definitely pleased with some of the recent updates, and we truly appreciate you keeping us on our toes to ensure we’re focusing on what matters most to you. That said, we’re certainly not stopping here—there’s still plenty more we can do to improve performance and enhance the overall experience. Great to hear that the changes have been noticeable! Please don’t hesitate to keep reporting any areas that don’t meet your expectations so we can continue to improve. Thanks again!

Correct, currently, you can only manage saves (restoring and backing up) for one game at a time. While it’s not out of the realm of possibility, it’s not something we’re actively considering at the moment. That said, we’d love to learn more about the specific use case this would solve for you. From what we’ve seen, users typically use the restore function when focusing on a single game and want to revert to an older save or a specific point in time. We’d be curious to hear about any workflows where bulk restores across multiple platforms would be beneficial. Let us know so we can take it into consideration for future updates!

Hi Folks, For anyone coming across this thread, we have a newer post with updated information on Big Box performance and troubleshooting steps. Please refer to that thread for the latest guidance on improving and debugging Big Box performance.

Hi There, Yes, this is common behavior for most NAS setups. NAS devices are typically designed to be discoverable via local network protocols (such as SMB or NFS) and do not natively support discovery over the internet unless additional configurations (like port forwarding, VPN, or cloud services) are used. Right now, this is very much up to how the individual NAS is configured, so it should be possible to setup, but we don't have any visibility over that on the LaunchBox side. This is again dependent on the supporting Wake-on-LAN (WoL) packet to the NAS when trying to access it. Some third-party file managers support this, which is why they work. If your NAS supports Wake-on-LAN, you could try manually waking it up using another app before launching Launchbox. Right now I don't believe we support Wake-on-LAN within the Launchbox app so that it sends a magic packet to wake the NAS when needed. It's something we could look to add in the future though. Hope that helps to clarify. Give me a shout if you have any more questions.