Jason Carr

Okay, good to know. So perhaps exFAT has issues with creating symlinks, sigh. I'll look into that.

We have noticed weird things like this with certain cores in the past, but it's always been an issue with the core. Unfortunately I don't have any experience with that core, so I can't help out much here.

It could be the file system on the external that is causing the trouble. Can you check if it's NTFS, exFAT, or FAT32? If I had to guess, it's probably FAT32 which is causing the trouble.

We'll do some testing to see if we can replicate any issues with the Windows import in the new release. In the mean time, all you have to do to import Windows games is simply drag the shortcuts onto the LaunchBox interface. Yes, we were aware of that false positive. We generally don't work at getting around anti-virus false positives for the beta releases, but we do for the officials. I've seen that recently from one other user as well; unfortunately it's a video driver bug that causes it (and was mostly fixed for the other user with a video driver update). Can you try updating your video drivers? You can safely install 11.2 directly over top of your LaunchBox folder. Not the Core folder, but your original LaunchBox folder. Watch carefully though in the installer, because if you browse to a folder, it will automatically put \LaunchBox on the end of it (which makes sense for new installs). Just check the text box after browsing to make sure you've selected the correct folder and not a LaunchBox\LaunchBox folder.

The Escape key is handled via an AutoHotkey script. Tools > Manage Emulators > Snes9x > Running AutoHotkey Script tab. If you clear that script out, it should stop that functionality. I think you might want to leave the top comment line though, so that it doesn't replace it with the default script. Here's a copy of the Visual C++ redistributable (assuming you're running 64-bit Windows): https://www.dropbox.com/s/ifjy6o1y1gqc52k/VC_redist.x64.exe?dl=0 That should solve it for you, though not sure why the setup isn't automatically installing it. Do you have Internet access on your LaunchBox machine? Sorry for the issues you've been having. Unfortunately at least some of that is a Windows issue, and has nothing to do with LaunchBox (Windows Explorer crashing, for instance, obviously is not related to LaunchBox). It sounds like there may be other issues on that system that could be causing some of this trouble. We can troubleshoot the individual issues here though if you're still having them and you're interested in getting us more details. Let us know if you're still having any of those issues and want us to help troubleshoot them.

It looks like for some reason Big Box was having trouble creating folder symlinks in the Core folder. Those theme issues are what happens when the links can't be created for some reason. By chance, are you running LaunchBox over a network drive @angelobodetti?

Should just be navigate up and down, if the wheels are scrolling.

If boxes are scrolling because of the pedals, you should be able to just clear out the controller bindings for scrolling boxes under Tools > Options > Game Controllers > Mappings.

@Owls21 To be honest I'm not sure what happened here. If you're willing to try upgrading again and provide more info (screenshots or exact error information), I can help you troubleshoot this and get it working.

That was a really good idea @Kuro Houou. Glad you found a way to pull it off.

Did you install 11.3 or 11.4? Can you try downloading and installing 11.4 over top?

Yes, just copy the whole folder. Unless you've put things in non-default locations, that should work well to back it up. In the setup, just check the actual text box folder path before continuing and make sure that it's C:\Users\TBTol\LaunchBox.

@games I just tested a fresh install, and the Metadata.xml file showed up fine in the Metadata folder. My only guess is that maybe it's being removed by some kind of over-zealous anti-virus app?

@starfiretbt If you install LaunchBox over top of your existing install, you won't lose any data. Just make sure that you install to your actual LaunchBox folder, and not LaunchBox\LaunchBox. Pay close attention when you select the folder.

@starfiretbt @Tezza77 What version of Windows are you guys running? What particular error messages are you seeing?

Yeah, I wish. Unfortunately there's no quick or easy solution for that (or really a solution at all, sadly).

Yeah, that's pretty odd. First I've heard of that too. Video drivers are often cause for some weird issues though.

Here's a zip of the exact version that we include with the installer: https://www.dropbox.com/s/kfvekinxcz2ygik/DirectX.zip?dl=0 Unfortunately if there's an issue, it's not likely from doing anything exotic, more likely just a Windows bug that came from an update or something.

@theflashmastab Unfortunately I think this is likely a system issue. The DirectX installer is straight from Microsoft, and if it's causing the system to reboot, there's probably something going on with the system (I also haven't heard of this from anyone else). Can you post the event entry here so I can confirm?

@NOMAD0P It is what it is. The C++ update is required because we needed to update to the latest version of the Chromium web engine. It's either that or we choose not to update those things and end up with security issues. Would you rather that?

Nothing was changed controllers-wise for the 11.3 update, so I'm not sure what would be different there. I don't have my Logitech setup out right now to test with though.

Yes, the shortcut thing can simply be fixed by unpinning and re-pinning while LaunchBox is open. But the shortcuts have nothing to do with your data, so that shouldn't cause any trouble from that front.

Unfortunately we need to reach out to @eatkinola for an update to the plugin. That's my fault (I had to move the Meta.Vlc stuff to it's own DLL). Should be a simple change for him to make, at least. Good to know. We'll take a look.

Thanks Keeper, I'll be back to this here soon. I had some fires to put out with the release here first.

Thank you Brett. I do need to clarify though that a native Linux version isn't likely to happen any time soon. Keep in mind that over 7 years of full-time development have gone into LaunchBox and Big Box on Windows, so as you can imagine, starting over for Linux is somewhat of a pipe dream.