C-Beats

Now that I know what causes the errors correcting it isn't too bad. Finding out why it's happening in the first place is the bigger issue that needs addressed.

This. You have 3D box art in your Box - Front image priorities. Either that or that image is tagged incorrectly and isn't marked as a 3D Box image.

No the error is the same one. Something in the Automated Import page is failing to save correctly which is stopping other changes from being saved that you made in that window. This error has absolutely nothing to do with LEDBlinky from what I can gather from your stack trace.

Ugh.. thanks for the heads up. Bad record snuck in again. I removed it so should help with that.

You can restore a automated backup to get the data back, sounds like your parents.xml file was corrupted.

Too small to waste time on something that ultimately doesn't matter

Because that's the last time some one updated the date. As you can see the company, the website, and thus the copyright are all still active and valid so the date on the bottom of the page doesn't really mean a ton. Could probably just cheat and use JS to just put the current year there but meh...

Yeah, but look how well the LB icon pops in comparison to the rest! It's like it's screaming, "PUSH ME!!! I'M RIGHT HERE!!!". Sounds like a feature more so than a bug!

The error you're seeing isn't related to LEDBlinky at all, one of the options pages is having problems with it's save event and is throwing an issue for it. It appears to be looking to add the folders used in automated import feature and is failing to do because the folder in question doesn't exist (or can't be read by the app). If you disable this feature via it's option page and press OK I'd have to assume it'd work and the LED Blinky options would save then for you.

Nothing in the LB application flow should need to be ran as administrator and running the actual apps this way will cause issues do to relative pathing that being ran as admin changes in the environment. We've seen issues in the past as well with the app being in some system folders and so generally I recommend it NOT being in Users folder like I believe the default installer path is. Something like C:\LaunchBox\ has been more full proof in the past. I've never used compatibility mode with the application before and so can't really speak as to what (if anything) that does to the process flow. I'm not really following though what the exact issue is though if I'm honest. Is it that you attempt to open LaunchBox and the main UI just doesn't appear, or are you reporting something else. When you see your issue are there any event logs in Windows Event Viewer? They'd be in the application section and generally I believe on errors from our app appear in there as we don't directly report to it and it only happens when something in the .NET framework fails or crashes.

If you start seeing any obvious patterns like this while moderating the DB please reach out to support@unbrokensoftware.com so we can attempt to look into it. They can look up the accounts and reasons given for the changes and we can try to get it stabilized.

Inside of LaunchBox, go to that platform, select any game, press CTRL+A, then CTRL+E. Press Next on the wizard, select Emulator as the field you want to edit and leave the bottom value blank, and then hit next until the changes are applied then say you're done making changes. Should remove that "Undefined" emulator entry from those games.

We didn't change any of the dependencies, I'm unsure if our installer just checks for the latest release or not. It sounds like you have a suppressed UAC prompt though. UAC should ask you if you'd like to give permission to installed Direct X in which case you press yes and the installation happens.

Product codes for those two I believe are just W1R and W2R

Potentially so. If you could since the full release is out submit an official bug report so it doesn't get lost in the shuffle, especially given that holidays are around the corner.

In the options menu of Big Box there is an image cache section. Clear your logo cache (don't remember if we have a platform logo option or if it's all of em) and it should pick up the new images.

@boylag You're being told that if the image you're seeing is of one of the image types Faeran listed then the theme displays them with priority and so what you're seeing is the theme working the way it was designed. If you don't like how that is handled you'd want to copy/paste the theme to a new folder and then rename it. Then go to \\LaunchBox\LbThemes\{Name of your theme}\Views\GameDetailsView.xaml and search for "FlowImage" you should come up with 3 references 2 of which have an "ImageType" property with several values. Make sure the only value in parens is the "Backgrounds" value and you'll have what you're looking for.

You already have some one helping you in the appropriate theme support channel, there's no reason to start up another thread. Does this behavior happen on themes OTHER than Big Details?

Have you tried doing what the error message is telling you? Go check that files properties and ensure there isn't a "unblock" button requiring clicking on the bottom of it. The release is new and Windows tends to do a mass approval type of thing where if it sees the DLL has access across a lot of it's user it deems it as more safe. Since this release is new some of the definitions haven't been auto-flagged as safe and so may require more manual effort than it would normally. I'm not sure I've seen it manifest itself in that way before which is a bit unsettling but we'll keep an eye out for it.

Actually had the build done and was about to release it when we saw your message. We'll get it added in and rebuilt. Thanks for going the extra mile and getting it done while away, much appreciated!

Save each platforms image folder into a zip and archive it somewhere. After the install use the image pack importer to then import all the images to your library at once. I'd try it once to ensure it'd work the way you were expected before stopping at this solution though.

There are 3 levels we attempt to match games by in a manual playlist. Filename LaunchBox Games Database Id Platform/Title pair We go from top to bottom (first two steps may be in wrong order) and if a game matches it's considered the game in question

\\LaunchBox\LBThemes\{YourTheme}\Views\ListContentView.xaml. There is a a datagrid in most of them that displays the items (often CALLED Items). In those columns you see add a Width by adding the following: Width="100" (set 100 to whatever you value you actually want)

Yeah, not even sure at this point what the DAT is showing you that isn't already being displayed though. I still wouldn't get your hopes up as I just don't have time to invest into any huge undertaking but I'd be curious to understand what you DON'T have now that you want in those files.