Jason Carr

Just in case anyone else finds this, there are a few possibilities if this happens: You're using a known throw-away email address We've already sent you a download link recently You've entered an invalid email address

You should be able to re-map the buttons in the various emulators, but you'll probably need to do that for each emulator. I don't know how to re-map everything system-wide. Also, if that menu button isn't working, unfortunately I don't have any ideas for a fix for that. I've been using an ipega BlueTooth controller that surrounds my phone, so I haven't played much with an Xbox controller on Android.

Good to know; I've put this on my list.

You can long press with the select button (A) on an Nvidia Shield TV controller. Not sure how you would handle that with a keyboard though...

This looks to be an issue specific to the theme, or a really old syntax that accidentally got removed. We're working on a fix.

Can you take a look at the application path field of a few of the games that worked, and a few of the games that didn't, and compare them? Maybe post them here?

@Leiard From what I've gathered in other threads, there may be some issues with really old versions of Android, like 5.1. I have this on my list to investigate.

Also, we did implement this waaaaaaaaaaaaaaaay back. MAME software lists should get translated to their actual game titles. I haven't tested this in a long time, but this feature has existed for a while.

Hmm, I'll add this to my list to review. It's strange that it works properly on some platforms but not others though. Maybe the Sega CD games are pointing at the bin files instead of the CUE files?

Here is the list of what we check in order to determine if a game supports MAME high scores: The game application path field must end either in .zip or .7z The game's default associated emulator's application path field must be either mame.exe or mame64.exe The game's default associated emulator's name must contain "MAME" The game's associated platform name or platform Scrape As value must be Arcade or MAME The LaunchBox\ThirdParty\hi2txt\hi2txt.zip file must exist (installed by the setup) That hi2txt zip file must contain the game's ROM file name The ROM file name must not be on our short list of exclusions (broken games)

Iirc, there is a way to connect PS3 controllers in a way that does not make them mimic 360 controllers (just with DirectInput instead of XInput). But that's about all I know; it's been a long time since I played with any of that.

Yes, unfortunately the ROM copy tool does not work with MAME games, only traditional console platforms.

There is a keyboard binding available for "Switch Image Type". Perhaps it's just stuck on the wrong image type? You'll need Big Box to be unlocked in order to change it, in case you set up a lock pin.

They should be imported to a platform called MS-DOS. Do you have a LaunchBox\Data\Platforms\MS-DOS.xml file?

If you have a decent Android phone, I'd say use it and pick up a Glap or an ipega controller.

It does run on Android 6, but Android 6 isn't recommended (we recommend at least Android 10). However, since I don't have one of those to test with, unfortunately I can't guarantee that it'll work. Looking at the specs though, it is rather low-end (especially the RAM), so it might be a bit of a dice throw.

LaunchBox for Android 0.38 is out now with the following: Added a new option to "Skip Menu and Play Game on Tap", which will remove a step and allow you to immediately play games without pulling up the game menu; if enabled, you can still access the game menu with a long press Emulator settings can now be overridden on individual games via the game menu Fixed the DuckStation emulator to no longer have issues launching games

Yeah, that's the thing. Some emulators are (sort of, kind of) easy to figure out, while others literally require access to the code or for the developer to answer. Still a terrible design on Android. Good to know about that app though. That does make it easier than my previous method, for some emulators at least.

This is an Android problem. It's not easy to get this information at all, which is why we're manually entering in so many emulators. This isn't a solvable issue, because of Android's poor design. Often times the only way to get this information is to ask the developer or look at the code. The rest of the suggestions are planned.

Yes, it's configurable.

Thanks @Akean. It turns out that device is a lot older than I thought, so it probably is running that ancient version of Android. I will admit that getting LaunchBox to run on that device will be difficult and might not happen, because it's so old and the hardware specs are so low. I have it on the list though.

Thanks, this is planned.

It creates a LaunchBox folder either in the root of the SD card (priority), or in the root of the internal storage.

Thanks, I will look into adding those emulators here soon.

You might still just need to uncheck the box that asks whether you're importing a full set.