Jason Carr

I just submitted version 0.19 with the following: Fixed a regression where controllers were again not working properly in all cases after returning from games Added support for Dolphin emulator Added support for DamonPS2 and DamonPS2 Pro emulators Added support for fMSX and fMSX Deluxe emulators Added support for Redream emulator Unfortunately I have not tested DamonPS2, DamonPS2 Pro, fMSX, fMSX Deluxe, or Redream, as I do not have readily available ROMs currently for those platforms. I would very much appreciate if someone could test launching those emulators once version 0.19 goes live.

Thank you @Cauptain and @Kondorito; I have those translations updated for the next beta. I'm not sure if there will be another beta for the desktop, but there will be another beta for Android at least. Good find @Kondorito on that beta mention. It would indeed be best if the paragraph mentioning the betas was removed from the translations. So here is the text that we would ideally translate, instead of what's in there: It's not a huge deal if this doesn't get changed, but it would be a good thing to get right.

Thanks for these requests; I'll do my best to get them added in today. Nope, just what I noted above. Unfortunately no. I do need to make it a priority to allow editing and importing games directly on the device though, because that has been a very common request and it will open it up to a lot more people.

We'll get that in there eventually, yes. Probably not before the 1.0 release though, honestly. Bah, sorry for this regression. I'll get it fixed and get a new beta out today. Yeah, I'm sure I can fix that here soon. It's not exactly a priority, but it does bug me too.

If you have several instances of LaunchBox running on the same computer, and one works but two do not, the first question to ask is if they are all the same version of LaunchBox. If not, it would probably be best to upgrade them to match. If that's not the issue, I would think that it has to be one of these potential issues: File permissions issue Corrupt data (XML files) Corrupt media (shouldn't cause LaunchBox to not start, but I suppose it's possible) File system corruption Software interference (most likely crappy anti-virus if it's working in one folder but not another)

Thanks for finding that @dragon57. It pointed me to the right area of the Dolphin source code, and it was obvious what I needed to do from there. Dolphin is working for the next beta release.

I'm happy to offer you a refund @uhhhhhhhhhhhhhhhhhwyanwunt. That was interesting to type. For what it's worth, this is not an issue that I've ever heard anyone else experience. The closest thing I've seen was an issue with Google Drive not syncing properly and causing issues. Do you use Google Drive by chance? Or another file syncing service? Other than that, I have no idea why you're experiencing these weird issues out of nowhere. Please email us at support@unbrokensoftware.com though with the same email that your license uses and we'll get you a refund.

The 0.18 update just now finally went live on the Play Store.

Wow, it's not 100% clear, but that definitely helps. I'll give it another shot here. I thought I remembered something like that. If I recall correctly, that is the recommended solution, so I'll probably just add that automatically to the exports. Thanks @dragon57.

Good to know, thanks. Unfortunately that doesn't help me to figure out what parameters are needed to launch Dolphin properly, but at least I know it's possible now. I've scoured the web but I haven't found any good details on how to launch Dolphin into a game, so if anyone has any good info on that, let me know. Otherwise, I'll experiment with it again here soon. I might have to dive into the Dolphin code to figure it out if nothing else pops up.

It's about that time again guys; I'm hoping to put out the 10.0 official release early next week on Monday or Tuesday. I've managed to get the new Android app working with our existing translation system as well, so all the Android translations are also included in the Strings.resx file. There's not a whole lot of things to translate at current for the Android app, so it shouldn't add much extra work. Thanks as always. @Opak @dukeemu @cyanjiang @Bardock @MajKSA @gamehacker @Cauptain @Kondorito @Nyny77 @alexposad @k_kutsugi

Thank you @alexposad. I have all the translation updates into beta 4 which I just put out.

Also, FYI, I attempted to add support for Dolphin, but as far as my research could find, it looks like Dolphin is not currently working to launch directly into games. Either that, or I'm just missing the secret and I can't find it. If anyone is aware of another frontend for Android that is successfully launching Dolphin directly into games, please let me know.

I just submitted version 0.18 to the Play Store with the following: New boxes view overhaul with support for background fanart images New launching view overhaul, also with support for background fanart images Added Yaba Sanshiro and Yaba Sanshiro Pro emulators for Sega Saturn In order to make the best use of the new background fanart images, you'll need to download the new beta 4 release of the desktop app, and re-export everything, as backgrounds were not included in the previous versions of the Android export process. I'm looking to put out the official releases early next week, so I'm hoping this beta will fare well.

Yeah, I can see that being helpful. I'll be putting the release notes in the app here at some point. As it stands, for the beta releases, I always have to limit the amount of busy-work I put in as it distracts from development.

Beta 4 (of the desktop app) is out now with the following: The Android exporter now allows you to choose what types of media you want to export The Android exporter now does a better job of prioritizing the correct images to use, such as using proper Box Front images if they are available instead of another category (like advertisement flyers) The Android exporter now allows exporting background images for use in the newest beta of the Android app (out later today) The Android exporter now has minimal support for bin/cue files, but only if they are named the same (such as Mario.bin and Mario.cue) The Android exporter is now much more stable, and truncates file names if file paths are too long Fixed a glitch with attract mode in Big Box where in some cases the speed was unlimited and not obeying the attract mode settings The associated Android release will be out in a bit with background images for the boxes view. I am hoping to put out the 10.0 official release early next week, along with the 1.0 official release of the Android app.

No, emulator associations do not automatically migrate over. That would be too messy. Not all Retroarch cores that run on Windows work on Android. Nor do all emulators.

Oic; that list includes not only the default platform names, but also any custom platform names that you already have in your collection. So it isn't there the first time; you would have to manually add it. Then subsequent times it's there whether it's a default platform name or not.

No, the desktop themes will not be fully compatible with upcoming Android themes. Unfortunately that's impossible. I will be looking to build themes that are very similar, but each theme will require at least some manual conversion.

I suppose that could have been the case a long time ago, but I just checked the platforms list in the importer and Super Famicom is not listed there as best I can tell. Where were you seeing it?

Oic, I think I understand now. The LaunchBox Games Database sees Super Famicom and Super Nintendo as the same platform (as it should). Basically, Android currently requires the platform names to match the games database exactly. But the exporter should name the platforms to match the games database if Scrape As is set correctly for the platform in LaunchBox for Windows.

Can you explain? Why isn't Retroarch an option for SNES? Is the issue specific to Super Famicom?

I'll see if I can get that added in today. There should be no problem with exporting one platform at a time like that. The only thing to note is that you have to export entire platforms. If you try and export only part of a platform, it will overwrite any games that you already had for that platform on Android.

I'll see if I can get that added in today. There should be no problem with exporting one platform at a time like that. The only thing to note is that you have to export entire platforms. If you try and export only part of a platform, it will overwrite any games that you already had for that platform on Android.

Currently the only way to remove a platform is to delete the platform's XML file under /Android/data/com.unbrokensoftware.launchbox/files/LaunchBox/Data/Platforms. You'll probably also want to delete the image and game folders as well for that platform.