Jason Carr

I just put out beta 2; I believe I finally figured your issue out. The controller automation features were not working properly in LaunchBox *if* pause screens were disabled. So hopefully this version will fix it for you.

Beta 2 is out now with the following fixes: Fixed: LaunchBox controller automation features were not working properly in some cases with pause screens disabled Fixed: The new controller mapping features were slightly misleading as they allowed free users to map controller automation features, but they do not work without a premium license

Hmm, by chance, is your LaunchBox licensed? I just realized that the controller automation features do not work if you don't have a license to LaunchBox Premium on the LaunchBox install. I know you have Big Box though, so that wouldn't make too much sense.

Hi Bobby, that issue is specific to the PCSX2 emulator, which doesn't look to be installed properly. You will probably need to re-download/reinstall PCSX2. The new beta is out; you can update to the beta by going to Tools > Options > General > Updates in LaunchBox and checking the box to update to beta releases. Uncheck the box for background updates and then restart LaunchBox and you should be prompted to update.

Okay, I tested your InputBindings.xml and didn't have any issues with exiting games or opening the Pause menu in LaunchBox. Tested with an Xbox One controller and a PS4 controller via XInput, and the PS4 controller via DirectInput. So I'm baffled here. Can you zip up and PM me your entire LaunchBox\Data folder? Don't upload it here for security reasons.

@Android16 Also, if you're willing, do me a favor and zip up and PM me your entire LaunchBox\Data folder. That may help me with the bindings issue.

The bindings reverting thing is definitely something I need to figure out. The code is set to populate the bindings fresh, if and only if the InputBindings.xml file doesn't exist. By chance, are you removing this file? If not, then I need to figure out why on earth that's happening. Per the scrolling delay, I didn't understand that the issue was unrelated to controllers. I haven't looked into that one yet.

I think the issue is more likely to be a conflicting mapping elsewhere, than those certain mappings. Can you attach your InputBindings.xml file here?

What are your controller mapping settings in LaunchBox? I'm guessing that there might be a conflict in there that might be causing issues.

I have this on my list to look into. I wasn't aware that bindings were changing with updates. Did it change when you updated from 10.5 to 10.6-beta-1? That's new to me, and I haven't heard of that happening elsewhere. I also haven't heard of this elsewhere. Can you explain this issue?

The new beta is out. Details are here: Let me know if anyone is still seeing any controller issues after updating to this beta. Thanks!

Thanks guys. I just put out a new beta, with details here: I'm hoping that the new beta fixes any remaining controller issues. Let me know.

The first 10.6 beta is out here: I am hoping that it resolves any remaining controller issues. Please let me know in the above thread if anyone is still seeing any controller issues after upgrading to 10.6-beta-1.

Hey all, the first 10.6 beta is out now with the following two fixes: Fixed: Errors were sometimes occuring when using the "Switch to Desktop Mode" option from Big Box Fixed: When using more than one XInput controller, the second, third, or fourth controllers were not always working I currently don't plan on pushing out an immediate release for these. I'll be back to more poll items for the 10.6 release here soon. The second item above, which is related to controllers, may solve more issues than what are immediately apparent.

Hi guys, I think I have a solution for this stuff (the BlueTooth weirdness). I have a new beta coming out shortly.

This is honestly the best place to troubleshoot. I'm going to put out a beta later today that might help, so hold up for a bit and we'll test it.

Okay, thanks for the details. I can't explain what happened the first time through, other than maybe some incorrect controller mappings. But glad it's all working. MAME does have a known issue where it refuses to accept simulated inputs if you use the wrong input engine. That shouldn't be an issue though if you use "-keyboardprovider dinput" in the emulator command line options.

Currently, you will need a collection on the PC; that's the only way to set it up for the moment. I'm adding features in the future to be able to set everything up directly on Android, but that will be a bit yet.

Hi Bobby, I'm testing with mine and not seeing any issues. Do you have any controllers listed in your controller settings?

Hey guys, sorry for the issues here. I'm currently working on a beta and have some other controller issues resolved, but for the life of me I can't seem to replicate any issues closing down emulators with the button combos. That said, this thread is extremely confusing; can you guys detail for me the exact issues that you're running into with version 10.5? My understanding is that the exit emulator button combo is not working, but I need to figure out what the difference is because I'm not seeing any issues with it. @klepp0906 @Terminates Here

LaunchBox does use .NET 4.8, so that could be the issue here. You'll definitely need to make sure that 4.8 is installed properly in order to use the latest versions. That said, version 9.10 still uses .NET 4.7.2, so if 9.10 doesn't work, then that's probably not the issue. It could be that somehow Windows got corrupted during the update. I would make sure that all Windows updates are installed. It might be worth trying to install a fresh copy of Windows 8.1 (or better yet Windows 10), if that is a possibility. I honestly have not done any testing on 8.1 in a very long time, as very few people are running it, but I see no reason why it wouldn't work.

Sorry to hear about this issue guys, and very sorry for the late response here. I'm just now seeing this thread. That is a strange issue; I haven't been able to replicate that. It is possible that it got fixed in a later beta though. Regardless, if it's not working to automatically copy the files over to your phone, you can simply do it manually by just manually copying the files over from the export folder to your device.

Glad it's fixed. Outside of duplicating videos, I don't think we have an option for that currently. Although you could certainly create a custom theme to do it.

I just tested for this, and it's clearly a Retroarch issue and not a LaunchBox issue. I went back and tested it with LaunchBox 9.10, and it was definitely still an issue back then, so clearly it doesn't have anything to do with any recent controller changes. Retroarch just appears to be bugged with the controller shortcuts out of the box. The only solution that I've found is to override the shortcuts so that Retroarch stops using invalid defaults.

@dov_EL I'll note that, but unfortunately I can't go making changes to the startup screens right now. I don't think that's a common issue, because most people aren't experiencing that slow of emulator load times. Startup screens were always known to be slightly finicky, which is why I waited years to even consider tackling them. So we'll have to live with them as-is for now.