Jason Carr

I screwed it up apparently. Sorry for that. Thanks for the note. I've fixed it, so it should be correct in the official release that we plan to put out tomorrow.

Alright, let's stop this discussion @Lordmonkus @C0ntrA. It's not worth it.

@C0ntrA What you do and how you acquire ROMs is one thing, but we won't stand for promoting hard drive sellers on these forums, so please keep that stuff to yourself.

Thanks all! We have these all in for the next beta, which should be out in a bit.

Not to bash @C0ntrA, but please don't do this. It supports hard drive sellers who are literally making a living by stealing other people's work. Most importantly, the games. To be clear, I haven't re-read-up on this thread, but there should be no reason why anyone would need to buy a drive in order to use MAME well on Android. The Retroarch MAME core works really well, and you can use the same modern ROMs that you use on the desktop.

Hey all, we're looking to put out the big 12.0 official release early next week, so now's the time to get the translations updated if you can. Thank you all for all your work! @Kondorito @Cauptain @Nyny77 @Opak @dukeemu @cyanjiang @Just001Kim @MajKSA @gamehacker @alexposad @k_kutsugi @Bardock

The games may be combined into additional apps.

@tiagotachard Unfortunately some devices do not let you change your data folder to the SD card, because they're configured to lock down the permissions, which is extremely irritating, but there's not a whole lot we can do about it. What device are you using? The best solution in this case is to put your ROMs on the SD card, but keep the LaunchBox folder on internal storage.

It should prompt you when you restart the app, but of course you'll need to make sure you have a decent connection. You can use the Android app switcher to swipe up and close the app. Then just restart it, and you should be prompted to update.

There are debug logs under LaunchBox\Logs, but they do need to be enabled in the Options, and they're really only for errors and crashes.

0.42-beta-1 is out now with the following: Games can now be filtered by Platform, Genre, Developer, Publisher, Rating, Play Mode, Region, Series, Status, and/or Source fields The default root filter can now be changed to any of the above filtering options (Options > Default Root Filter) A default secondary filter option has also been added that will allow you to add a second filter to default navigation (Options > Default Secondary Filter); this will allow you to navigate by platform and then by genre, for example Fully dynamic and nested filtering is now available, which means you can filter to anything at any time; long press on a platform or filter and select Filter, or choose Filter from the top menu of any games list An All Games option has been added to all filter views Added the ability to customize all platform/filter media; you can long press on a platform or filter and select Edit Media to change all media items The Android games list will now only show apps that are in the Android Game category; unfortunately though, Android apps are often miscategorized, so it might not be perfect The Arcade platform now supports the RetroArch Flycast core The new dynamic/nested filters system is extremely effective, to the point where I'm wondering if we should actually do something similar on the desktop. Also thanks to @faeran for some beautiful new genre banners: Remember that this is a beta release, so you'll need to check the box in Options to update to beta releases in order to use this version. We're hoping to get help from everyone in this thread to get rid of any bugs and get the official release out next week.

Editing/matching games is coming soon. I'll also add those emulators to the list.

It's not that it would be hard to implement; it's that there's really not a great reason to implement it. Hiding games already allows you to hide platforms just the same...

We're still waiting on details on exactly what is happening, as we've never seen it or been able to replicate it. What video playback engine are you using when you experience the crashing? Does it happen with both video playback engines?

@Joseph B

PCE.emu is already supported. Is it not showing up for you? What platform?

Yeah, I'm really not sure, but I suppose that could be a possibility.

Yes, we will definitely be adding those options in the future.

This will depend on a lot of things; it's a good idea, but I'm not sure what the implementation would require. I'll keep it in mind to see if we can tackle it, but it's probably not going to happen for v1 of the video implementation.

I see, it sounds like we need to allow the Flycast core for Arcade. I'll put that on the list.

That's why you need to open them both up at once, using the same window. That way you'll see the English translation and the Polish translation (empty) on the same line.

Final Burn is a bit of an uncovered part of the LaunchBox implementation. My understanding is that Final Burn ROMs are very similar or the same to the MAME ROMs, but I have never really tried to play with any of it, so I'm not very knowledgeable on the subject. What specific files is the importer not recognizing?

Unless you import MAME ROMs using the full-set importer, LaunchBox will not currently import clones unless the files exist on disk.

You'll need to read the first few posts of this topic in more detail; it sounds like you're not following the steps from the first few posts. You need to open up one set of files at a time. For example, open both the English Strings file and the Polish strings file. I'm not aware of a way to export things to Excel; I haven't really played with it though. Unfortunately in order to check the strings in LaunchBox itself, the only way to do it is for you to give me the translation files, and then I can compile them into a beta release.

I can guarantee that loading the source images without the cache would definitely not be faster and would be more of a performance issue. We always test that stuff before we implement things the way we do. I understand the desire to not write the cache images to disk, however. I think performance for most users would be significantly negatively affected in that case, but I do understand why you would want to do it. If you would, please create a BitBucket ticket for it and we'll see if other users are interested in it as well (Help & Support > Request a Feature in the header of this page).