Jason Carr

Yeah, it's super easy to have more than one instance of LaunchBox with separate collections, so that is what I would recommend. We probably won't add a whole new set of features for multiple MAME collections, because that's mostly useless sans for the Android export process. Also, I expect that Android will soon do a better job supporting modern/recent versions of MAME. Retroarch already has a recent MAME core, but only in the 32-bit sideloaded version.

Just responded to this in your other thread. Have you checked the box for use all controllers? To be honest I haven't specifically tested for this, but I'm also baffled how that could be a new issue with the changes that were made. Unfortunately I'm out of the house for the next few days and I have my laptop with my development stuff, but I don't have any controllers with me (that was dumb). Can anyone else test this?

Unfortunately I don't think it would be that simple for the TargetUpdated thing. Not every button press does something that would result in that event happening. Though I do understand the issue. Per the delay, that's odd; I don't think that was ever intentionally added, nor was it intentionally removed. In fact, I don't think I added or removed any delays at all. It could have been a side effect of something though I guess. I'll see if I can play around with that here at some point.

Also, are you running Windows Media Player or VLC for your video playback engine? What Big Box theme are you using?

Okay, well that's good to know. I haven't seen this reported by anyone else (yet), so it doesn't seem to be a widespread issue, but it's still something that we should figure out. Does it still happen if you plug your PS4 controller in via USB? Do you have any other controllers to test? If I had to guess, it's most likely a driver issue of some sort (most likely video drivers). If you can, try running all Windows updates and update to the latest versions of your video drivers.

Per version numbers, yeah, it's not ideal, but it's also not that big of a deal. I do my best not to run these forums with a bunch of over-bearing rules.

I'm baffled here. Forget DS4Windows for a bit. Turn it off completely, and plug in your PS4 controller via USB. Do you get a "Wireless Controller" option to show up in the controllers list? It should show up, and should work, although it's Direct Input and not quite configured correctly. From there, try starting the latest version of DS4Windows, while still connected via USB. Then you should have two more options show up in the game controllers list in LaunchBox. Also make sure every other potential controller is disconnected when you run these tests, and reboot before trying them. That's a brute-force approach that should hopefully help.

The only thing I am aware of is that there are lots of other programs that can conflict with it, such as Steam. So try closing out of every running program and see if that fixes it.

We haven't made any core changes to the data saving or loading, so this is most likely unrelated to the new release. More than likely it's just a failed backup or a failed restore. The data files are all simple XML files, so there's no reason why they should be difficult to back up or restore. It could have been because a file was in use during the backup operation.

To be honest, I don't receive many requests for improving the search, but I will take note of this for the future. I'll put it on the list of potential items for the next poll as well.

This is a known issue with the current version of the exporter. We do hope to improve this in the future, but for now you can just manually copy over any missing files, as Neil suggested.

This is actually always been an issue (I've never specifically addressed it). It's on my list though.

DS4Windows is working well, yes. There aren't currently any betas out. The 10.5 release is the latest release.

I'm guessing this is most likely due to the new data backup engine. I'll check it out here soon.

Hi @Skyroller, as far as I know this is not happening for most people, so we'll need to troubleshoot to figure out why it might be happening on your machine. What version of Windows are you running? What controllers are you using? Does it happen if you use the keyboard instead of the controller? Do you have startup and/or pause screens enabled? Does disabling those fix it?

Eek, that's weird. You can run the 10.5 updater from the LaunchBox\Updates folder and just manually install to the correct folder.

Sure, thanks for following up with me.

Thanks much. I suppose it's possible that the new controller requirements could be causing issues with needing admin rights. I doubt it though.

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.