C-Beats

I'd copy it again (or at least the "Core" folder). Sounds like the AV is quarantining/locking that DLL. We've had issues with that specific DLL getting blocked like that a lot lately since it's essential Chrome in DLL form. Lot of AVs block it since it allows the application to open websites and other web related activities.

This thread pretty exclusively talking about genre playlists where we have systems in place that help you create playlist by each genre automatically, you can then use the Genre sidebar filter and select "(NONE)" to see the games that don't have a genre at all. This option may need to be enabled in Options (I can't remember the default value).

Yeah, this solution predates all of these features and may need a revisit at some point. Ideally as we moved towards new solutions on other fronts we will likely move away from some of the sidebar systems in place as they tend to trip over themselves a lot. We have a lot of idea's fleshed out for future projects but it's kind of hard to inject them into LB currently because it'd be a pretty drastic change from the normal. Tagging @faeran so he can mull over what the best course of action is in the more immediate future.

That's been a thing for as long as I've been around. I think it's largely because most of the events that create playlists create a PRETTY large number of them with names that aren't always pretty. There were concerns it'd bloat that view with playlist names that made knowing what you were looking at pretty difficult. I'm referring to things like auto-generated genre child playlists. Due to this I think the logic was to hide them so only the ones you manually created yourself were shown and not lost in the sea of the other stuff.

You got a screenshot of what you're referring to? Want to see if we're talking 3D Box Images or the 3D Box Model

I'm not entirely sure what the end goal here is but there seems to be some confusion regarding the difference in the 3D Image Type you are using in your game grid, and the 3D Model that you're seeing in the Game Details (on the right). The one on the right is created by the application using a 3D model and procedurally adding the appropriate images to it (Front, Back, and Spines). The one on the left is a single image. The one on the right you can rotate and zoom in/out of, the one of the left is what it is.

Not beta related and as of now working as intended. When removing all games you remove the platform which means we can't be 100% where your image folder for that platform was. We could probably at the very least check the default path, but as of right now I don't believe we do. You could submit a feature request for us to change that logic and see how much traction it gets.

The sidebar on the left. The drop down where you can pick things like "Platform", "Platform Categories", "Genre", etc. There should be one in there called "Games Missing Media". It'll probably ask to scan your library for missing media when you select it. Say yes for the most accurate results.

No I don't believe any of the image controls have logging entries in them that says, "hey this image type was asked of us but we didn't find it". Closest thing to something like that is our Games Missing Media sidebar view in LaunchBox proper that helps you select items in your library based on what image group it has missing

There is a checkbox in the controller section of the options menu within Big Box that says something akin to "Problematic Controller Compatibility". Is that checked? If not check it and let us know if you still see the issue.

When users report they've imported games but don't see them it's almost always because an auto-hide feature is enabled. Inside of LaunchBox go to the View menu and look in the Show/Hide section. Make sure none of the options stating "Hide Games Missing..." is enabled.

LaunchBox files are pretty installation specific. Only file that stands out immediately may be \\LaunchBox\Data\InputBindings.xml which stores the controller bindings for LB/BB. If the bindings are diff per install that may be worthwhile to omit.

Automated imports page, it's the feature that allows LB to automatically scan your drive for new roms and auto-import them.

Take a LaunchBox installer and install it to the same location ensuring the installer doesn't try to install it to a LaunchBox subfolder under the current folder. That error indicates one of the dependencies is missing or corrupt, typically caused by an overzealous AV application.

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.