Jason Carr

@Bawnanable That's interesting; I've actually never seen that before. What device are you using? Does it happen with every theme/view?

@SegaDreamer I recently imported SMS and all seemed to work well for me, so I'm not sure what the issue might be. Is it a No-Intro ROM set?

Are you getting any errors? How are you trying to download the videos? I don't have that specific device to test with, so I don't know exactly what might be happening here.

It doesn't matter which frontend; Dig would work. I'm only asking to prove whether or not it's even possible to launch those games from a frontend at all, because that helps to eliminate where the problem is.

Not currently. We can force the app to be fullscreen, but stupid Android throws hissy fits whenever a popup window comes up, and then it jumps back and forth between fullscreen and not fullscreen, which is jarring and ugly. So in order to properly make the app fullscreen, we would have to forgo using Android's popups and build/draw our own completely from scratch. So that's a long ways off if we're going to tackle it.

Hmm, good to know. This is likely because there's just no images on the games database for that platform. You might be able to edit the platform and tell it to Scrape As Arcade. Does that work?

Yes, and these are bugs with the emulators themselves, for the ones that have that issue. I don't think just starting the emulator only would be a better solution than what we have right now, but perhaps in the future I could add an option for that somewhere.

Please confirm whether or not you're able to do this with any other frontends. I don't currently have a CPS3 set so that would be extensive to get up and running, and whatever the issue is isn't likely to be LaunchBox's fault anyways.

Thank you much! I will look into that. Okay, good to know. Will review.

Sorry for the late reply. I'll need more information as far as what's going on here in order to help though. I'll need the exact error message and the exact steps you're taking. Thanks! We can probably add that option at a later date.

Beta 4 is out now with the following: Improvement: Added a warning to the MAME Fullset Import Wizard when the user points to a directory that doesn't contain enough files for a fullset Improvement: The Region field in the on the fly filter has been reworked to make it easier to use with games that have multiple regions Improvement: LaunchBox and Big Box now support up to 32 controller buttons instead of just 16 Improvement: A new Problematic Controller Compatibility option has been added to Big Box that improves compatibility with non-gamepad controllers such as racing wheels; this option disables binding axes (axises) that are often completely thrown off by pedals and wheels Fixed: FlowImage now works properly in LaunchBox (for theme devs) Fixed: Rare errors related to missing data when using the Manage Platforms or Manage Emulators window Fixed: Some built-in platform clear logos weren't generating correctly (introduced in 12.15 beta 2) Fixed: The fallback image in some LaunchBox themes weren't loading in immediately Fixed: Pressing the Show Pause Menu button while not in a game would mute computer audio in some circumstances Fixed: LEDBlinky now updates correctly when moving through a platform's recent or favorite games in Big Box platform views

This was indeed fixed in version 1.5. But make sure you're running the latest version of the .emu emulators from the Play Store.

LaunchBox for Android 1.6-beta-1 is out now with the following: Platforms are now automatically sorted by manufacturer, console type, and release date by automatically populating the platform Sort Title fields Platform metadata can now be edited by choosing Edit Metadata from the platform details menu (including the Sort Title to re-arrange)

Yes, sadly, playing Windows games on your Android device is unavailable for the moment (and probably won't be available for the foreseeable future), because of a lack of Windows emulators. Really old Windows games can sometimes run in certain versions of DOSBox, but it's not exactly a smooth experience, and I doubt that any of those listed games would run.

Yup.

MAME is complicated; depending on your MAME set, you can't just pick and choose which MAME games to copy over. Unfortunately the entire set is often required. Since we don't know what type of set you have, we don't just copy those games only for MAME.

We just put out the official 1.5 release, so hopefully all of the above issues are actually solved. Let me know if anyone runs into any additional issues.

@Vader The issue was just that we weren't previously showing the additional versions options unless there were more than one additional version. I've changed that up though to show it even with one, so long as it's different from the main ROM path.

I was able to replicate the same issues with the 1.4 official release of LaunchBox, so it definitely wasn't a new issue, unless it had to do with an update to the emulators. Regardless, it should be fixed for all the .emu emulators (if any of the other ones have the same issue). Master Gear is working fine for us in our testing, but we're testing on Android 12. There may be issues with the emulator on previous versions of Android, or with previous versions of the emulator.

@rpc9943 I was finally able to replicate this; it's more of a bug with NES.emu, but I found a workaround. So I have that fixed for the next release.

Hey all, LaunchBox for Android 1.5-beta-3 is out now with support for Game & Watch. Any testing you guys can do to confirm that everything is working would be appreciated. @Jmnice @SegaDreamer

@Vader Can you confirm that this new beta fixes the issues with additional versions for you?

LaunchBox for Android 1.5-beta-3 is out now with the following: Fixed an issue with replacing images for Android games Fixed an issue with adding additional versions Fixed issues launching games on Android 11+ with the 2600.emu, ColEm, ColEm+, GBA.emu, GBC.emu, iNES, MasterGear, MD.emu, NES.emu, and PCE.emu emulators Added support for Nintendo Game & Watch via the RetroArch GW core

Do you mean reloads immediately from LaunchBox? Is it NES.emu that is reloading immediately, or LaunchBox? I don't think it's really possible that LaunchBox could be causing an emulator to load repeatedly, so it's probably something else going on with the device. To be honest, it sounds like some odd things are going on with the device. Both of these things are issues that I've never seen before anywhere, which tends to be a sign of faulty hardware or misconfiguration somehow. Though it's hard to say without seeing it all firsthand. Is your device an Odin Pro? Or the non-pro? I ask because @C-Beats does have an Odin Pro and things are working great on it.

This is on my list to add, but probably won't make it into the next release. Thanks, I was able to fix this for the next release. This is puzzling to me; I'm unable to replicate any loop behavior like you're describing. Can you explain this in more detail? That said, I did just fix launching games with NES.emu on Android 11+. By the way, for what it's worth, I would highly recommend using a sideloaded version of RetroArch for everything instead of these individual emulators. It tends to work better, is free, and will save you from a bunch of these issues.