ChaosDrop Posted July 1, 2022 Share Posted July 1, 2022 (edited) I can't get Launchbox android and NES.EMU to play nice on my ANBERNIC RG353P [Android 11] They both seem to use different folder selection systems which leads to Launchbox trying to lunch the roms from a path that NES.EMU doesn't have permission to use despite them pointing to the same folder. Edited July 1, 2022 by ChaosDrop Quote Link to comment Share on other sites More sharing options...
ChaosDrop Posted July 1, 2022 Author Share Posted July 1, 2022 Seems this is an issue with all of the explusalpha / Robert Broglia .emu emulators.. I tried grabbing fresh nightly copies off the repo https://github.com/Rakashazi/emu-ex-plus-alpha/actions/runs/2514860625 And tried moving the roms from the SD card to the internal storage and neither worked. Quote Link to comment Share on other sites More sharing options...
Clab4293 Posted July 13, 2022 Share Posted July 13, 2022 Every emulator (Nintendo handheld and NES/SNES) that is listed that is not a retroarch core doesn't seem to work with Launchbox. Quote Link to comment Share on other sites More sharing options...
ChaosDrop Posted July 14, 2022 Author Share Posted July 14, 2022 I don't have the handheld anymore since I already handed it off to my nephew, but I got SNES working with LaunchBox using SNEs9x... not entirely sure what version though, and can't check now since I don't have it... For GB/NES I couldn't ever find any good free/cheap non-retroarch options and retroarch was way to hard to read and fiddle with on a 3" screen for me to give it to a youngster, so I just didn't set LaunchBox up for them and just left them as NES.EMU...etc. Quote Link to comment Share on other sites More sharing options...
ChaosDrop Posted September 1, 2022 Author Share Posted September 1, 2022 Any news updates on this in the new 1.5 version that I got an email about today? Trying to figure out if it's worth trying to get the console back from my nephew to upgrade it and get NES games on it proper or just leave it well enough alone. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted September 1, 2022 Share Posted September 1, 2022 Unsure what your issue was previously but 1.5 does have some logic in it to help with .EMU emulators. I believe most of them were related to weird interaction issues they had with LaunchBox when closing the emulator. Really though I'd just bite the bullet and set up RetroArch for basically any system it emulates as it just does it better. Quote Link to comment Share on other sites More sharing options...
ChaosDrop Posted September 1, 2022 Author Share Posted September 1, 2022 File system issues Launchbox and .EMU emulators aren't compatible on Android 11+ because they didn't provide the same file access / file path compatibility so lunchbox would fail to lunch the roms. I tried RetroArch, but on tiny screens and low resource system it was substantially worse overall than the .EMU emulators and wasn't worth the trade offs to keep everything in LuanchBox by using it. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted September 2, 2022 Share Posted September 2, 2022 On 9/1/2022 at 8:53 AM, ChaosDrop said: File system issues Launchbox and .EMU emulators aren't compatible on Android 11+ because they didn't provide the same file access / file path compatibility so lunchbox would fail to lunch the roms. I tried RetroArch, but on tiny screens and low resource system it was substantially worse overall than the .EMU emulators and wasn't worth the trade offs to keep everything in LuanchBox by using it. 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. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.