![]() Mupen64Plus-Next + Parallel RDP runs great. Quite a few cores are currently working better in aarch64. I guess that you will have lots of things to explore. You rock! testing it out, might finally make an update to the video now that there is some good news to actually share XD I hope to see a refreshed version soon ). I'm the person that recently reached out about Turok's artwork. I'm also launching RetroArch 32Bit + mame2010_libretro_android from the same build without issues.īTW, I use "different" nicknames around the internet. RetroArch 64bit + flycast_libretro_android is working great. I've tested the modified version with 2019 No Clutter Classics. I could not figure how and where the edit is being made.Ī little later than expected, but here you go Bandit. How are you making the modification? I opened the apk up and was looking at the contents, but I am assuming you somehow edited the. Have you considered modifying it to support the other versions such as 64 bit for use with flycast? This is a much, much simpler way to fix the issue! Especially since the hyperspin android side of things seems to be dead, so its installed once and done. ra32 from the retroarch apk, which worked but requires more manual editing every time retroarch updates. Mupen64plus_next_gles3_libretro_android.so works in Retroarch, i assume i am using for this fix! I was using the alternate method of removing the. Rompath=/storage/ROMSTER2/Hyperspin/Emulators/Sega Dreamcast/romsĮxe=/ I also tried Dreamcast (Reicast works fine) Parameters=cores/mupen64plus_next_gles3_libretro_android.so Rompath=/storage/ROMSTER2/Hyperspin/Emulators/Nintendo 64/roms ini (my system name is ROMSTER2 which has a shared folder Hyperspin located on the 4TB) P.S: Do i need the modded Hyperspin to solve my issue, here is my. nothing works, which means it has to be the retroarch_32?Īppologies if this is confusing but i am a bit frustrated (like most newbies.) Note that all my roms are on SMB external drive (4 TB), which Retroarch can see and run smoothly, so what happens for Shield Tube 32-bit, do they need this command, or it's native 32-bit, also since Hyperspin is working i assume that is the 32-bit version running since i can't run Dolphin, but i can run Nintendo 64 roms fine, anyhow, maybe someone should make a separate Tutorial for people using Nvidia Shield 2019 (Tube Version) because i have tried everything, changing rompath, changing paths etc. Now i managed to get Hyperspin working ie just the wheels and videos load, but am stuck on the dreaded message "cannot load or execute rom" or something like that which now gets me to speculate if i am using ra_32 or not, no idea. Newbie here, i just wanted to point out i am probably one of the first to be using Nvidia Shield 2019 32-bit (Tube version), so now i am confused what Retroarch i have installed, before the site got hacked, i managed to download the 1.9.0 version which is running all games fine, MAME, SNES, PSX, etc. RetroArch_ra32 (1.8.8) 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |