C-Beats

During MAME import there is a checkbox asking if you want them made. It's on by default. Turn it off and it won't create those.

Anything worth saving is found in your Data folder. If you have backups enabled in LaunchBox it'll automatically back up that folder into a single archive and stick it in the Backups folder. It'll keep the last 10 backups at startup and shutdown for easy roll back. You can also manually create a backup file via the LaunchBox interface and store that somewhere you want as well.

Use the "Games Missing Media" sidebar, let it scan artwork, select games missing box front, select all the games and then go to Tools > File Management, select bottom option. Export/Move the files to a new folder

If the files aren't listed in import it's almost always because you already have them imported and just aren't seeing them because they are hidden, or imported to a platform they shouldn't be. First step is to look in View > Show/Hide and make sure nothing is being auto-hidden via that menu. If those are all off and you still can't find it you can run the Audit tool to attempt to find what game imported is pointed to the file in question (list view can likely be used as well)

If using default image type settings Box - Front is placed there

Scrape As means "Hey what system do we call this thing in our database?". When we look for any metadata/media for that game we look at the platform name if it matches, and that scrape as value if it doesn't. For example it's not "Xbox" in our database it's "Microsoft Xbox" and so you're essentially saying "I know I call it something different, but look for all the good stuff over here"

Should resume from where it it's at if you close and reopen LaunchBox. If it doesn't just rerun the wizard. If you select the "do no replace" option it'll only download the media for the items that still need it

Intel GPU's have a known issue rendering WPF related to their anti-alias logic. In the Intel Graphics control panel there is a setting where you can either enable or disable aliasing for an application. By default the value is "detect" or "handle automatically" or something like that. You need to set that drop down to either Enable OR Disable. The value you pick really doesn't matter and either will work. For some reason that auto-detect feature makes it so entire chunks of elements don't render correctly though like you are seeing.

Removed the last message in an effort to stop you from doxxing yourself. All licensing inquiries and issues need to be resolved by emailing support@unbrokensoftware.com. Give them as much information you can about the transaction and they'll be able to assist you.

Sounds like the font load we do is potentially failing on startup.  You can manually go to \\LaunchBox\LBThemes\Default\Fonts and then right click the Gilroy fonts and select "Install for all users" in the context menu that appears to install the font in your system permanently and it should correct what you're seeing.

I've looked into this and made some adjustments to code internally to correct. Should be in the next beta release. I believe the goal is have that out today.

Yeah, I think this is the cause. I have a full path in mine that isn't in yours and it's causing issue in the code. A work around for now is to open the yml file and in the "pref-path" entry put the full path to the folder the emulator is located in. Save the file and then try to import again in LB. Alternatively you can rename/move that file out of that directory, run the import and put it back. I've noted the problem location in code and it should be corrected in the next beta release.

We've seen this happen in the past with older metadata files. If you can open up LaunchBox and go to Tools > Download > Force Download Games Database (or something similar). Fairly certain it's the bottom most option. Let that run and you should see the issue go away.

Thanks for the heads up. I'll get it cleaned up

That button just calls the appropriate AHK script you have set on that emulator. Sounds like the script needs altered to do what you want. If you need help adjusting it you'd need to provide more information like what emulator you are using, and what hotkey within the emulator you have "Reset Game" set to since you'll need AHK to pretend to push that button.

All data pertaining to your personal library in \\LaunchBox\Data. The files that contain information about specific games would be \\LaunchBox\Data\Platforms\{NameOfPlatform}.xml

I personally would like to address it in the near future. That being said I don't really get a say on when things are done. In the future I'd like to be able to add the name of the executable/process to look for in Edit Game so that a user can basically tell LB "hey don't pay attention to that first window, look for THIS one instead". No eta on when a change like that will make it in though.

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.

Go to Tools > Manage Emulators and select Redream and press edit. Then go to the Associated Platforms tab. Uncheck the "Use M3U Playlists for Multiple Discs" and press OK then launch the game. Redream doesn't list .m3u file support on their page and so I'm assuming in an event it's asked to open a file it doesn't support it just loads to the menu.

Auto-import will auto-assign the imported games in question to the default emulator for the platform they are imported for. If one doesn't exist then an "unassigned emulator" flag is set on those games. If you attempt to play one it'll ask you to set up the emulator and give recommendations as to which to use if we have a recommendation. When you set up it up it'll ask you if you want to assign it to all games in that platform and if you press yes all of them migrate to it and can be played like normal.

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.

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.

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.

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.

In Big Box options there is an option to set the default view. In the new install it's set to Discovery Center, you'll want to change that to either Platforms or Platform Category