C-Beats

What file location is the new and old installs at? I know some locations have caused issues in the past, like installing directly to the root of the drive. Curious if WHERE it's being installed is the problem.

For starters I'd close all instances of LaunchBox. Then navigate to an old instance of LB and copy it's data folder to the new instance, (delete the folder in the new instance and then copy the old over). Then start the app again. If it still works you probably have a corrupted file some where in the install. Sounds like it could be either a plugin, or some no longer needed files lingering in the core or metadata folders causing an issue. If you're feeling adventurous delete the following folders from an existing install and then run the installer over top the location and see if it corrects anything: LBThemes Metadata Plugins ThirdParty

Can you use the 13.14 installer to install a new instance of LaunchBox some where on your computer and let me know if the new instance works?

Pretty sure this will occur if you manually alter the settings file and add it twice on accident. I'm not seeing it in any of my builds.

Can you open up \\LaunchBox\Data\Settings.xml and look for the <Theme> tag and change that value from Default to Old Default and then save the file and attempt to open LaunchBox and let me know if you still encounter it?

What file system format is your drive? NTFS or exFAT?

The 13.14 installer should be in the updates folder as well. Just run it and point it to the current install (make sure you don't point to a LaunchBox folder WITHIN the current LaunchBox folder when doing it) and then see if it corrects the issue.

Does running the current version installer over top work?

If the Event Viewer has an app crash log there will be two of them for the crash, one log just saying the app crashed and the other with the actual exception. The text you posted appears to be the "it crashed" log which won't be helpful at all. The other log should at least list a reason for the crash.

The cache system of auto-pop playlists has been altered a few times since I've been on team, but I've not been the person who changed the code so I don't really remember where we landed regarding WHEN/IF we cache the return set of an auto-populated playlist. I do know we had that issue in the past, but pretty sure we removed the startup cache of those playlists a while ago. What are your startup times looking like, and which app are you seeing it with? I have a build that has 2680 auto-populate playlists and I don't see any impact to my startup time. I admit I don't have as many game records as you in that build though and am only around 17k.

Reads like you're trying to load a bad theme XML file. What theme are you using? If using Default, did you try to edit something in the files?

NetherSX2 is just AetherSX2, should be able to select it as the emulator in the app and it work with NetherSX2 out the box. Or least did on my Odin 2. I don't remember having to change anything special for it.

Files the emulator needs to run the games properly. They are typically BIOS files for the system in question.

Known bug for platforms with no dependencies. Press back to get to the page, we have a correction made and it will be in the next release.

We're looking into the data to see if we can do it without causing a lot of false positives. No promises.

In the View menu there is an option for showing the version of the game in the title. Sounds like you accidentally pressed it. Ctrl+R turns it on and off as well. I've tapped it a few more times than I care to mention....

Ah. What you're looking for is called the "template" for that type of image. I'd ask the author of those image packs if they are willing to give you theirs or where THEY got it to begin with.

You only looking for circle logos for platforms? I know if you look around for artwork for other frontends you may be able to find it a bit better as then tend to use that style of clear logo.

That emulator should be pretty strait forward. Pick one of your games and then press CTRL+E to open the Edit Game window. Then go to the Launching page and post up a screenshot of what that looks like.

Our download section has a lot on offer, including several "silver ring clear logo" sets

Updating that file would only help with DB related activities. The ones you are mentioning don't interact with the DB at all. Are you seeing your reported issues on ANY theme? I'd try Default theme and see if the problem persists there, if it doesn't then it's probably a theme related issue.

First step is to figure out where exactly you want to see them. Take a screenshot then mark it up in paint about where you want it. Can guide you from there.

Ah, would explain the other one as well. Your local GamesDB xml file is corrupt. Go to Tools > Download > Force Update Games Database (or something similar). Let that run and it should resolve the issue.

Version 1.7 has just been released! THIS THEME NOW REQUIRES 13.12!!! - Improvement - Added the advanced search help popup that was added in 13.12. If you do not want this popup to display at all you can alter the ThemeValues.xaml file and set SuppressSearchPopup to 1 and it will no longer display. - Fixed - Made modifications to Game Details to hopefully eliminate the stuttering issue. Let me know if you do not see it resolved.

The error would indicate something is happening with your Automated ROM imports. To work around this error do the following: 1) Close LaunchBox if open 2) Navigate to \\LaunchBox\Data\Settings.xml and open it in a text editor 3) Find the following tag <EnableRomAutoImports> and make sure that line reads "<EnableRomAutoImports>false</EnableRomAutoImports>" (without quotes) 4) Save and close the file 5) Reopen LaunchBox