(We stress that these should be copies of games you already own.) Sega Saturn – Yabause (very strenuous performance-wise)Īfter you have your cores all set up, to get Retroarch to detect your games, you’ll need to get the ROMs and ISOs for your games onto your Android device.Sega Genesis/Game Gear – Genesis Plus GX (PicoDrive from Sega 32X games).They should work fine on relatively recent devices, but older/low-end Android devices may struggle. Note: cores for more demanding consoles with 3D graphics and so on (N64, PS1, Sega Saturn) will be more straining on your device. There will be certain games that don’t quite conform to this list, but for most people, we believe that it’s optimal. Which cores are best for which console? Below are our core picks for the most popular consoles, based on the broadest compatibility and best performance with the most games. (The only way to then uninstall a core is to go to the Retroarch app settings and “Clear Data.”) (For real, I have an old LG Optimus that runs Android 3.Note that as soon as you tap a core in the list, it will download to your device. You are much better off emulating on any other handheld, including any Android device. Not all games are going to play (Final Fantasy games are especially horrible), and those that do are going to suffer badly. (Meaning MD5/SHA1 hashes match the official!!!) Other than that, there isn't much else you can do. Use a clean BIOS file (preferably SCPH-1001!) you know is good. In all cases, audio must be disabled in RA settings for any game to load properly. I've gotten a lot of games to play fine (~50-60 fps), and a lot more to play tolerably (~30-45 FPS). (And they may have in their latest updates, I'm not sure.)įor what it's worth: My experience with PCSX-ReARMed for 3DS has been pretty extensive. Of course, the safest option is probably to wait until Retroarch fixes the issue. Keep in mind that Luma3DS does not support A9LH anymore and you will no longer receive support or updates for Luma3DS. Any games/updates/saves will need to backed up and restored afterwords. I have done this and confirmed with astronautlevel that it works fine. If you have a NAND backup from this setup, you can use GodMode9 to restore that NAND successfully to remove B9S, restore A9LH, and restore Luma3DS 7.1. If you MUST use Retroarch, my suggestion is to continue to use A9LH+Luma3DS 7.1. Luma's newest builds got a little more strict on the way it handles crashes (because the CFW devs are depending on people to fix this in their homebrew, where it needs to be fixed), so the issue hasn't been present until Luma3DS build version 8 and beyond. Since the issue has been present basically forever, I'm not holding my breath. Nothing you can do but nag the RA guys to fix it. So, load Retroarch, load core, load content, play for a bit, tap bottom screen, select "Exit Retroarch", CRASH! Everytime. If by chance it does load the content and you get to play, it is GOING to crash on Retroarch exit. You've got a 50/50 chance of actually playing the game and not seeing it crash. Basically do this: Load Retroarch, load any core, load any game for that core. It's gotten to the point that I prefer the standalone SNES9x and VirtuaNES by bubble2k (god I wish he'd write a Genesis emulator too!) over Retroarch because of a consistent easy to replicate crashes. Since Luma was updated last (Luma3DS version 8.1.1), Retroarch and NTR CFW are the only homebrew apps still crashing for me. It always crashes for me, regardless of the core I load. Retroarch has a known issue with Luma and the way Luma handles crashes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |