Jason Carr

Yes, you should be able to use either the .NET Framework or .NET Core.

Apparently .NET Core has some issues still with System.Speech. I didn't see that one coming. Here's a couple of links that may help: https://github.com/dotnet/runtime/issues/30991 https://www.c-sharpcorner.com/blogs/using-systemspeech-with-net-core-30 The first link has a port of System.Speech on Github that supposedly works.

@Armhunter I have not seen that. What type of controller are you using?

@Bernard Bernoulli When you edit the games, are the ROM paths correct?

You would need to copy the Default theme to a new theme, and then modify the XAML files. Shouldn't be too difficult, but would require a bit of learning to get it done.

@Elhora Your best bet is to keep everything together all on one drive, sans for the game/ROM files. Generally, the media and LaunchBox installation can be easily kept under the size of relatively inexpensive SSDs. Then you can place your game/ROM files on a different, slower drive (or even over the network), and there won't be much of a performance difference that way. So it sounds like you just need to move your LaunchBox installation to an SSD, sans for the games, and then change the game folder paths in LaunchBox separately for each platform under Tools > Change ROMs for Path for Selected Games.

Hi @Garydwh, what platform(s) are you getting that on? Is it happening every time? Can you zip up and PM your LaunchBox\Data folder so I can review?

Hi viking, they are playlists. The new cab images look awesome!

What was the specific permission error?

Check your Image Group drop down at the top of the LaunchBox interface, and make sure it's set to Boxes.

I've updated the script in the first post of this topic with the above fix. It's working for me.

@The_Keeper86 Try running these commands: wget http://aka.ms/vs/16/release/vc_redist.x64.exe WINEPREFIX=~/LaunchBox wine ./vc_redist.x64.exe /passive /norestart WINEPREFIX=~/LaunchBox wine ./LaunchBox-11.3-Setup.exe /DIR=C:\LaunchBox /SILENT I think that will fix it. I'm gonna update the script with that in a second here.

Where in the process are you getting those errors? The second one (http one) means that it's trying to download a pre-requisite that should have already been installed.

Ah, I see. Might be a bug in the startup process because of the duplicate apps running for a short period. I can't reproduce it myself though. If you can get me the exact error message, that might help.

Wow, I have never seen that before. Sorry for the late reply here, first time seeing this thread. It must be somehow specific to certain machines, yes, because I've never run into it. Do either of you have anything interesting or out of the ordinary on those machines that could be causing it? Hopefully we can figure out how to reproduce it and get it fixed, but we'll need to be able to find some common ground first.

The good news is that LaunchBox does its best to use relative paths wherever possible. So unless you override it, as long as everything is on the same drive, it should work to relocate it all, yes.

Actually no, that's not true lol. It had to do with the .NET Core upgrade.

Yes, I honestly wish I had a solution for you. Unfortunately I spent 3 days searching for a solution that did not involve the folder symlinks during development, but there just wasn't any other options. You may be able to manually create the necessary symlinks, but I'm not sure if that's possible over a network drive. Certain themes may also not require the symlinks, and most themes can be upgraded to not require the symlinks in the future. If you're willing to restructure, I can recommend FreeFileSync as an alternative. You can keep your files in your network share and sync them to your various machines (though of course that requires more hard drive space). I find it extremely convenient though because I can always easily undo any changes and re-sync.

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: