Jason Carr

Yeah, just to confirm, if you export Arcade/MAME from the desktop, it will always export the full ROM set. This is because MAME ROM sets are not always merged (most of them out there aren't), which means that picking and choosing ROMs won't work. I'll put an item on the list to allow for that though.

If we ever end up back on Google Play it will be the free version only. We're not interested in doing anything paid on Google Play anymore (and I'm hesitant to even put the free version up there). We just did not have a good experience on Google Play, and I'm not convinced that we need it. It really does make everything much more annoying and makes it so much harder to get stuff done. Anyways, sorry for the bad news on that. We currently don't have any plans to combine discounts, but it is something that we can consider for the future.

Yes, we'll definitely be adding the option here soon to specify a different emulator on a game-by-game basis. Yes, this is planned as well. We'll be adding the ability to customize metadata and media here soon.

This issue is very system specific and a little hard to get right sometimes. If you wait long enough, the video should always play, but getting the priorities perfect can be difficult. I assume it does play eventually if you just wait a bit?

I have not tried with the portable, but we did just fix a number of issues with the Shield in a new release on Friday. So make sure you're installing the latest version, version 0.37. If not, you can go download the updated version via the website. If you would let me know if that fixes it, I'd appreciate it. It doesn't sound like Android 5.1 is really the right version of Android though (I believe that was before Android TV even came out).

Just confirmed that it's there just fine. Are you using a translated version of LaunchBox? Maybe there's an issue with a translation.

Thanks @mordroc; I will investigate this on Monday and see if I can replicate.

This is a known issue. We'll be fixing it soon.

You probably mistakenly still have a pirated license in your LaunchBox folder. It's called License.xml. You can just delete it.

This was actually fixed in the 0.37 release which has been out since yesterday. But if you imported before then, it's probably best to delete the platform and the images and reimport if you want to fix that issue.

Yup.

I would recommend the MAME arcade core in Retroarch. It's basically up to date MAME. I generally don't like any of the other options because they use really out of date versions of MAME and thus really out of date ROM sets.

Not currently, but that is on my list. See this thread: Good to hear.

Did you check the box to use MAME metadata for these?

Thanks, will review this.

Version 0.37 is out now with the following: Improved region prioritization for image downloads, which should help the images that are downloaded to better match the region of the game and/or the prioritized region Added 23 missing platform banners for some of the more obscure platforms; thanks to Faeran and other members of the community for their work on the images Added support for ClassicBoy Gold and Dolphin MMJR Added support for Duckstation, Citra, and Citra MMJ (though unfortunately all of these emulators are broken and will not actually launch games from a frontend; we can only launch the emulator itself) Added support for Mupen64Plus FZ and Mupen64Plus FZ Pro (though they also appear to be broken on some devices; games will launch fine on an Nvidia Shield TV, but they fail to launch with a "Failed to open ROM file for reading" error on some other devices) Added support for Nintendo Game Boy and Nintendo Game Boy Color to the Retroarch mGBA core Added problematic emulator warnings on some emulators to help notify users of broken emulators

Hi @redboyke, I wish I had a good, concrete solution for this, but for whatever reason that device is just not allowing us to write to the SD card. Storage permissions on Android are a complete mess, because Google is switching everything over to a new storage security model, but it's a complete wreck because it's a very poorly designed solution on Google's part. Unfortunately, the new storage security model completely breaks all emulation frontends on Android and pretty much makes them impossible. The good news though is that in most cases, the old storage security model still works. Unfortunately, though, for whatever reason that device is still restricting write access to the SD card. I don't have that device available to play with, so I'm not sure if there's a setting to change for that or not. If we switched to the new security model, it would not likely be an issue, but it would also break launching games completely, so we can't do that either. Just to explain this dilemma further, we *can* write to the /Android/data/com.unbrokensoftware.launchbox folder on the SD card. But if we do anything with that folder, then none of the emulators will be able to access any files in that folder, which of course causes other issues. It's really a mess, and unfortunately there's nothing we can do about it. So, anyways, unless you can find a setting to change on your tablet, unfortunately the best thing you can do right now is to just leave the LaunchBox folder on internal storage (hopefully it's not too big with just some media) and keep your ROMs on your SD card. You could try putting the LaunchBox folder inside of /Android/data/com.unbrokensoftware.launchbox/files. That might work to keep it on the SD card, but I believe it will break the zip file extraction features, because games won't be able to launch from the temporary folder. Might be worth a shot though. Sorry for the book.

That would be new to me as well, unfortunately. I can confirm that you'll probably need to use an external app to do it, though.

Just tested this and I was able to load up that page just fine, but it does flash white while the page loads. So all I can figure is that this was some kind of connection issue. Have you tried again to see if it happens every time?

Alright, so I tested everything again and I still can't get it working on my Samsung Galaxy S10+. M64 Plus FZ just always gives me a "Failed to open ROM file for reading." error. However, it does work on my Nvidia Shield. So the emulator appears to be broken, but only on some devices. Anyways, I'm adding it in for the next release, just with a warning that it might not work.

We're actually pushing this fix out to an 11.18 beta, because we don't want to risk breaking the 11.17 release that we just put out. But a fix for this will be in the first 11.18 beta, hopefully out next week.

So I think you mean deleting the games on your Android device. MAME is very complicated, and unless you really know what you're doing, you generally can't and shouldn't use a partial MAME set that doesn't include the full set of games. That said, there is an option with the MAME importer to specify that you're not importing a full set.

Hi @J2chulo, are you looking to remove all games on Android? Or the desktop?

A fix for this is coming in the next release.

I'll see if I can get it working. We're getting a lot of reports to add those emulators, so I've got a new plan. I'm going to go ahead and add them, but put a big red note on them that says what the issues are. Then at least everyone knows that it's not the fault of LaunchBox.