Retro808

Keep in mind also you need to download your own media. You mentioned the game wheels look plain. This could be either because you are in a Text View or you are in a Wheel View and you never downloaded Game and Platform Clear Logos. Theme's typtically do not come with media. There are some that have certain media types, but you will more often then not need to make sure you download media for your games and platforms.

There is a bulk edit game path option in Launchbox. You have to do it per platform. Choose a platform, highlight all the games, then... >Tools>Change Rom Path for Selected Games.

Are you talking about for playing games? If so that is all done in each unique emulator you use.

Yes, different scenario, but just slightly. As I mentioned in my posts it still works if the custom images are in a folder inside the theme's actual folder structure. If the folder is outside of the theme that was still an issue. Switching the code to LAUNCHBOX_ROOT_FOLDER was needed to get it functional again with the new LB build.

Ah like we would do with custom Fonts also. Just tested one theme and it works perfect. Thanks Jason now time to update the rest of the files with the LAUNCHBOX_ROOT_FOLDER change.

For example my Startups and Pause theme's as well as a custom marquee xaml I use a custom folder stored in the main \Launchbox\Images folder so I do not have to have multiple copies of those images in each theme. I just point the theme xaml or marquee xaml to a custom folder in the Launchbox Image folders. Below is the code used for marquee images similar to what I do for game controls: <TextBlock x:Name="MarqueeStatic" Visibility="Collapsed"> <TextBlock.Text> <MultiBinding StringFormat="{}pack://siteoforigin:,,,/Images/Marquees/Platforms/{0}.png"> <Binding Path="SelectedGame.Platform" /> </MultiBinding> </TextBlock.Text> </TextBlock>

So far with new beta no more issues with theme's and custom images if the folder is located within the theme's older structure. Still have issues if the custom folder resides outside of a theme's folder. You did say some outliers remain, but I just wanted to mention.

If it is telling you which specific file is corrupted you can just open one of the backups zipped files and copy the specific xml to the \LaunchBox\Data folder. You can copy them all, but not needed if it tells you which one if corrupt.

This is not anything new. This has occurred for quite a while in VS2017 and VS2019. Those errors can usually be corrected by fixing the broken/missing referrences. Just tested again and the Default theme would error. You can see the errors in the references. Correct for the missing .dll and the theme displays.

It is possible. LB has a couple ways to use AHK to either close out a game/emulator depending on what exactly it is you are trying to do. 1. The simplest way if you are just trying to close a game (if using the keyboard/controller automation is not working) is to add an AHK script to the Running AHK tab in the edit emulator screen (>Tools>Manage Emulators and edit the emulator you need). 2. You can also compile an AHK with the code you need and then add it as an additional app to a game (Right click a game and choose edit. Add the AHK to the additional apps tab). What emulator/game are you having issues with?

@Rincewind Perfect. Been really enjoying this theme. Was able to quickly update all missing platform/playlist logos! Thanks again!

Thanks. I was sure it had nothing to do with the issue, but wanted to confirm.

Still having issues with latest beta not showing images in either custom folders inside a theme or custom image folders outside of a theme's folder structure. Jason is the above fix related to that?

@Rincewind with y2guru releasing the latest version a couple of days ago is that the version needed to be released to be able to use your files to make missing platform logos?

@kinoeye I did. I will have to check if I still have it when I get home. If so I will send you it.

Yeah this issue and the workaround was mentioned early on in the thread. I am confident The dynamic duo will have us squared away soon.

This is a feature of the current LB/BB build. The videos simply need to be in the console's respective video folder and named exactly as your game is in LB. The videos would then be named with a -01, -02, and so on after the game name. Just be sure it is "-01" and not "_01" (not underscore). Example: \Launchbox\Videos\Raw Thrills\H2Overdrive-01.mp4 \Launchbox\Vidoes\Raw Thrills\H2Overdrive-02.mp4

This is definitely odd as the Settings.xaml is where the issue normally is. It is possible one of the backups could be corrupted, but deleting it and letting LB generate a new one should rectify. Try copying the one from the new folder into the original build's folder.

This could be due to the Beta. We have been experiencing a few issues with the Beta and it has affected themes, startups, pause, and some other areas. I recommend going into your \Launchbox\backups folder and running the last stable version installer. Do not run beta 13.1 or 13.2. You can simply run the installer right over top your existing build. It will not affect settings. If the theme is back to working then it is likely a beta issue. Issues that occur when you update with a beta are best posted in the beta thread. It helps for better tracking.

Dod you try both ways mentioned?

Just remove the Settings.xml from your \Launchbox\Data folder. Then inside you \Launchbox\backups folder open one of the recent backup zipped folders and copy the settings.xml file from within that zip into the \Launchbox\Data folder. If everything returns to normal you can delete the corrupted one you moved out from there to begin with.

Ah I just tested the Unified Startup and I get the same thing. I had only tested on three Startups / Pause theme's I made that are using custom image folders. I did not try any themes from other creators. Regardless of which them I use though if I Change the image path to the full folder path that allows it to work again. Put it back to the relative path and it stops working.

Yeah Pause working ok for me as well. Only issue is the ones using a custom image folder outside of the theme’s folder will not show images, but it still functions otherwise.

No, this means you did not actually point it to install over the existing set-up. If you search you will likley find you have to instance of the Launchbox.exe somewhere. What we typically see when this happens is someone had it install in the Launchbox folder into another Launchbox folder. Look and see if you have \Launchbox\Launchbox\Launchbox.exe showing. Open you original LB folder and see if there is a Launchbox folder inside of it.

Glad your sorted. Saw Neil assisted in the discord. Dolphin never needed admin rights and neither does LB/BB. So no need to mess with setting admin.