C-Beats

You can actually have multiple parents. So when checking a different box you need to also manually uncheck the box that is checked for "Root". Unsure by your description if that was done or not.

That's driven by the app itself and isn't really something that can be changed via theming that I'm aware of.

We didn't change any logic that would affect how a game is launched so I'm not entirely sure how an update would have caused that. Are the games launching in the emulator and just not performing the way you'd expect, or is LaunchBox not able to launch the games in the emulator at all?

This could just mean the OS is having problems giving us the requested RAM because another program is using it, or because it's taking longer to move currently utilized RAM to the page file and so it can't give us the resources requested in a timely manner. I'd verify you don't have too many apps running alongside of LB when you see this error. Also consider increasing your page file and seeing if that helps your issue at all.

Regarding the Xinput that REALLY isn't needed ever if you don't want to, especially if the PC games are all via Steam. Just run Steam Input and it'll translate the keyboard to Xinput for you. You could also use an app like x360ce and create a virtual xbox controller using your key inputs and then tell the games to use that.

Not sure we changed any launch parameters for documents in the menu move but will verify and let you know.

I'd run the installer over your current build and see if that resolves. This error would indicate to me that something isn't being set correctly in the default theme's XAML files. This is typical if an install didn't go as planned or if you have those files set to Read-Only for some reason. First step would be to just run the installer into the same directory (make sure the installer isn't trying to install to a LaunchBox folder INSIDE of your LaunchBox folder). This has 0 risk of destroying any data and is safe to do. If that doesn't work go to your LaunchBox folder and make sure the LBThemes\Default folder properties has the Read-Only box empty (all white) and if not set it that way (with LaunchBox closed). If neither corrects let us know.

Sounds like this is a message you're seeing inside of RetroArch. Last I knew with some of the changes on RetroAchievements you need to actually update credentials on RetroAchievements (change your password) and then use the new password inside of RetroArch settings.

We don't explicitly tell any app to start on a specific screen, all that logic is driven by the game or emulator you are starting and so would need updating in that app's settings.

You can reach out to support to get a direct download link of the installer and then use that to install. Email support@unbrokensoftware.com

You have to be connected to your DB account for the scores to upload. You can do so by opening LaunchBox and going to Tools > Cloud >> Connect to LaunchBox Games Database

If that's the case you can look in your XML files and delete lines that say "<RetroAchievementsHash>COULDNTFILEHASH</RetroAchievementsHash>" (without quotes) and then run the scan again. That way you don't have to reimport and potentially lose data you put in your library.

Last I knew you can't get collections data from Steam's API. It's been a minute since I've looked though. Would be pretty interesting if we could create import collections as playlists. I don't really use the feature much and replicating the ones I have in LaunchBox is pretty strait forward (Only have ones for controller support levels).

We use the hash application to get the information regarding what the file hash is and so that isn't logic from us. First thing I'd do is review your platform and make sure if it's a custom name (like SNES for example) that the Scrape As value on the platform is properly set.

Images make it look like you are looking at a single row. There should be two error logs (rows) right next to each other, what does the other look like?

If you right click the log there should be something that says "Show Details" or something similar that brings up a new window with an error message. Can you do that and press Alt+Print Screen and then paste the image here?

Can you right click the log and show details and see if there a message in there? Also check the other log in the pair. This looks like the one with the least amount of data.

That log have any more details? What you're showing doesn't have any information on what the error is.

You will want to open Windows Event Viewer and look in the application logs for two errors next to each other that point to LaunchBox crashing. One log will be a generic ".NET stopped working..." sorta thing and the other will give actual details (I believe it to be the top most log by default). That log should give a hint as to what's failing. If you could paste it here or attach a screenshot of it we can go from there. Also if you haven't tried run the installer again over the same location (making sure it doesn't try creating a LaunchBox folder IN your LaunchBox folder) and try again. Sometimes AV applications quarantine files that cause issues like that.

What sidebar filter are you on when starting?

Unfortunately the best way is to just put the old folder back and start adding underscores to folder names to hide them from LB and see where the issue appears. Most of the time I've heard this it's because of older malformed images tied to MAME games gotten from EmuMovies, I believe they've since been removed but if you haven't updated your media in a while it could potentially be the case. Does the error occur after selecting a specific game? With where this stack trace is showing I'd have assume it occurred when selecting a game, I'd just start with that game and remove the images to see if it fixes it, then potentially rescrape media on the platform that game is in.

As stated, this is almost always an image file that is corrupted and NOT a hard drive issue. You can prove the theory by renaming your Images folder to _Images (with the app closed) and then open LaunchBox and see if you still run into the same issue.

No, there's no process in LaunchBox that would overwrite that database ID association. Once it's set it stays set that way.

Right now the database is undergoing a process where we are adding SteamIds to games. Currently LaunchBox will not attempt to match games without a SteamID associated to them in the database. You can tell these pages because the pages WITH the association has a link to the game's Steam page. Right now the only work around is to manually go to a game and edit it. Once the window comes up, cut out the app path and then go to the metadata tab. Press search in the upper right and it'll find the game page. Then click on it to associate the game. Then go back to the launching page and paste the app path back in and press OK to save the changes. We realize this is FAR from ideal and are working hard to get the database changes completed.

Yeah, they've all came in at different times in the app so the uses they were put in for are all slightly different. I could see it being a tad less confusing if we could have a single location for all that stuff. Something to think about moving forward.