Jump to content
LaunchBox Community Forums

Jason Carr

Administrators
  • Posts

    12,756
  • Joined

  • Last visited

  • Days Won

    362

Everything posted by Jason Carr

  1. I spoke with Tahlreth, the AetherSX2 developer tonight. I was as careful and polite as I could have possibly been, but unfortunately he has no interest in supporting frontends or allowing frontends to launch games in AetherSX2. He ended the conversation with "I might just make the activities private next update", suggesting that he is going to completely disable any chance of frontends launching games at all. So unfortunately that is bad news, but it is his choice if he does not want frontends to be able to launch games in AetherSX2. From what I can tell, his reasoning is that he wants users to use his user interface only, and does not want it to be hidden or bypassed by a frontend. So, for now, we have to give up on supporting AetherSX2.
  2. Huh, that's interesting. I would expect that to be on the emulator developer to fix. Or at least we'd need their input if we do need to change how we launch it.
  3. LaunchBox for Android 1.0-beta-4 is out now with the following: Fix for crashes on startup with Nvidia Shield devices (introduced in a recent beta) Fix for launching games with Snes9x EX+ on Android 11+ Added some additional warnings for emulators that are not always working to launch games on Android 11+ For anyone who had issues with the previous beta and needs to manually update, you can download the APK for beta 4 directly here: https://www.dropbox.com/s/bhutfrdol75gp4l/LaunchBox-Android-1.0-beta-4.apk?dl=0 There are now four emulators that have been updated to work properly with Android 11+: Dolphin Snes9x EX+ Mupen64Plus FZ Mupen64Plus FZ Pro Thankfully, the above emulators do prove that things can work just fine on Android 11+, but it requires that both LaunchBox and the emulator itself are updated properly. The problems come into play when an emulator developer chooses to update to the latest Android API, but does not implement all the necessary features in order to support launching games properly. For example, often times an emulator developer will update the internal code to use the new Android Storage Access Framework, but unless they add additional code to properly launch games from shared content URLs, then launching games will be broken by default. Google is the biggest cause of this problem, because they've made horrible design decisions as to these changes, and the documentation is incredibly confusing. So we can't really blame any emulator developers, but the emulators will need to be updated in order to fix the issue. Here's a list of emulators that we are aware of having known issues launching games on Android 11+: AetherSX2 Citra Citra MMJ Pizza Boy GBA Pro Pizza Boy GBC Pro PPSSPP Redream There's probably more that we haven't run into yet as well. There are known hacks that work to force some of these emulators to launch games on Android 11+, but they are not good solutions, as they provide a bad user experience (such as forcing the user to have to re-select a folder with the Android Storage Access Framework). For example, Arc Browser has a hacky solution right now that uses an external app to handle translation, but it's confusing to set up, and I would much prefer to avoid that kind of a solution. Ideally, we can reach out to the development teams of all of these emulators and work with them to get the issue fixed properly. Soon I'll be doing my best to reach out to them all to start up a conversation. If anyone has any direct contacts, please let me know. In the mean time, do remember that RetroArch works great with most platforms and there are zero issues launching games with it, because they have refrained from targeting the latest Android API (which honestly is just about the wisest thing you can do right now). Thanks for bearing with us on all of this; we'll be working on finishing up the video support and hopefully working with emulator devs to improve compatibility with the above emulators before the official 1.0 release.
  4. Quick update guys, the latest beta does fix the issues launching games with Dolphin and Mupen64Plus FZ. However, AetherSX2, Citra, PPSSPP, and Redream all have issues launching games on Android 11+, and they need updates/fixes from the emulator developers to make them work. More details are here in this post: Also, I have a new beta coming out here shortly to fix some additional issues, so you might want to wait to update until beta 4 comes out in an hour or two.
  5. Just to update this thread for anyone who hasn't been in the loop in the beta testing thread here: We've successfully solved the issues with launching games on Android 11+ with Dolphin and Mupen64Plus FZ, because they've apparently been built correctly for the latest versions of Android. Unfortunately, though, several others have issues with their implementations, including AetherSX2, Citra, PPSSPP, and Redream. These emulators apparently don't yet support the proper content URIs for Android 11+. We're hoping to reach out to all of the development teams here soon. If anyone has a direct contact, please let me know. To clarify, it may be possible to launch games with some of those emulators by popping up file browser dialogs that should really not be necessary, but we're trying to avoid that if possible for the best user experience. Arc Browser uses a hack to make them work that we would like to avoid, though we may end up doing something similar if absolutely necessary. Regardless, we're working hard to get these issues resolved, despite the unfortunate climate that Google has dumped on the emulation community with Android 11+.
  6. Lemuroid is on the list of emulators to add, so hopefully I can get it in soon (assuming that it does actually allow us to launch games).
  7. It's possible that Dolphin is expecting a different way to launch the games if they are compressed. I'm not sure. I'll be putting out a new Android beta later today. Can you test 1.0-beta-4 (after it comes out) to see if it happens to solve the issue?
  8. I've spent some significant time on this stuff, and unfortunately, both PPSSPP and Redream will need updated/fixed in order for us to properly launch games on Android 11+. They don't appear to support the new proper URIs that are required in order for us to send the games over. I'll be doing my best to reach out to the development teams here soon to see if we can coordinate a fix. If anyone has a direct contact, please let me know. That said, you might have some luck by installing older versions of the emulators and then upgrading to the latest versions. This is because of Android's poor design decisions; permissions are different if you upgrade from an older version than if you install the latest version fresh.
  9. Are you referring to the export from the desktop app for the videos? If so, you will need to update to the beta of the desktop app to fix that.
  10. @Buckshot60 @Ally68 Thanks, I have that issue solved for the next beta. Will review those emulators. Yup, should be relatively easy to get it all back with the same process. No idea why your phone would have removed it on an update though; that shouldn't be happening as far as I'm aware.
  11. Yeah, you may want to use a different device, if at all possible. It will automatically place them in internal storage.
  12. I believe folks that don't have the All Games banner showing up are having the issue because they're using a translation. This is an issue that I need to solve, and plan to for the next release. In the mean time, here's the image to download and use manually:
  13. @Neil Aubin @Kuro Houou We've seen this odd issue with some lower-end devices that are just not quite configured correctly. Unfortunately we don't have a solution currently, outside of some strategic file placement. On these older devices, you should be able to place the ROM files on the SD card and import them from there, but the media and XML files unfortunately don't work on the SD card and have to be on internal storage.
  14. Sorry for the way late response here @senkwich. This is a known issue with those really old clamshell Shield devices. I might be able to solve the issue if I had one on hand, but I don't, so solving it has proven difficult. Whatever the issue is seems to be unique to that device.
  15. @rubenjavier Sorry for the way late response. I've noted the request. The code is supposed to pull only the relevant images for the region of the game, but it will use the foreign images if the ROM is marked as from that region. I may need to revisit some of that code though, because I believe I've heard this issue elsewhere recently as well.
  16. @flexzi Unfortunately we haven't tackled DOSBox or ScummVM on Android yet, because there's a lot of complicated stuff involved in the process. We do hopefully plan to tackle them soon, though. As of yet, I'm not sure what all would be required or if it's possible on the current versions of LaunchBox for Android.
  17. I've been disappointed with the Tankstick in the past, just because it's way too limited on buttons. It doesn't have dedicated buttons for anything, really; not even exiting games (or at least it didn't last I checked). I've never used it on Android though, either. Sorry I'm not too much help here.
  18. Yes, we do plan to add support for DOSBox in LaunchBox for Android here soon.
  19. Thank you both. I have both translations updated for the next beta.
  20. @hobapli I don't fully follow what the issue is, or what you're trying to do, unfortunately. However, the latest beta may fix some issues with file storage permissions on Android 11 and 12.
  21. Jason Carr

    Update

    0.42 didn't break anything as far as emulators. However, if your device recently updated to Android 11 or 12, you might be running into issues because Google hates us all (half kidding...?). Anyways, the latest beta does fix issues with some emulators on Android 11 and 12. I'm not sure if you guys are referring to the betas, but the official releases have never been broken, so I'm not fully following what's going on in this thread. We did have an issue on Android 12 with version 1.0-beta-2, however.
  22. It's best to use a modern/recent MAME set, along with RetroArch Plus (from the Play Store), or one of the sideloaded versions of RetroArch. You should use the current MAME core. Last I checked, mame4droid was not recommended because it uses really old sets.
  23. Yes, it did get solved, but it sounds like Google or Nvidia screwed it all up again with the latest releases of Android on the Shield. I'll be reviewing it (again) here soon.
  24. Assuming you were updating to 1.0-beta-2, this has been fixed for 1.0-beta-3. Sorry for the trouble.
×
×
  • Create New...