Jason Carr

Hey all, we are hiring for two important new positions here at LaunchBox/Unbroken Software. Both positions will be focused on LaunchBox: Web Development Analyst Experience with ASP.NET, C#, SQL, JavaScript, HTML, and CSS is a must Experience with .NET 6.0, ASP.NET MVC, SQL Server, and/or web server management is a plus Experience with other web technologies is a plus Android Development Engineer Experience with C# and Visual Studio is a must Experience with Xamarin and/or other mobile development technologies is a plus Experience with Linux development is a plus Both positions are work-from-home, full-time, salaried positions with a starting salary of $80,000-$120,000 per year. We are ready to hit the ground running with continued improvements to our existing projects and several new projects as well. If interested and qualified, please reach out to support@unbrokensoftware.com with your resume. Feel free to comment below as well, if desired. We look forward to hearing from you!

Thank you guys; sorry for the late reply. I've had to focus on other things recently. I should be able to come back to those few one-off errored records here soon.

@Benjc Assuming it's a certain platform that is affected (or I guess everything for that matter), you can just delete the media folders for that platform (or all of them). Just make sure you do it while LaunchBox is closed. For example, delete the LaunchBox\Images\Nintendo 64 folder. This will remove all images for Nintendo 64. You can also delete the image cache as well by deleting the LaunchBox\Images\Cache-LB folder. You'll need to either do that, or refresh images in the app.

Honestly I have no idea. We did the best we could to get it running back then, and we kept it up and running for a few versions, but we haven't tried since. You're welcome to give it a shot. Unfortunately it didn't get anywhere near enough of a response from the community to merit us investing lots of time into it.

Yes, unfortunately currently entire platforms have to be exported at a time. So if you add any games to a platform, you will need to re-export the entire platform in order to get the games onto your Android device using the exporter. There are other manual options that don't involve the exporter, but the exporter currently requires entire platforms to be exported.

This thread has lots of details and back and forth on running LaunchBox and Big Box on Linux using Proton, yes: However, it's quite the convoluted mess to get going, and it seems to go back and forth on whether it will work new versions that we put out.

@DrTy_Wizard I looked into Flycast. I was surprised to find that we had never added it into the app. I tried adding it, but it looks like it only allows us to launch the app, and not to launch the a game, at least on Android 13. It just seems to be ignoring the game path that we're sending. Let me know if you have any more information. Did you previously have Flycast working? Or were you referring to the RetroArch core?

Check the beta thread here: Dolphin has been fixed (kind of) for the next beta. I'll have to review Flycast yet though.

I'll add that to my list to investigate. I'll have to do some research on it though.

Oh, I forgot about that one. I've never used it myself. I get the impression it's really old and outdated.

You mean connecting up the hard drive to your phone? That may or may not work, and if it doesn't work, it would be the fault of Samsung for not implementing that functionality properly. From what I've seen, unfortunately it's a crapshoot whether external hard drives work properly on mobile phone devices, depending on the firmware of the device.

Those are the only two options, and DamonPS2 never worked properly with frontends. There are no other options for PS2.

Apologies, the previous issue with changes stuck in limbo was unfortunately reintroduced because a stored procedure got reverted (it was my mistake). Apologies for that (again). That has been fixed.

FYI all, the previous issue with changes stuck in limbo was unfortunately reintroduced because a stored procedure got reverted (it was my mistake). Apologies for that (again). That has been fixed.

Yeah, you will likely need an older version. If you do some Googling online it should point you in the right direction.

@Bugleboyjeans Your testing results here are very similar to ours, unfortunately. Assuming you've seen the beta thread, we put in a lot of effort to fix the launching of as many emulators as we could. Unfortunately there are still some that the emulator developers need to modify to support Android 13 before anything can be done on our end to launch them.

Thanks guys, will review on Monday.

That would be long gone at this point, because that was years ago, unfortunately. I'll definitely have to revisit.

Unfortunately you would have to ask the emulator developers, as we don't have direct relationships with any of them, really.

I'm guessing that mame4all must have changed its launching settings here at some point. I'll have to play with it and see if I can get it to launch. It might be a while though on that.

Hi @Zman, make sure you're using the sideloaded RetroArch APK, and not the version from the Play Store. Google has unfortunately crippled that version. So download the APK directly from the RetroArch website. Then download the official MAME core from inside of RetroArch (the one without dates on it). Select that core in LaunchBox, and make sure you're using a recent MAME ROM set, and you should be up and running.

Nice, yeah, that should work well. Great to hear.

That wouldn't actually be any different from moving the LaunchBox folder as it is right now, because the "LaunchBox folder" doesn't actually contain the app itself. Only the data and media.

I wouldn't personally recommend mame4droid, because last I checked it required an extremely out of date and specific MAME set. So that's probably your issue.

@MDGeist Just tested adding some videos to Android games, and everything worked as expected for me, but I was also testing with known-good video formats. My best guess is that maybe the video format being used might not work? We use VLC for video playback though, which should support most everything, so I'm not exactly sure what's happening there. But unfortunately I can't replicate any issues.