![]() I need to settle on how to statically name the games and in turn the media and obviously the database entries. ![]() I do have a dedicated thread for the Amiga here. We still have the problem that the Hyperspin Amiga database and media naming is out of whack to the latest Retroplay WHDLoad set. lha files etc. you don't really need uae & hdf files now from what I've seen with my limited testing. Ps, I don't suppose you have the settings for Citra for 3DS now it's on Google Play ?įYI Amiga roms are strictly speaking BIOS (kickstart) files but I know what you meant. I will try this out over the next few days and report back. Retroarch provide a Retroarch_ra32.apk which is a dedicated 32bit version we can sideload/install and use, however Hyperspin is NOT setup to use this version as some of the paths changed. In a nutshell currently we have access to more cores for us to play our retro systems on the 32 bit version. This has proved to be a bit of an issue for those of us who love Retroarch as there are some serious differences between the 32bit and 64bit versions. Right guys as some of you are aware Google changed how things work on the Google Play Store a while back, when we install an app it will use the 32 or 64 bit version depending on what's native to the device. As we're mainly focused on the Shield TV here on the Android part of the forum, it is a 64 bit device. RetroArch_ra32 (1.9.0) newest stable version at time of posting ( ) Mega Link for Hyperspin_0.1.8_Hono.apk ( ) Let me know how it works for you, I'll do a Youtube video to help those less experienced with setting up Hyperspin when I know it's working 100% and I have the free time. Those who use adopted storage it's wise to move the Retroarch_ra32 app to internal storage after installing AND before running it for the first time. Use the Search and replace feature to find com.retroarch/ and replace to 32/ do this for all opened files then save all. ini files need to be adjusted to use RA32.Įxe=com.retroarch/.RetroActivityFutureĮxe=32/.RetroActivityFuture Feel free to download it and test yourselves, obviously backup your essential files AND do remember the. I've done some limited testing with RA_32 (1.8.7) and it seems a okay to me (even the Daphne test core works) however I don't use screen overlays or really bother with alternate config setups (in truth I've not used the STV in many months!). So.I decompiled the Hyperspin.apk and made the necessary changes (yes including the config path) to solely use RA_32. ![]() RetroArch provide a RetroArch_ra32.apk which is a dedicated 32bit version we can sideload/install and use, however Hyperspin is NOT setup to use this version as some of the paths changed. Alternatively you can right click a game and go to edit then the emulation tab and check the box for command line and add the command for loading another core there and it will work for just that game.Right guys as some of you are aware Google changed how things work on the Google Play Store a while back, when we install an app it will use the 32 or 64 bit version depending on what's native to the device. As we're mainly focused on the Shield TV here on the Android part of the forum, it is a 64 bit device. You can simply go to Tools/Manage Emulators double click Retroarch and go to the associated platform tab, scroll to the bottom and just add another entry with the same system name but with the different core set, then you can right click a game go to launch with/retroarch/name of core. Under NES launch Castlevania with the Nestopia core and Launch Castlevania 2 with the Snes9x core. My question, is there a way to set different Retroarch cores for the same console in Launchbox (without adding another Retroarch as a separate emulator)? Hello everyone! This is my first time posting here so if I asked this in the wrong place please feel free to let me know (Also if you can post a link to the rule page that would be awesome.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |