Jason Carr

This is a good point. I kind of wish we could just remove adult games from the database completely, but I know that's probably too much to ask. I agree that we should at least have a flag of some kind. On my list. It's worth noting, however, that images like that are not allowed in the database, and should never have been approved.

Hi Dragoon, LaunchBox considers Nintendo Famicom to be the same platform as Nintendo Entertainment System in the database. If you go to Tools > Manage Platforms in LaunchBox on the desktop, you can edit Nintendo Famicom. Then select Nintendo Entertainment System in the Scape As field for that platform, and it should then work properly in the exporter.

Just uploaded version 0.27 to the Play Store, so it should be available soon. I'm hoping this release fixes the app killing issues I described above for at least some people, but I'm fairly certain it won't fix it for everyone. Still, if you were experiencing issues with the new import process closing to the desktop, please give the new version a test and let me know how it goes. I did some brainstorming with @CBeatt13 (C-Beats as he apparently likes to go by these days), and we came up with some more optimization I can do to try and prevent the app kills further, but that will take quite a bit more development effort, so I'm hoping that these quick fixes at least help in the mean time. All in all, I have no idea if we'll ever be able to eliminate the app kills completely, but I'm certainly hoping so.

FYI on this all; I've hit a major roadblock that is fairly disastrous. Android phone manufacturers have a nasty habit of aggressively killing off any apps that use a large amount of resources. This is done to conserve battery, primarily. On my Samsung Galaxy S10+, it's not an issue when I have the phone plugged in, which is why I didn't discover the issue initially. However, the moment I unplug the phone, all of the sudden the import processes are killed regularly. The issues we're seeing in this thread are not because the app is crashing, but rather because Android (more specifically the customized versions of Android installed on mobile devices by certain manufacturers) are killing the app. At this point I don't have a good solution to this problem; I've tried everything from running it all on the main application thread (which destroys performance) to setting a super high thread priority, which seems to do nothing. At this point I'm seriously concerned about the feasibility of Android for the future at all. I also have more sympathy and understanding for some of the common issues that I see with emulators on Android. More information on this issue is available here: https://dontkillmyapp.com/ I plan to do a bit more experimentation to try and come up with some sort of a solution, but the way it's looking right now is not good. This is an issue that many Android app developers are dealing with, and I do not want to deal with the support nightmare that is having to tell everyone to change settings or hack their devices in order to get around this issue. This is all after spending 3 weeks of development time on this import process. The more I deal with stuff like this, the more I appreciate Windows.

It shouldn't, no. But if you want to run a test to make sure by deleting it first, I would appreciate it.

Cool, thanks.

One more question, what platforms did you import? Just in case I'm able to replicate it with certain platforms.

Wow, two of them doing the same thing. The only difference I can envision between your setup and mine would be the Internet connection. Does it always immediately crash when it gets to the downloading stage, or does it randomly get part of the way through it and then crash?

Yes, we'll definitely get a search function in there eventually.

The on-Android importer won't move the ROMs off of your USB stick. It just uses them in whatever location you put them in. If you want to move them from your USB stick to your Android device, first copy the ROMs onto your Android device, and then run the import.

Okay, what type of nVidia Shield do you have? Is it a Shield TV? It shouldn't matter that the ROMs are zipped. Sounds like it's not liking the downloads though for some reason.

The point of this new beta is to allow you to import them directly on your Android device, not have to export them. But that functionality is currently beta, and you do have more options currently on the desktop. This looks to be an Internet connection issue, but I'll confirm and see if there's anything I can do to make that part more resilient. I've done most of my testing on my own nVidia Shield TV, so I'm not sure why you'd be running into that. What screen is it crashing on? What text is displayed on the screen when it crashes? Thanks for all the testing guys.

The good news is we just hired Christian (our new developer). I do have plans to clean some things up with the games database and website here soon. Per #1, I never even thought about parenthesis in titles lol. Is that even a thing? Are there any games that officially have parenthesis in their titles? Per #2, I'm not sure about changing the titles in that case. I know it's a problem, but hopefully they would have different release dates, at least. I believe the MAME importer in LaunchBox does properly differentiate between these games. Let me know if anyone can prove otherwise, and I'll look into it. Per #3, I am in agreement that we need all arcade games under the Arcade platform, because that is what the platform is. However, I don't see anything wrong with duplicating them also in there subcategory "platforms". That way users can choose which approach they want and it should work well for both. I know we're missing a lot of subcategory platforms currently though. Per #4, that would be a massive job, identifying all of them, and we'd end up having arguments about what goes where lol. I do see the benefit of it, but honestly, that one's not likely to happen. Thanks for the feedback though @Jeffe. These are some good points.

And the beta update is live.

Beta 3 is out now guys with the following: New Feature: You can now force update metadata from the LaunchBox Games Database via Help > Force Update Games Database Metadata in LaunchBox Fixed: Removing existing auto-generated playlists was sometimes incorrectly deleting unrelated playlists because of "Nintendo Game Boy" being part of multiple platforms Fixed: Steam metadata imports were causing errors for games without videos (introduced in previous beta) Fixed: Counts were not properly showing in the side bar for the new Games Missing Media section Also, I finally have a new Android beta out with a new import process that runs directly on Android devices (and no longer requires the desktop app):

@wallmachine I've done some testing and haven't been able to replicate any of that. I'm inclined to believe that whatever is causing it is not related to the update, as you suggested. Rolling back to beta 1 should work just fine, so most likely it's not related to the beta release. Does it happen with all themes on your system?

Hey all, I just uploaded a new 0.26 beta to the Play Store with an on-Android import process. Details are here:

Hey all, I just uploaded a new 0.26 beta to the Play Store with an on-Android import process. Details are here:

Hello all, I just uploaded version 0.26 in beta form to the Play Store. Hopefully it will go live quickly here. I've been working on an import process that runs directly on the Android device (instead of requiring an export from the desktop app) for weeks now, and this is the result. I'm releasing this in beta form first, because it's such a big release. The only other new thing with this release is the fact that the app should now work on Intel x86 and x64 devices as well (instead of just arm and arm64). In order to use the betas, you'll need to opt-in to the beta releases here: https://play.google.com/apps/testing/com.unbrokensoftware.launchbox Once you've opted in, you should be able to able to update to the beta version on your Android device. Please keep in mind that if you opt-in to the betas, you won't be able to leave a public review of the app (and we can use them if you're willing). You have to use the same link to opt out of the betas before you'll be able to leave a public review. Any testing you guys can do on the new import process (or anywhere else) would be much appreciated.

Actually, the reason why this is an issue in the first place is in order to allow multiple users to control Big Box at once. The issue is just a side effect of the fact that we don't currently differentiate between different controllers when taking inputs. We have this issue on our list.

Hi @mariano2860, this is a known issue. I assume you're using two different XInput controllers (360 or Xbone or compatible). The controller code currently doesn't differentiate between them in that case, so that is why. It's not a major focus for us, but we do have an item on our list for it.

Hmm, I'm not sure why a playlist would lose those settings; I haven't seen that situation before. I'll keep an eye out though. Thanks @RULLUR. Yeah, this is just Windows. There's unfortunately not anything we can do about it.

Good to hear guys. I'm pretty sure the issue comes from using different DPIs on your various monitors. Windows still does not handle that well without jumping through a bunch of additional hoops.

There should be a new "Games Missing Media" option available in the side bar filter type drop down.

I see. Steam is not known to cause any issues, no, but that is certainly a clue. It may be controller-related somehow. Maybe try disabling controllers in LaunchBox and/or Big Box, and disabling Steam's various controller features as well.