Jason Carr

In our efforts to make Yaba Sanshiro 2 work, we found that it did not work properly on Android 11 and 12, so we didn't put a whole lot of time into the implementation. I'm not sure if it works on Android 10 and below, but it sounds like perhaps it doesn't work there either. I will review.

This is likely because LaunchBox is creating a temporary m3u playlist file in order to launch games with multiple discs properly in RetroArch. Does this mean that save states aren't working at all?

I think I know why this is, but it might take me a while to resolve, since I have to set up a testing scenario for it.

Yes, but it may not be completely accurate. Emulators update all the time (or don't update when necessary), and especially with Google's terrible design decisions in Android 11 and 12, it's difficult to make sure everything is still working. We highly recommend using RetroArch for most platforms, sans for a small few disc-based platforms like GameCube, Wii, PSP, etc. You're shooting yourself in the foot on Android if you don't use a sideloaded version of 64-bit RetroArch. It's easy to find out which emulators are supported for a specific platform just by importing that platform.

Nice! We have German covered well, but our French translation hasn't been updated since March. So if you wanted to update that, that would be much appreciated. You can check out this thread for details on how it all works:

Thanks Claudio; I have this in for the next beta.

Beta 6 is out now with the following: Behavior has been added to allow for vertically centering the selected item in Big Box themes (for theme developers) The CurrentDateTime binding has been added to Big Box (for theme developers) Other miscellaneous changes to the Default theme Fix for potential compatibility errors with some older themes Please let us know if you guys are still getting the same startup errors in beta 6 @kmoney @bbweiners @Suhrvivor. I'm thinking there may have been an issue with the upload of beta 5, because our testing hasn't run into any of those issues.

Unfortunately I'm not aware of one. Maybe you could run a Windows VM on your Mac?

The Nvidia Shield is what we typically test with for Android TV. NVidia's done a terrible job with firmware lately though, creating all kinds of issues. So I wouldn't necessarily recommend the NVidia Shield. Do let me know what you decide to get though because it would be good to hear how well it works.

Thanks much; I have this translation in for the next beta.

MS-DOS support has just been added to both the Export to Android features of LaunchBox for Windows (latest beta) and the latest beta of LaunchBox for Android. Just FYI, though, it was the opposite of easy. Exporting games from the desktop that are in a completely different format, zipping them up for Android, and maintaining configuration information is a tremendously extensive process.

LaunchBox for Android 1.5-beta-1 is out now with the following: Added support for the MS-DOS platform using the DOSBox RetroArch cores New Swedish translation thanks to gantraz from the LaunchBox Community Forums Fixed an issue where the user could select "Recently Played" as the Default Root Filter in the options, which would cause a crash on startup Please note that MS-DOS only works with zip files right now, which works much better on Android currently anyways, so we would recommend this approach. The latest LaunchBox for Windows beta (12.14-beta-4) has also been updated to be able to export MS-DOS games in zip format for Android (using the Export to Android feature). It will zip up your MS-DOS games so that they can be easily added to the Android app.

We are planning on tackling alpha-numeric navigation here soon. The Last Played section is limited to 100 games. There is a known issue with extracting files that are too large. It is not recommended currently to use compressed disc image files that need extracted on startup. Small ROMs will work fine, but larger ones will not currently.

I am currently running this beta on 7 different machines overnight in order to test for any further memory leaks. We did introduce some memory leaks in the previous betas, which in turn caused some performance issues. None of these memory leaks are in the 12.13 official release, however, and they do appear to be fixed now. Thanks for the reports. Also, this beta contains an update to the Export to Android feature that will allow you to export MS-DOS games (it zips them up for ease of use on Android). A new Android beta will be out shortly to add MS-DOS to the Android app itself.

We should definitely talk. We are still leaning more towards full time, but you've already proven that you're certainly talented. Can you email us at support@unbrokensoftware.com so we can set up a discussion?

Unfortunately for the moment we don't have a good way to add individual games like that (it's been built to emphasize ease of use and mass imports primarily). You can edit individual games, but we need to add an option to add individual games yet.

The high scores unfortunately will never be perfect. There will always be games here and there with issues. This is due to the nature of high scores within MAME, and the fact that the processing to retrieve those high scores is different between each game (and sometimes even between MAME versions). The hi2txt project is what we use in order to read the scores, and @GreatStone (the developer of it) does an amazing job with it. But it will always be a work in progress, because of the nature of the beast. If/when you run across an issue, you can report it here: https://greatstoneex.github.io/hi2txt-doc/ Keep in mind that it will probably be a while though before it can be fixed.

I am skeptical that it would be possible for a specific game in your collection to be working in LaunchBox, but not Big Box. Are you sure you're not using a different version or a different ROM file? The code is the same for this whether you're running LaunchBox or Big Box, so that doesn't really make much sense.

Unfortunately not at this time @squallsoft.

@samchop I've been working on trying to get ClassicBoy Pro and Lite working, but I haven't been having much luck. I haven't found any documentation on how to launch the new versions properly, unfortunately, and everything I've tried has failed. So I'm at a loss for the moment. For the time being, I'm going to remove support for those emulators from LaunchBox. We can add them back in if anyone can clarify how to launch those emulators (or if they get fixed). To be frank, it looks like most of the platforms (if not all of them) are already well-covered by RetroArch, so I would recommend using RetroArch instead anyways. I can see how people might like the ClassicBoy interface better, but if you're using a frontend, that probably doesn't matter much anyways.

Unfortunately I don't have any information on how Dolphin would expect us to launch NKIT ISO files any differently from any other type of file, so there's not really anything I can do there, unless someone has any additional information on it. Most likely it's just a bug with Dolphin, but I don't really know for sure. Also, for what it's worth, that file format is no longer a recommended file format to use, from what I've heard.

Sure, it looks like that issue is fixed when the window is resized to be bigger, so hopefully that will fix the issue.