C-Beats

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

That's driven by the database. Typically articles (a, an, the) are placed at the end for sorting purposes. You really only need to move them to the back when you have to sort by that string. Since LaunchBox doesn't and has a custom sort value field moving the article isn't required and can be shown in front as intended. If you want to move the articles despite that you can in your library.

Badges are a somewhat newer thing for Big Box and I'm unsure if CTC supports them or not which affects how many themes use them. I know the default theme does show badges (or at least some). I'd say find a theme that overall works for you, then modify it to add the badges. They aren't overly complicated to add and people on the forums can help you out with it.

Our download section has a lot of uploads for Pinball FX3 tables, you can start there.

OH, that explains why I'm not seeing what you are... Didn't even notice you're using RetroArch. I wasn't even aware there WAS a PCSX2 Libretro core. I've only ever used (or heard used) the standalone emulator. I'll have to take a look again now that I'm on the same page as you.

What's your details page look like? Can you post up a screenshot of that? I'm having a hard time replicating on my end so could use the information to maybe help in that pursuit.

Are you running a file sync application? That typically displays when saving the options and can be delayed by something locking the file we are trying to write to.

Not entirely sure I know what screen you're referring to. Can you post a screenshot? Big Box code wasn't touched at all in this release so I see no reason you should be seeing ANY difference in that application in these versions compared to previous.

Tools > Options, Go to the Automatic Rom Import page. Uncheck the only box in there to disable the feature, press OK to close the window and save the setting change.

I'll need to take a look at the code but that is not how that window should look. Should list the various BIOS that the emulator supports. I'd try running the installer over your current install again and see if it corrects. Not really sure how what you're seeing would even be possible given the code in place atm.

This typically happens when an overzealous antivirus app quarantines that file. Because it contains the in-app chrome browser we use AV's mark it as being bad sometimes and quarantines it. You should be able to tell your AV to knock it off and then re-run the installer so it gets placed there again and then run the app like normal.

Can you post up a screenshot of what page/tool you're referring to?

Automatic storefront import and Automatic ROM import are two different features and can be turned off/on independently of each other. Storefront auto-imports can be managed via Tools > Manage > Storefronts, Auto ROM imports has an on/off checkbox in Options (Tools > Options)

I'll look into why the error window is showing, but you need to assign an emulator to your games. You currently don't have one.

Can you go to Tools > Manage > Emulators. Then select RetroArch and press Edit to open the Edit Emulator window. Once it's opened go to "Associated Platforms" page of the window. Is there a "Sony Playstation" row, and if so does it have a core listed? If not select that row and delete it (press delete button) and press save. See if that corrects. In the meantime I'll take a look at the actual error and see if we can get that resolved.

Fairly certain that list is derived from your game data, to remove them you'd need to remove those genre's from the games that have them assigned.

Still shouldn't throw an error like that but the stack trace makes it seem like your game doesn't actually have an emulator assigned to it and the app is trying to tell you as such.

As stated... All eXo builds ARE LaunchBox builds... any tutorial that helps with one helps with the other... The only thing that requires any amount of potential maneuvering is when the eXo collection is using a platform by the same name as one in your collection (This typically occurs with the MS-DOS platform since GOG can already import to that platform). If they don't it's simply a matter of moving the appropriate data files and eXo dependencies to the new LB directory. If they do you need to change either the existing platform or the eXo platform before doing the migration. As far as LaunchBox is concerned you'd want to migrate the following folders from the eXo build to the new one. \\LaunchBox\Data\Platforms \\LaunchBox\Data\Playlists \\LaunchBox\Images \\LaunchBox\Videos \\LaunchBox\Manuals Data backups are fairly simple to restore via in app so those concerns are easily corrected if something goes awry. We don't auto backup the media folders and so ensuring you aren't overwriting any files in that process is a bit more critical.