C-Beats

You can delete the BigBoxSettings file in \\LaunchBox\Data\ to reset everything to default

Not sure it's possible with the Windows Store version. Last I knew you have to have a cabinet code from Zen Studios to launch directly into a table, and they only give out codes for the Steam version (or at least according to their website).

You don't have to do it every time. Should be a one and done. You do need to do it anytime you use the Theme downloader though since it puts them in the root Themes folder and not the Core themes folder though. The reason it was implemented the way it was is because it works fine for the vast majority of users, and without the implement we would have had broken installs on literally everyone's install. exFAT isn't heavily used anymore, NTFS is the de facto format at this point and so we put in a solution for those users, and tried to find the simplest work around for those on exFAT who aren't willing to reformat to the standard format.

The code expects the themes to be in the original location though. The paths inside of the theme's XAML is what required that Core folder redirect thing so Cut process won't work unfortunately.

Yeah, we could look into something like that. The initial idea is that some Themes have a LOT of theme dependent art (like the original BannerBox theme) and copying that folder increases your hard drive footprint where symlinks do not.

There is not currently a way to do that. We do have a BitBucket ticket requesting exactly that. You can vote for it here

Works for me, thanks.

Yeah. I thought that may be the case. The issue is because the drive is formatted exFAT and not NTFS. To get themes to work properly you will need to copy the Themes folder from \\Launchbox\ to \\LaunchBox\Core and then update that folder whenever you install a new theme. It isn't the best work around but exFAT doesn't allow us to build the symlinks LaunchBox uses and so is the best we have come up with thus far.

@Amiiben18 Could you provide the following details: LaunchBox version, OS version, what format type is the drive LaunchBox is sitting on (ExFat or NTFS)

Could you post details of what you are trying to download when you see this issue into the beta forum? Also would be helpful to understand what version you are on, and what version you started the queue in. If possible attach a debug log of when this is occurring as well.

@SqHd Thanks for the report, we were able to track down the cause, but are still working out the best way to correct. @Chris Kant I could see something like that being useful moving forward, and before it was FAR more difficult to implement, now that we have the beta feature built something like that is far more doable since we have a lot of the pre-requisites now built. It isn't currently planned to implement that this release, but moving forward I would like to make that download process less disruptive. If you would, could you submit a ticket for us detailing what exact processes you are running into that are getting blocked by the image queue? It would be nice to have to keep track of what processes are being affected and give us a place to show progress to users if we don't get them all updated at once.

Most recent beta would only fix this if the queue was starting IN the most recent beta version (or potentially beta 5 depending on the image type). I would re-queue the downloads and see if you still have the issues. If you do please report it in the beta thread.

Beta 5 is out now with the following: Improvement: Now scrape controller support information for GOG games during import and in the Download Metadata tool Fixed: EmuMovies downloads were failing if in the download queue for too long Fixed: Mouse navigation wasn't working in Big Box Fixed: The download queue wasn't starting until after pressing "ok" when using the Download Metadata and Media tool

Your best bet would be to email support@unbrokensoftware.com. They will be able to assist you.

The additional apps have to have something listed in the version for them to be considered for the badge

No need. I have found what source is throwing the error and am testing code changes I hope will eliminate them. Thanks for the report.

Feel free to PM it to me. They are in your \\Launchbox\Logs\ folder

Are you getting an error or does it just close/crash? Turn on debugging logging, you should get debug log of what is going on and we can go from there. You're the first person to report anything like that with this beta release though (at least to my knowledge).

@TheNewClassics do you happen to have a debug log for when you were getting these errors? Would have more information about what URLs are throwing the error so I can look into some of the stuff @sevenalive was referring to and try to get that improved.

You could also opt into the beta build via the options menu. In the beta we do all import first then grab the media second to help with things like that.

What Neil stated isn't really a matter of opinion. It is how the tool does indeed work. That being said I can understand your point of view as well. I would suggest you go to the top of the page and click "Help & Support" then "Request a feature" and explain there how you think the tool can be improved to do what you are trying to do with it. Will help us keep track of the suggestion and allow other users to vote on it.

Did you restart the PC with LaunchBox open? May have corrupted your data files. I would look in the back up folders and restore the most recent backup and see if that corrects the issue.

Thanks for that, have gotten that fixed.

Thanks for that, it had a similar issue to the one we corrected in the Edit Game screen. It has been corrected and will be in next release. Until then if you remove the "Associated Platforms" from the controller you should see it on that list.

The process to add a new game controller support level to a single game you would do the following: Go to the game in question, and edit to bring up the Edit Game window Go to the "Controller Support" tab Press the "Add Controller" button In the row created in the left column (labeled "Controller") you select the controller this game uses In the right column of that same row (labeled "Support (Optional)" you select what support level the game has for that controller (can leave it blank if you know it uses it but aren't sure the support level) Press OK to save your changes You can then use that information to display badges or use them in auto-populate playlists