C-Beats

I don't foresee us dropping Windows 10 anytime soon. The ONLY reason we dropped Win7 was because one of our dependencies did. I personally am on Windows 10 and have no desire to move to Windows 11 and so will be personally pushing to stay on that OS for as long as I can. That being said I don't make any final calls in regard to any of this so can't really make any guarantees on the matter.

Please post errors in beta version to the beta thread so we can keep track of them and ensure they aren't a new error caused by a change we made.

I believe this bug is address in the recent beta update. You can go to LaunchBox and opt-in to beta updates to grab it and see if that resolves your issue.

While we appreciate any constructive criticism's from users (new or long standing) I'd also ask you take the time and attempt to use the software as it's intended before making any final calls. If all you want to do is use another program as if it was Hyperspin than just continue to use Hyperspin. The way other software work will not be the same and it won't correlate 1:1 in almost any way. Things like the insistence of using RocketLauncher will only cause undue headaches for very little gain and will inevitably sour your experience with the application. LaunchBox is open ended enough that it'll let you do a lot of interesting things if you want, but the more you fight against the intended use of the application the more manual and grueling your migration process will be. As you've seen should you run into issues in your migration the forums are always willing to help out, you just got to be open to the fact that the most correct steps in how to achieve what you're trying to do WILL NOT be the same as they were in your previous set up.

13.17 IS the latest version. We dropped a beta update of version 13.18 Beta 1 yesterday. Beta updates require you to opt into them in the options menu (Tools > Options > Updates). Go to the page and check the box and then you will detect beta updates. Beta updates are more prone to errors/bugs since they've only been vetted internally and haven't been tested en masse by users though and so you need to be aware of the potential drawbacks. We do our best to ensure all beta releases are stable, but unfortunately that's not always the case.

I added the alias and then manually refreshed our metadata.xml files server side. Inside of LB go to Tools > Download > Force update local games data (bottom most item) and then try to scan again

There were a few bad records in the DB again, I cleaned them out and should eliminate the error.

Yeah, if the cause is something similar to before the less items in the queue the more often you're going to see it since the odds of tripping on the bad record are increased. I'll take a look and see what I can find out. Thanks for the heads up.

Locking thread as I can see this going no where positive for any party involved.

Can just look in the Alternate Name section of the game and select the English translated title (if the DB entry has one for that game). May need to update your metadata from the DB to get the newest strings first though.

Right... so you don't actually want duplicated platforms. You want two separate ones. Select the games from the one that needs to change (can hold CTRL and select multiple) and then press CTRL+E to open the edit window and change them to the new platform. Doing so will change the platform they are associated with and move the media accordingly.

The way the one-year license works is that you gain access to the premium features within the app now and for any future versions that are released before your license expires. You CAN use newer versions after that but the premium features will be deactivated since your license is not valid for them. You could optional decide to use the latest version your license IS good for forever though. If the newer version doesn't have a feature you care about you can just stay on the version you have premium features unlocked for.

This may be related to a bug we found internally that will be corrected in next release. Do you run into the issue if instead of pressing back to return to your default filter you go to the "View Platforms" (or what ever filter you want)? If it's the same thing that navigation method should work where simply pressing back wouldn't. I'd also like to point out the issue found internally is a CPU timing issue so not everyone will experience it. Thankfully my machine did and I was able to use that to get it corrected.

Code changes were just pushed to the server and the temporary fix removed. Not sure we got ALL the cause for errors, but should have at least nipped some of the more pressing bugs in this code change. I'll continue to monitor from my side, but let us know if the issues start to creep back in on your side of things.

This error indicates you have bad data in your local Games Database definition file (\\LaunchBox\Metadata\Metadata.xml). To correct please open LaunchBox and go to Tools > Download > Force Download Games Database Metadata (last option in that menu). Doing so should correct this error.

I have updated one of the processes that fetches the moderation item for you to skip these obviously bad change sets in an effort to keep the DB running smoothly while I track down the change. It MAY result in the page taking a slight bit longer to fetch a change to moderate but should stop the error from occurring at all. This will get reverted once the bug is found and the permanent correction is pushed to the server. Thanks all for the help tracking down this issue, and the patience in it's resolution. Both are much appreciated.

Thanks for confirming. Feel free to post up in here if that changes for you.

Thanks I looked in the DB again and found a few more bad change sets that were clogging up the system. We're looking into how these keep getting the in the DB. I'll do my best to update the thread when any new code gets deployed. I'll do my best to keep monitoring the DB until then but feel free to let us know if you keep seeing the issue. Will help us determine if we're looking into the same issue you're all getting tripped up by.

Thanks, had a few bad change records that were failing to apply. I cleaned them up which hopefully removes this. Let us know if you keep seeing it.

What you're asking for has been in the app for as long as I've been around (at least 6 years). In the Edit Playlist window for your playlist on the first tab set the sort to "manual" and then in the games tab order the games the way you want.

Inside the marquee views is an "IsActive" binding you can use for this purpose. When true Big Box has focus, when false it doesn't (typically because you're playing a game)

Close LB, navigate to \\Launchbox\Data\Settings.xml and open the file in a text editor. Look for the line that says "ControlsBarHeight" and set that to something like 56. Save the file and close it then reopen LB. You can hide that control entirely in the view menu or by pressing CTRL+SHIFT+B as well.

Known issue with Intel integrated graphics cards. You need to go into the Intel software and turn anti-aliasing for Big Box either on or off (auto is the default). For some reason their auto logic makes some poor choices and causes issues like what you see. Having a service called "nahimic" running will sometimes do similar things but Big Box should check and alert if you if it finds that already. If you didn't see that message my guess that it's the intel gpu issue.