Jason Carr

I hadn't planned on prioritizing that for soon, but I'll boost that up a bit higher on my list. Wow, that is exponentially slower than what I've seen. What was the total number of games you exported? That's probably easiest to check on the desktop. Where in the startup process does it spend the most time? What's it say when loading? Is it the Data portion?

Okay, good to know. When you connect through Steam remotely, what controllers show up in your controller list? What are their names?

Yes, I do believe that is most likely a beta issue, or at least there's a good chance that it is. I'm actually working on overhauling controllers with the betas. And yes, you can just install the official version over top of your existing folder. Just make sure you install to the correct folder, and not a subfolder.

Thanks for the purchase. I would highly recommend though sticking with the official 10.1 release for your initial setup though. Jumping straight into the betas probably isn't the best idea.

I see. The exporter currently does not automatically export all the files in that case, so it will probably work if you manually copy over the missing files.

Okay, I'm not overly familiar with CDI and GDI files, but I'm guessing that Redream on Android just doesn't support those GDI files. I don't think that's a LaunchBox issue. As far as I know, GDI files do not need extracted, as they are not archives.

Sadly the Android version doesn't (yet) support extracting RAR files on game startup; it only supports extracting zip and 7z archives. So if the emulator doesn't support the RAR files directly, currently the only option is to extract them on PC before exporting them.

If Redream isn't running the ROMs when you run them manually, then that would be the issue I guess. What file extension are the ROMs? Are they actually zipped?

Yeah, I have plans for that long-term, but multi-select is proving harder to implement than it should be, so I haven't prioritized it as of yet.

Yes, we're still a ways out from Big Box themes. Hi Solo; I'm sure we'll get custom configurations in there eventually, but to be honest I don't think it will be a priority because I doubt very many people use them. There's always stuff I can do to help with performance and such, but what device are you using and what are the actual startup times? This is the first I'm hearing of them being an issue, and it's usually less than a second or two. I'll add that core and that emulator to my list to add. Yes, eventually. I was looking for a way to do that currently, but it was proving way to time consuming because I was having to reinvent yet another wheel. But yes, I can't imagine we'll be able to continue on forever without multiple selection. @nearvanaman @Soxbrother No idea why XML files would be getting corrupted when you edit them. They're just simple text files with an XML extension, and they should be perfectly fine to edit in any text editor, including Notepad. I have noticed though that sometimes the Windows functionality to copy files to Android devices can be sketchy, especially when copying files multiple times, so who knows, maybe that was the issue.

I can confirm that LaunchBox won't access any ROM files while simply browsing, only once a game is launched, which I believe should alleviate your concerns.

Thank you Chunk; all of those features are definitely planned, and most of them are coming soon.

Hi guys, I fixed a bunch of Direct Input controller stuff in beta 3, which just came out. Please let me know if you're still seeing issues with beta 3 in the above scenarios.

If you've updated from a non-recent version of LaunchBox, it may be that parameters were added to your MAME emulator configuration in LaunchBox. This is only an issue for really old versions of MAME, but try removing "-keyboardprovider dinput" from your command-line parameters for MAME.

Eventually I'm planning on adding controller-specific configurations (different bindings for each controller). When we tackle that, I'll make sure to cover this. As for right now, though, doing that properly would require tracking controllers separately, and currently they're all combined, so I can't really make that happen until we do that restructuring. Trackball support is completely separate code than game controllers, so unfortunately no, it's not something I can slip in right now. I actually have a version of the code in progress for trackball support for Big Box, but it proved to be more extensive than I had originally thought, and sadly it hasn't seemed to garner a whole lot of interest so I haven't been back to it as of yet.

Beta 3 is out now to fix issues with some DirectInput controllers. Ended up picking up a few of them to test with; let me know if anyone sees any further issues with any particular controllers.

I have an idea as to what is going on with the mapping stuff. It should work perfectly fine with XInput controllers (360, Xbone, PS4), but some DirectInput controllers treat the trigger axis differently, and I think that is causing it to not map properly. I have a controller coming in the mail tomorrow that I can test with.

Thank you guys. @rodww As much as we all want everything to be free, that's not how businesses work. You're only the second complaint we've received about it not being free since we released the app, and the amount of purchases we have coming in confirm that people are happy to pay $5 for the app. We've never promised that a license on Windows would ever work on other platforms, and since Android requires separate code and completely separate work than the Windows version, it only makes sense for it to cost at least something. Per it requiring the Windows version, that's a moot point since it only requires the free version of the Windows app; it doesn't require another purchase.

I managed to get it working, and it does seem to be working fine with the guide button. I had to reboot to get it working again though. I'm not sure what made it stop working, but I'm guessing it was connecting my Xbox One receiver/controller. Why would you use the controller in Switch mode on PC? For setting the button combination, go slowly like this: Press and hold the first button. Press and release the second button. Release the first button. If you do that out of order, it doesn't always register. Does that fix it when the controller is in XInput mode? What are the reasons to use the other modes?

Alright! Beta 2 is out now with a huge game controller overhaul: New Feature: Game controllers have been completely overhauled in both LaunchBox and Big Box! See below. New Feature: Xbox 360 and Xbox One controller guide buttons can now be used anywhere (from the poll) New Feature: Multiple controller bindings can now be used everywhere New Feature: All controller bindings can now be a button combination if desired (and the opposite, controller automation bindings that used to require a button combination can now be mapped to a single button) New Feature: Left stick, right stick, and trigger axes can now be bound to actions, and buttons can now be bound to navigational movement This stuff will need some significant testing. Let me know if anyone runs into any issues. Also, those of you who have PS4 controllers, if you can test them, I would appreciate it, especially support for the "guide" button in the bottom center. My understanding is that this button only works in XInput simulation mode, but I'm finding DS4Windows to be a bit finicky and couldn't get it to work (might be conflicting with my Xbox One controllers).

Sure, I can add the field easily enough. But yeah, I've already determined that using checksums isn't anything that we're going to tackle ourselves, for various reasons. But yup, it's certainly open to the community to try it.

Hi @KillerQ, this is definitely planned.

CRCs aren't consistent enough to really be effective in that way; I've looked into to doing that in the past, but there are way too many versions of ROMs. But anyways, new features for Retro Achievements was on the poll and got voted fairly highly, so I will be doing that soon, and I'll plan on adding that field when I do.

Yes, matching is done on platform and title only, which is unfortunate. Sadly, though, there aren't really any other options, or at least there wasn't back when I implemented it. There is no global "ID" that identifies a game that everybody knows. So it basically comes down to matching by platform and title; that's all we've got. The only other solution I can think of would be to provide a field in LaunchBox for the user to manually put in a Retro Achievements game ID. If anyone knows any other way, let me know, but I don't believe there is one.

Most likely this is caused by a stray game controller, not a mouse device. Also, it sounds like you're trying to use the new data restore feature to go back to a previous version of LaunchBox, which isn't going to work. You shouldn't need to go back to a previous version currently, as I'm almost certain you'd have the same issue. Just need to figure out which game controller is causing issues.