Jason Carr

Hmm, it looks like perhaps we haven't marked "Neo Geo" as a platform that works with Retroarch. What is your platform name called exactly? Neo Geo is technically Arcade, so there is some confusion there.

If you can help, I need more details on this. If possible, I need the exact error message and I need to know exactly where that error is coming up. On game launch? Or loading the app?

I have not yet tested Neo Geo. Currently, the app does not parse the system to see what all emulators are installed; it just recommends a default based on what we think works the best. That recommendation may not be the best though.

@Skidda420 Come to think of it, your issues could also be caused by missing ROM files, potentially. I need to put a check in to report if the ROM file is missing before launching; I'll do that.

Per #1, what other emulators have you tried? Try uninstalling and reinstalling the latest version of Retroarch to see if that fixes the problem. What version of Android are you running on your device? Per #2, usually this means that the file copy operation did not complete when copying files over to your device. Check the "/Android/data/com.unbrokensoftware.launchbox/files/LaunchBox/Images/Super Nintendo Entertainment System/Box - Front - Thumb" folder to see if the images are missing from that folder. If so, it looks like the copy operation did not complete successfully. That could also be causing issue #1 if ROM files are missing as well.

I believe we do have a problem with PPSSPP, so I'll get that fixed. For Retroarch, though, everything is tested and working fine. I would say uninstall it and reinstall the latest version from the Play Store, and see if that fixes it.

SD cards should be working, and are in my testing. What device are you using? What is happening exactly when you export to the SD card? We're honestly a long ways off from that, but there are existing solutions, such as the Steam Link. I know there are issues with that solution, though; I believe they can be solved but it may be kind of finicky. I can see us doing that eventually, but it's a major challenge and we're not going to be able to focus on something like that for quite a while. Haha, sorry I didn't get it in there quite fast enough. I haven't tested it on Kit Kat because I don't have any Kit Kat devices, so let me know how it works.

Not yet. It's not really possible to do an export from the desktop for MAME, because they require different ROM sets. That said, we do definitely need a way of handling MAME in the Android app.

FYI, 0.13 is live now, but I actually just put out 0.14 lol. Nothing much new in 0.14, except for some slight optimizations that I thought might help.

Version 0.13 is out now with the following: Enabled support for Android 4.4 (Kit Kat), primarily for GPD XD devices More robust error handling/reporting for data loading and launching emulators Updated About screen Nothing all that big for this release, but I'm trying to resolve the one-off crashes that I'm still seeing with certain users/devices on the Play Store. I've also been working on improving the desktop Export to Android wizard, but that's not quite ready for a release yet. That should be out soon though.

Awesome. I only wish that Retroarch would just work to exit with the back button, like most everything else. I'm very confused on this, as I haven't been able to replicate that at all. I just saw your specs though, so I see you're using a Shield TV. I'll give it a shot on my Shield TV to see if I can figure it out.

@PiperCalls I'm not really following all of that, honestly. I'll do some testing today though with the Shield and external drives. Currently, it only works to export from your desktop collection. This will change in the future though.

Any time, though there's certainly plenty to do before we get to the niceties. If you press the Y button on the Shield controller, it should open up that ellipsis menu. I think the update issues are most likely just caused from it being a beta release, so I'm hoping things go more smoothly there once we put out the official. I'm currently in the process of testing all of the emulators. I successfully tested Snes9x EX+ and MD.emu before the 0.12 release though, and they were working fine. Are those not working for you in 0.12? I have yet to test NES.emu.

New update is live now.

I just submitted version 0.12 to the Play Store, and I think the app is finally getting to the point where it should be mostly there. Here are the changes: Added parsing Android games back in, with an option to disable Fixed emulator launching issues for many different emulators New Exit option in the main menu Improved error handling for launching emulators Improved searching and error handling for initializing the root folder Improved error handling for corrupt data Now notifies the user to export via the desktop application if no data is found on startup Please let me know how this version fares, especially for folks that were seeing errors or issues. Also, I don't have any good lists of emulators for Android outside of what we already have, so if anyone knows of any good lists or is missing any of their favorite emulators, please let me know. It would be nice if launching emulators on Android were as simple as launching a command line on Windows, but sadly, it's unnecessarily complicated, so there's not really a good way to easily allow the user to add custom emulators.

Thanks; I will look into adding kat5200. I haven't yet tested the Shield with external drives, so honestly it should work, but I'm not certain if it will at this point. That said, no matter what storage device you put the files on, they should be in that exact same folder. I plan to do some further testing with the Shield and external drives here soon. Please read the first post of this topic.

Gotcha, looking into that. Ah, I see. Yes, the right joystick is used to navigate more quickly through the items in the list. I can probably add an option to disable that though.

Well thanks; it's been a stressful past few days because of the bugs that I didn't predict, but I do find it all very rewarding. I'm happy to have 0.11 out finally. Not currently, at least not that I'm aware of. You might be able to figure out by manually copying files though, not sure. I'll have a fix for that in before the official release though.

FYI, the 0.11 update is live now.

One more thing; we may still run into some weird permissions errors, but at least the app should tell you that now instead of just crashing. Let me know if anyone sees any permissions-related error messages (or any error messages at all for that matter).

I just submitted version 0.11 to the Play Store, and I'm hoping it will resolve the rest of the startup crashes and such. Here's the change log for this version: Fixed crash/white screen on first start after accepting permissions Improved error handling on startup Now searches for only folders with actual content (avoids using an empty folder when exported platforms exist elsewhere) New splash screen That crash on startup was doing me in, so I hope I've finally got it fixed. Turns out it was only happening in my release builds and never in my debugging builds, so no wonder it was so difficult to track down. I know there are still issues launching some emulators; I'll be back to that tomorrow to try and fix those issues. Not sure how long it will take for 0.11 to go live on the Play Store, but hopefully it'll be live soon. Thanks all.

Agreed, I do plan on adding that.

Then I'm not sure what's going on. I'll add that to my list to test N64 with Retroarch. Per the controller, I'm testing with the exact same hardware, so that's baffling. Any chance you have another controller connected? Or maybe a keyboard or any other input devices connected?

I'm not yet clear on using USB drives on the Shield. Android permissions have been an absolute wreck to work with, so I'm not sure how easy that's going to be. Feel free to experiment with it, but I would not expect USB drives on the Shield to work correctly just yet. It was my understanding that Retroarch was changing things up to release both the 32-bit version and the 64-bit version in one app, but I have yet to research all of that. I'll get Retroarch all fixed up here soon though. Good to know about NGP.emu; I'll take a look. Perhaps are your N64 ROMs zipped up?

This is true; it's something I should add. If a ROM is from a Europe, it should use the name from that region. There's a lot of complication in all of that, such as an alternate title being from the UK, for instance, but the ROM being from Europe, but I'll add that to my list here.