Jason Carr

Typically requiring administrator permissions is caused by file permissions issues. Have you always had to use LaunchBox as administrator?

Hmm, that might be important to know. What folder is LaunchBox installed to?

When it does this it means that the previous instance of LaunchBox is still in the process of closing. I should probably put a better error message there for that situation.

Odd. It could be that it's still waiting on the previous launch to close. Most likely if you reboot, it shouldn't be an issue anymore.

Not if you transfer the whole set over to your Android device. It won't work for picking and choosing games though.

So it's been a pretty crazy past couple of days. I just put out 10.5-beta-2, which appears to fix an issue where controllers weren't working for Windows 7 users, because Windows 7 apparently does not support XInput 1.4 at all. So I'm now reverting to XInput 1.3 in that case. Any testing you all can do with 10.5-beta-2 would be appreciated.

Hey all, I have a new 10.5 beta out to address an issue with controllers not working properly on Windows 7. Details are here: If this confirms to fix everyone's issues, I'll put an official release out later tonight.

That is good to hear. I'll wait to confirm from the rest of you guys and then I'll probably put a fix release out tonight. It's worth noting that I did just put out beta 2, which addresses a minor issue, so if you guys can test with beta 2, I'd appreciate it. If you're prompted to update from here on out, beta 2 will download anyways.

Hmm, well I'm glad it's working. I really don't understand why that would fix the issue though.

So you're saying that your controller isn't working in Retroarch. What controller are you using? Can you try starting Retroarch without LaunchBox or Big Box loaded to see if it's actually LaunchBox affecting it?

Can you explain exactly what's happening? I'm not following. You're saying the controller isn't working in Big Box after launching a game? Are you on Windows 7 or Windows 10?

I just put out a beta release for testing. You can update to the betas by going to Tools > Options > General > Updates in LaunchBox and checking the box to update to beta releases. You may also want to uncheck background updates; that way you'll be prompted to update on restart of LaunchBox. If you guys can test this beta to see if it's working for you on Windows 7, I'd appreciate it.

Sigh, I failed to realize that XInput 1.4 is not available on Windows 7, which we're using for the new controller stuff. The irritating thing is you can't install it either; it's only available on Windows 8+. So it looks like I'm going to have to support XInput 1.3 for Windows 7 users. Working a solution.

I see. My current hunch is that something isn't working on Windows 7. I'll do some quick testing and report back. Thanks guys. If you want to, in the mean time you can roll back to 10.1 by running the 10.1 installer in the LaunchBox\Updates folder, and just installing over top of your current folder.

Hi Willy, just responded over here: https://forums.launchbox-app.com/topic/51925-controller-not-working/?tab=comments#comment-329085

Hi guys, sorry to hear about the trouble. First off, I'll need details on exactly what controllers you guys are using. Also, what version of Windows are you running? Windows 7 or Windows 10? We will get this fixed, but I will need your help to troubleshoot it.

To be honest, not really, but I guess it does make sense. Just tested it; I wouldn't call it a significant issue. If you set All Games as your default startup view, it does work properly after a restart of Big Box. Otherwise you just have a second view to go through to get there.

@Retro808 and I have done some testing here. Retroarch is apparently wonky in that it has some default bindings set for hotkeys that do some weird things, and the only way to fix it is to re-set those hotkeys. Basically, Retroarch's hotkey menu is lying in that there are controller hotkeys defined by default that don't show up in the menu (at least that's my best understanding of what's going on). What has fixed it for @Retro808 is binding the same buttons to the same functions in Retroarch. So, for volume up and volume down, bind the same two buttons to that in Retroarch and in Big Box, and in theory that should fix it. Ultimately, though, this appears to be a bug in Retroarch.

@dov_EL I've just confirmed that the volume issue was also an issue in previous releases of LaunchBox. Somehow, it has to just be a duplicate binding in Retroarch. I'll do some more research.

I mean for Big Box. Is this an issue only for the new releases of LaunchBox? Was it working properly with previous versions?

You might be able to, I'm not exactly sure. Whether or not you'll need to format the drive depends on how you want to use it. It gives you the option to use it as an add-on drive or as one for apps. LaunchBox is able to work with add-on drives though, so you shouldn't have to format it.

I just put out yet another new release, 10.4. There was an issue where Big Box was not always saving the bindings when clearing them. This is certainly interesting; I'm seeing Retroarch go fullscreen and back when I use my button combo. I'm guessing Retroarch can be configured to remove this button combinations. Is this new for the new release?

I'll answer what I know here. I don't think you can set up more than one drive, but there is no real size limit that I know of. I have a 4TB drive connected to mine.

Sorry, that file is LaunchBox\Data\InputBindings.xml.

Hi slush, can you upload your InputBindings.xml file here? I'll take a look and figure out what might be going on.