AstroBob

Hi @leefaster I've broken this out into a new topic, since after giving this a quick test, startup videos do appear to still be working correctly on our side. To confirm how you need to have set this up Inside your LaunchBox\Videos folder, you need to create a directory called startup. In that directory is where you place your startup videos (it doesn't matter what those are called) If that isn't how you've got it setup, can you confirm what your directory setup looks like, and what you've named each of your folders and files? Cheers,

Okay, next thing to test: Do other file formats for the same platform auto-import correctly (i.e .ISO or .bin/.cue?) Second, go to Manage Platforms and for the affected platform edit it. Then go to the Folders tab, and under Game, what path is set there? Note that for the auto-import to work, you need to be adding games to the folder that is specified here Let me know how you get on

Can you do a fresh restart of your machine kill any LaunchBox processes that are running from the task manager, and then try re-opening the application? I'm still not 100% clear what is happening when you try to open the application if you're saying that no errors are being shown. If it helps, could you record a screen recording of walking through the process so that we can try to narrow this down?

Has this been working for you in previous releases? One thing to rule out is in your data folder you'll see a file called ImportBlacklist, this keeps just of games that were previously imported, deleted and marked not to be imported again. Can you temporarily move that file out of that directory to see if that helps. If not, the next thing to narrow down would be your specific build. The best way to test this is to install a brand new LaunchBox instance (on the same drive but different location), and set it up to auto-import a few steam games. It would be interesting to see how a fresh build handles them, or if it still doesn't pick anything up. Let me know

Thanks for the updates folks, the team is working on a fix and we hope to have this addressed as soon as possible. In the meantime, you can follow the guide here if you want to roll back to a previous version 🔗 Downgrading LaunchBox We'll update this post once we have a more permanent fix in place. Thanks for bearing with us here.

You can simply bulk select all the games and go to Edit > Metadata, then follow the wizard to change the Platform field from MS-DOS, to Windows. It may ask if you want to move all media as well, to which you want to choose yes. They should then appear correctly under your windows platform.

Gotcha, thanks for that! I think I've got this, there is a known issue atm relating to the Attempt to hide console window on startup/shutdown option. If you turn that option off, will it launch correctly in fullscreen?

Hi there, Can you go to Tools > Manage > Storefront click the cog next to GOG select *Set Windows Import Platform* and then follow the prompt to select Windows as the import platform? That should stomp them from being imported as DOS. Let me know if that works.

Hi Folks, Thanks for the report, however, this should have been addressed in 13.19. The fix was: I've just given this another test and it appears to be working, here's what I'm doing: Take a .exe file and drag/drop it onto LaunchBox When asked what type of game files are you importing, I select None of the above Follow the wizard to import the game The resulting import shout NOT have the Use emulator to play this game check under Launching > Emulator Please let me know if you're import games differently that produce a different result where this option is still remaining checked

Hi @Fursphere, I’m splitting this into a new topic since I can successfully use Steam auto-imports on version 13.19. This way, we can troubleshoot your specific issue together. The first thing that comes to mind—have you ever deleted Steam games from your LaunchBox library in the past? With auto-ROM imports enabled, if you delete a storefront game from your library, LaunchBox tracks that and won’t try to auto-import it again. To re-import the game, you’ll need to go to Import > Steam Games and use the wizard there. If you use the manual import wizard, are you able to import Steam games that way? A good way to verify this is to install a game on Steam that you’re certain has never been imported into LaunchBox before and see if it's able to be auto-imported. If that doesn’t work, we’ll need to know more about your Steam installation. Can you confirm where Steam and LaunchBox are installed? Are you using any symlinks, or do you have files spread across multiple drives? Let me know and we'll try and get you sorted

Hi there, Thanks for reaching out, we have an FAQ that addresses this specific issue. Please have a look through it here and let me know if you have any further questions. The TLDR is that not all themes affect the game discovery center since it's relatively new. If you prefer Big Box to load to another view that does support theming, you can go to `Options > Views > Default Startup View` and select a different section to use

@xevious1974 I've split this off to it's own thread to troubleshoot. The error you're seeing is because the AddToGamesDb plugin has not been updated for LaunchBox 13.19. This plugin is no longer supported by the developer anyway, so please delete it from your LaunchBox\Plugins directory, and this should fix the error. Cheers,

Hi there, Thanks for the report here, may I confirm a few things to try and narrow this down: Are you updating an existing build to 13.19, or are you installing a brand new instance of LaunchBox? Does the crash happen consistently? I.e if you re-run the installer, does it continue to crash at this stage? If you're updating a build, can you use the same installer located in LaunchBox\Updates to install a brand new build, and see if the issue occurs? Let me know and we'll try to get you sorted.

Hi there, Thanks for report, I've run some tests on this but unfortunately haven't been able to replicate the crash. Can you please confirm: Are you able to reliably reproduce this crash every time you run the cleanup media, or does it happen sporadically? Before you run the cleanup media, can you tell me all of the options you have checked (i.e images, videos, etc) Does it make any different if you run the cleanup for a specific platform VS all platforms? Please let me know and we'll try to get you sorted.

Hi there, Thanks for the report here. May I confirm a few things to try and narrow this down: Can you walk me through specifically what you are changing in order for the image to show up for a different game? Are you able to reliably reproduce this for certain games? Or it only happens for specific games When the issue occurs, if you go to View > Media > Refresh All Images does the correct image display For the game displaying the wrong image, if you edit it's metadata and go to the Media > Images tab, do you see the incorrect image as one of the available images? Let me know and we'll do our best to get you sorted. Cheers,

HI @jevcleem Thanks for the report here. I've split this into a new topic so that we can investigate. May I confirm a few things to help narrow this down: What version of Dolphin are you using? Can you send a screenshot of your Edit EMulator window for Dolphin? Can you also share your settings for the Startup Screen, Running Script and Exit Script sections for Dolphin Let me know and we'll get you sorted. Cheers,

Hi there, Sorry to hear about the issue here, may I confirm a few things to try and narrow this down: What Big Box theme are you using? If you revert to the default theme do you experience these freezes Are you able to reliably reproduce the freeze after a few game cycles, or does it appear randomly? If you can reliably reproduce it, are you able to record a screen recording that demonstrates the issue? Is any sort of error shown when it freezes, or it's just non-responsive and you have to force quit? Let me know and we'll do our best to get you sorted Cheers,

Hi there, Thanks for the report, and sorry for the issues you’re experiencing. Unfortunately, it’s hard to determine the exact cause from the provided error, as much of it has been cut off. If possible, please copy and paste the full report so we can investigate further. However, based on what’s visible, it looks like the issue is related to a third-party plugin that hasn’t been updated for .NET 9.0, which is required by LaunchBox 13.19. If you have any third-party plugins installed, please remove them from your LaunchBox\Plugins directory and check if the error persists. If removing them resolves the issue, you can reintroduce them one by one to identify the problematic plugin. If you’re still seeing errors related to blocked .dll files, it’s possible that your antivirus software is being overly aggressive and placing locks on these files, which are required for LaunchBox to run. To troubleshoot this: Check which specific .dll file is mentioned in the error. If it’s pointing to anything within the LaunchBox\Plugins directory (commonly affecting emulator integrations like ScummVM, Dolphin, MAME, etc.), try deleting the affected .dll files. LaunchBox will recreate them upon the next startup, which should hopefully remove any locks imposed by any antivirus software. Let me know how it goes! Cheers,

Hi there, Thanks for the question. This shouldn't be the case, I use .CHD for 95% of my disc-based platforms (including the ones you've mentioned), and they appear to work with both auto-imports and manual imports just fine. Can you confirm a few things for me: Could you run me through your setup, in terms of where you are stirring your ROMs and what those ROM directories look like. Are there any other files in those directories Does this appear to happen for ANY platforms that use .chd, or just specific ones? Let me know and I'll do my best to help you out

Hi there, Thanks for the report here and apologies this still isn't working for you. Could you please confirm a few things to try to narrow this down: It sounds like you've checked this already but just to be sure, can you go to Tools > Options, and then under General > Automated Imports, ensure that Enable Automatic ROM Imports is checked Go to Tools > Manage > Platforms and edit the Sony Playstation Vita platform. At the bottom you'll see a checkbox called Disable ROM Auto-Imports, can you make sure this is unchecked? This is used to override the default auto-rom import settings for platforms that you don't want to auto-import. What location is vita3k installed to? Is it inside you're LuanchBox directory, or somewhere else? Can you send me a screenshot of the Vita3k Edit Emulator window Finally, can you walk me through how you've been installing your games to Vita 3k? It sounds like you've been doing it correctly since you should see a bunch of directories in the Vita3k\user\ux0\app directory, but just to be sure Let me know and we'll try to get you sorted

Hi Folks, Sorry to hear about the issues here. To help try to narrow this down, for those on 13.19 having the issue, can you confirm if it's ONLY when running attract mode? I.e if you're leaving Big Box running without attract mode, will it still lock up? If anyone is able to confirm this, it will help us greatly in trying to narrow this down. Cheers,

Hi there, Sorry to hear about the issues—we’ll do our best to get you sorted. First, we need to know exactly what errors are being displayed. I know you mentioned that it disappeared the first time, but if you’re seeing an error again, could you please paste the full output here so we can investigate? One of the most common issues with the update to 13.19 is the use of third-party plugins that haven’t been updated to support .NET 9.0 (which is required by LaunchBox 13.19). If you’re using any third-party plugins, I’d suggest removing them from your LaunchBox\Plugins directory to see if that helps. Beyond that, if you can provide more details on what specifically isn’t working—or even better, record a quick screen capture of the issue—that would be incredibly helpful in diagnosing the problem. Thanks for bearing with us! Keep me posted on how you get on. Cheers,

Hi there, Thanks for your question. Unfortunately, Arcade is not a platform that can be imported over a network share, which is why you’re seeing that message. The reason is that arcade games are more complex than other systems, often requiring multiple dependencies to function properly. Currently, importing over a NAS has no way of verifying whether these dependencies are present. That’s not to say it won’t be supported in the future, but for now, you’ll need to import arcade systems locally. Hope that helps clarify things! Let me know if you have any other questions.

Also worth noting the `AddToGamesDb` plugin seems to have been not supported for a few years now. Chances are, if you don't know what it is or have never knowingly used it, it can be safely deleted. Here's what it appears to do

Thanks for the updates there. So because Big Box is able to load with a fresh install, it indicates there is something specific to your primary LaunchBox build, so we can narrow it down from there. Regarding plugins and the cue2chd one, you can certainly try removing it from your current build but I don't think that is the cause, since otherwise you'd see issues in LaunchBox as well. The next thing I'd like to test are Big Box themes, do you know what theme you are using in Big Box? Are you able to navigate to Big Box's system settings, in order to try changing the theme back to the default theme? Or does it crash before you're able to reach that point?