C-Beats

Is there a specific platform/game that you are having issues with?

Please attempt to login to EmuMovies via their website first and see if that works. EmuMovies had a recent server upgrade that flagged many accounts for a required password reset and until you reset the password their API just tells LaunchBox your credentials are bad and doesn't allow us to download any premium files.

If you haven't already please try to log into your EmuMovies account via the EmuMovies website. There was a server upgrade and most users accounts got flagged to require password reset. If you have not done that it may be EmuMovies API telling us your login credentials are bad.

Would assume it is caused by that bad character in the filename. Believe the OS expect calls to be made with UTF-8 encoded strings and if that character isn't a part of that it may be the cause for the issue.

The primary reasons you would see this are: You selected a root folder and all the games are in sub folders but you checked the "Scan only specified folder (no subfolder)" option You already have the files in your collection (and don't have force import option selected)

LaunchBox uses .NET Core 3.1 as of version 11.2 not Framework, and as Neil said you have to have SP2 installed to install those dependencies.

Additional App information is the platform's xml file. They are located at the bottom underneath all the game information. Search for "<AdditionalApp" (without quotes) and you should hop right to it.

Something like this is potentially doable via a plugin, though I don't know of any already made that would do what you want. I'll address each point below individually to give you a starting point, but after that you may have to experiment a bit to get it all working the way you want. Also wanted to point out all of the below will require C# programming as well as WPF/XAML. 1a) There is a keyboard mapping to switch theme's, but you don't pick what theme you're going to, you simply move to the next. 1b) You could in theory use a plugin to change a variable passed to an element in the WPF XAML view that would drive which images would display in the theme and change that variable via plugin. This would not actually be changing Big Box theme's but you could easily set up styles inside of the WPF to make the whole experience look completely different based on that variable (requires the use of a theme that implements a IBigBoxThemeElementPlugin from our plugin library) 2) This greatly depends on what you would like but you should be able to change this on the fly with a plugin as well (Requires use of IBigBoxMainViewModel and potentially IDataManager in our plugin library) 3) Would be done the same way 2 is

Do have the LaunchBox logs for those events?

@Kiinkyfoxx may be onto something. I would remove that other file unless it IS for another platform you have in your set up and see if that resolves the issue.

Two of the things throwing errors are DirectX libraries. I would make sure you have your video and audio drivers up to date as well as DirectX

I removed it because as I stated in the thread you linked in it, a user should never run LaunchBox as admin. it WILL create far more issues than it has the potential to fix. If you require admin privileges to run and use LaunchBox you have something set up wrong. Want to keep the misinformation to a minimum and so removed the post.

You can't do the replacements with LaunchBox or Big Box open. Have to close both down and ensure have completely closed via Task Manager before you can update the xml file. Then once you start either application back up you should see the change.

Alright, just wanted the extra information to help narrow down where in the process your image loading is failing.

So no, they aren't for the same file/game entry?

Are all those other Qbert logos for the same game and platform?

That is the reason you are having issues. We can't create the symlinks we use on an ExFat formatted drive. What you can do as a work around is copy your \\LaunchBox\Themes\ folder to \\LaunchBox\Core\Themes\ (there shouldn't be a folder there already by that name) and then mark it as read-only. When adding more themes you will need to make sure they get added to both \\Launchbox\Themes\ as well as \\Launchbox\Core\Themes\ moving forward if using that work around though.

Is the drive LaunchBox is installed on formatted NTFS or ExFat?

Typically that error is caused by bad XAML in the theme you are using. The XAML parser is choking on the file and letting you know and then loads the default theme.

You image is of LaunchBox executable failing to open because of .NET Core requirements, not the installer. Installer should install the .NET Core 3.1 runtime for you but if it does not you can download and install it manually from here (you want the desktop runtime in the middle of the right column). Your log indicates no fatal error so if you are seeing one could you post a screen of that error.

One of the following options was checked which fires logic that verifies what media a game does or does not have and is the cause for your increased CPU usage: Force populate image cache Hide Games Missing Video Hide Games Missing Box Front Hide Games Missing Screenshot Hide Games Missing Background Hide Games Missing Clear Logo

Logs indicate you are force populating your image cache. That process will use as much CPU as it can to cache all your images as quickly as possible. To see large CPU use while performing that task is to be expected. CPU use being high isn't a bad thing, it means the software is utilizing your resources to the best of it's ability.

Curious if the old cache files were corrupted in some way, or Big Box was having issues reading them for some reason. When you open Big Box after the images have re-cached, do you ever have the problem again or does it go away permanently?

If you sit still do they populate? Can you scroll up and see some logos, but not all? If so do they ones that weren't there reappear after a few seconds or no? Trying to see if the cache is stopping entirely or just taking longer than it should. Also could you look in \\LaunchBox\Logs\ and grab a log when you are seeing that behavior and PM it to me so I can take a look, see if there anything in there that could give us a clue as to what is going on.

I would assume given what consoles you listed is that you aren't using the Platform with the same name that is in the Database and don't have your "Scrape As" properly set. We don't look at the ROM file at all during metadata/media scraping and so it's location has no effect on that process.