Jason Carr

Backwards compatibility for themes is the gist. It's a long and drawn out answer, unfortunately. Here's a link to 11.2: https://www.dropbox.com/s/cg7fteljnwf0s9r/LaunchBox-11.2-Setup.exe?dl=0

Hi Nate, the Arcade.xml file is located under LaunchBox\Data\Platforms, and apparently it did get corrupted. Your best bet is probably to restore from a backup. You can restore using the Tools menu in LaunchBox, and you can pick from any of the backups in the LaunchBox\Backups folder.

Unfortunately the .NET Core upgrade forced our hand on this. You can easily roll back using the 11.2 Setup in the LaunchBox\Updates folder, but I can't promise that we'll be fixing that particular issue.

LaunchBox is trying to create a symlink for LaunchBox\Core\Themes to automatically go to the LaunchBox\Themes folder, but it appears that it can't over the network drive (though I'm not sure why). It may be that that is not supported for network drives in Windows though, I'm not sure. Regardless, we do not recommend running LaunchBox or Big Box over a network drive; that is an unsupported scenario. You can certainly put ROMs on a network drive (I do that myself), but putting the actual app on a network drive is not recommended.

Hi @Kuro Houou, is that a network drive? It looks like it's having trouble creating the necessary folder symlinks.

I highly recommend FreeFileSync. It won't likely do it automatically when you plug the drive in, but it is scriptable and you could set it up to do that.

Big Box is the home theater or arcade cabinet interface. See here:

To be honest, if you were just introduced to LaunchBox, it may be a bit too advanced for you at this point. The first post of this topic gives you all the instructions, though.

Hi paQ, I just logged in without issues. Is it still not working for you?

You mean like C:\LaunchBox? What are the exact errors you're seeing?

Gotcha. It should be an easy fix, in theory. Just delete the My Documents\Emulators\LaunchBox\LaunchBox folder. Then run the latest beta setup and make sure to install to the correct location.

Wow, that could have actually caused a lot of the issues you've run into recently. Glad you found it.

If you don't have any data, it sounds like you installed it to the wrong place. Usually this happens when you accidentally install it into a folder inside of your LaunchBox folder. What folder did you install LaunchBox to? Do you have a LaunchBox folder inside of that folder?

I did indeed. Great to hear. I plan to release the official version tomorrow. The gist of it was that the new version of the Chromium engine needed the Visual C++ 2015 redistributable to work.

@luvablemarmot @im_etten 11.3-beta-19, which I just put out, should resolve all the issues. You can download it here: https://www.dropbox.com/s/firlwbtu76rwvxj/LaunchBox-11.3-beta-19-Setup.exe?dl=0

Beta 19 is out now to resolve a number of setup issues, and now automatically downloads and installs the Visual C++ 2015 redistributable if needed. This is a release candidate, and I hope to (re-)release 11.3 tomorrow morning. If you're already on 11.3, you can go ahead and just stay on it, as the only thing that will change for the new 11.3 release is the setup, and if you're already working, then you have no need for it.

This is just how Microsoft decided to make the project files work for .NET Core. There's really nothing we can do about it, and I don't see how it's any kind of an issue for end users, but if it bothers you, you can safely distribute themes without the project file (it's only used for development).

@Wanderer189 Good to know. Did you get it all resolved then? What was the specific issue with the paths?

It probably is for certain views, unfortunately. CoverBox has different views set up for each platform, so you may find one that it doesn't work right for. I believe what it does is centers the selection in the text lists.

Pretty sure we finally have this figured out (from another thread). Can you try installing this: https://www.microsoft.com/en-us/download/details.aspx?id=52685 You'll want the 64-bit version. I expect that will fix it. We updated Chromium, which apparently now requires that. We'll integrate that into the installer here soon.

Well holy crap. Thanks for helping me figure out. Now, what I absolutely do not understand, is how completely fresh installations of Windows 10 are working for me without that. But I guess we will cut our losses and add that to the installer lol. I blame Google. This is all because we updated to the latest version of Chromium.

That might be really helpful, actually, but I'll need to do some prep first. Actually, I might have just stumbled on the ridiculous issue. I found this: Does it happen to work if you download and install this: https://www.microsoft.com/en-us/download/details.aspx?id=52685

Same issue as we're dealing with in this thread: But I can't for the life of me figure out why it's not working on certain machines...

@luvablemarmot Are you running 32-bit or 64-bit Windows 10?

@Boomerps2 @jeffbini Again, my apologies for the trouble. I just put out a new beta that I'm hoping will fix the issues, but I could use your help to test. You can download the beta here: https://www.dropbox.com/s/firlwbtu76rwvxj/LaunchBox-11.3-beta-19-Setup.exe?dl=0