Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Announcement

    Sorry for the recent downtime. Still much to do but we have the site updated, secure and back online.  Expect more changes.

Hyperspin modified for RetroArch 32bit (aka Retroarch_ra32)


Honosuseri
 Share

Recommended Posts

21 hours ago, monoculero said:

Hello. I am from Spain, and a Nvidia Shield user. Install Hyperspin 0.1.8_Hono, later Retroarch_ra32_1.8.8 and configure it downloading cores, asets and other things. When I run a selected game on Hyperspin, always get a black screen. What am I doing wrong? This is my mame.ini file on settings folder:

 

Thanks for the work!

Do your MAME games work in just Retroarch? There are different cores to use for different MAME romsets and I have no idea which set you are using. it's best to know the games play first before you worry about the frontend Hyperspin. Remember your .ini files to be used live in the "Settings_Android" folder. "Settings" is for a PC setup, these folders are separate for those who want to use an external USB drive and switch it between a PC and an STV

Link to comment
Share on other sites

2 hours ago, monoculero said:

Ok, the parameters are incorrect. I have done some custom system, like cps, and these are correctly funcionals. 

The error was mine, because on retroarch the roms are working like a charm. 

Thanks for help. 

Happy to hear you sussed it out. Part of the reason I modded Hyperspin to use RA32 was so we got that Mame2010 core to use, it's missing in the 64 bit version of RetroArch.

All the best with your setup, have fun with it!

Link to comment
Share on other sites

  • 4 weeks later...
On 5/24/2020 at 11:57 AM, Honosuseri said:

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. 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. In a nutshell currently we have access to more cores for us to play our retro systems on the 32 bit version. 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.

So...I decompiled the Hyperspin.apk and made the necessary changes (yes including the config path) to solely use RA_32. 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!). Feel free to download it and test yourselves, obviously backup your essential files AND do remember the .ini files need to be adjusted to use RA32....

exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
becomes
exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture

It's easy enough to open all your .ini files with notepad++. Use the Search and replace feature to find com.retroarch/ and replace to com.retroarch.ra32/ do this for all opened files then save all.

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. 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.

Mega Link for Hyperspin_0.1.8_Hono.apk (https://mega.nz/file/zQNBCYKI#QVrG4uVVmvXHshl8LbosQi7LAjQmUA09R5k_YqhcMBI)
RetroArch_ra32 (1.8.8) newest stable version at time of posting (http://buildbot.libretro.com/stable/1.8.8/android/)

Greetings,

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.

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. 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.. nothing works, which means it has to be the retroarch_32?

Appologies if this is confusing but i am a bit frustrated :) (like most newbies...)

P.S: Do i need the modded Hyperspin to solve my issue, here is my  .ini (my system name is ROMSTER2 which has a shared folder Hyperspin located on the 4TB)

 

[exe info]
path=
rompath=/storage/ROMSTER2/Hyperspin/Emulators/Nintendo 64/roms
userompath=true
exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
parameters=cores/mupen64plus_next_gles3_libretro_android.so
romextension=n64
searchsubfolders=true
pcgame=false
winstate=HIDDEN
hyperlaunch=true

I also tried Dreamcast (Reicast works fine)

[exe info]
path=
rompath=/storage/ROMSTER2/Hyperspin/Emulators/Sega Dreamcast/roms
userompath=true
exe=com.reicast.emulator/com.reicast.emulator.MainActivity
romextension=CDI,cdi
parameters=
searchsubfolders=
pcgame=false
winstate=HIDDEN
hyperlaunch=true

mupen64plus_next_gles3_libretro_android.so works in Retroarch, i assume i am using 32-bit... 

Regards,

Link to comment
Share on other sites

On 8/23/2020 at 7:20 AM, oyehia said:

Greetings,

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.

You'd know better than me, you are the one who downloaded the file and installed it. Retroarch.apk is the 32bit, aarch64 is 64bit, ra32 is a separate dedicated 32bit build. Hyperspin needed modding to use ra32.

Sounds to me like your issues are the rom path as you're doing it over a NAS. It can be done, someone mentioned earlier in this thread they are running multiple STVs from a samba share. Edit one of your .ini files so under filters "roms only = True". If you load that wheel and nothing shows then then rompath is wrong. If set as "roms only = False" it's just showing everything listed in the database.xml file whether you have it or not.

Link to comment
Share on other sites

@Honosuseri

Thanks for this fix! I was using the alternate method of removing the .ra32 from the retroarch apk, which worked but requires more manual editing every time retroarch updates. 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. :)

Have you considered modifying it to support the other versions such as 64 bit for use with flycast?

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 .so files. I could not figure how and where the edit is being made. 

Link to comment
Share on other sites

  • 4 weeks later...

Maybe this has nothing to do with this particular version of Hyperspin/Retroarch but is there a particular way to use a Shield Controller with Playstation games using pcsx_rearmed_libretro_android.so?

It starts the rom perfectly no issues, my Shield controller shows like it's mapped but just not usable at all.. should I be doing something special? I thought it was setup through the autoconfig process...

Link to comment
Share on other sites

  • 6 months later...
On 8/30/2020 at 11:20 PM, thebbandit said:

@Honosuseri

Thanks for this fix! I was using the alternate method of removing the .ra32 from the retroarch apk, which worked but requires more manual editing every time retroarch updates. 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. :)

Have you considered modifying it to support the other versions such as 64 bit for use with flycast?

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 .so files. I could not figure how and where the edit is being made. 

A little later than expected, but here you go Bandit.

I've tested the modified version with 2019 No Clutter Classics. RetroArch 64bit + flycast_libretro_android is working great. I'm also launching RetroArch 32Bit + mame2010_libretro_android from the same build without issues. 
BTW, I use "different" nicknames around the internet. I'm the person that recently reached out about Turok's artwork.
Your collection is great. I hope to see a refreshed version soon ;).

  • Super Like 1
Link to comment
Share on other sites

3 hours ago, thebbandit said:

you rock! testing it out, might finally make an update to the video now that there is some good news to actually share XD

Let me know how it goes. I guess that you will have lots of things to explore. Quite a few cores are currently working better in aarch64. Specially Vulkan stuff.

I'm mainly on 5th Gen consoles.

Mupen64Plus-Next + Parallel RDP runs great. I'm actually upscaling to 1440p without losing performance on my Shield (even Golden Eye and Perfect Dark). Some games can even be pushed to 4K. I'm not getting this combination of performance + accuracy even with Mupen64Plus FZ.

Swanstation core is also running great, although falling behind compared to DuckStation's master (DuckStation unfortunately still needs some tweaks to run on NVIDIA Shield. Once it does I may "hack" HyperSpin to launch it as well). I managed to run Driver 2 upscaled to 4k with PGXP enabled.

For 6th gen: Flycast is running great. Dolphin is still somewhat hit and miss (IMO, standalone is still better).

Haven't had the time to play with PPSSPP or Saturn cores yet.

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Similar Content

    • By therourke
      I have a fully working build for Commodore Amiga now on my NVIDEA Shield (2017 model). It took me a good while to get it up and running.

      I thought it might be useful to post an 'all in one place' tutorial. Thanks go to Honosuseri over in this post for convincing me it was possible.
      Commodore Amiga is infamously painful to configure on any and all emulation setups. Retroarch takes the pain out of some of this, since we don't need individual .uae files for every single game now. But there are still some hoops to jump through.
      Onto the tutorial
       
      1. Find/setup your own Hyperspin
      Hyperspin is free and available on this very website. Install the app on your NVIDEA Shield, and compile your roms and Hyperspin setup on an appropriately sized external harddrive/USB.
      As for the ROMs, videos, wheel images and all the aesthetic stuff you need to get your setup running, you will have to source that yourselves. The Hyperspin website is good for some material, emumovies for videos, and Google and Archive dot org for everything in between. 
      For this setup I used a properly named romset for Commodore Amiga in .zip format, but you can also use .lha or .hdf format. .lha is smaller in size, but all of these run pretty much the same on Retroarch now. 
      There is no need for those pesky .uae files anymore!!!!!!!!!!
      Once you have all your roms, you will need to allocate them to the right videos and images and build your .xml database. The info for how to do this is available elsewhere on this very website. I used HyperspinChecker to do this.
      Now, onto the part where we make Hyperspin and Retroarch play nicely so you can finally play your Commodore Amiga games 
      2. WHDLoad and kickrom setup (bios file preparation)
      I obviously can't link to kickroms or WHDload.hdf and some other stuff, but Google is your friend.
      You can get kickroms legally as part of the Amiga Forever app on Google Play Store for only £1.79.
      You ABSOLUTELY NEED to get hold of these EXACT kickroms:
      kick34005.A500 kick37175.A500 kick40063.A600 kick40068.A1200 Some info on kickrom file names and how to match them up correctly can be found here.
      MAKE SURE THE FILENAMES ARE PRECISE! I left one of those As in lowercase and Retroarch didn't like it.
      You also need a properly prepared WHDLoad.hdf file: ADD THESE EXACT KICKROMS TO YOUR WHDload.hdf file (guide to do this here using ADF Opus)
      Copy all these file to the external drive you are keeping your Hyperspin setup on (I made a 'bios' folder in mine for safe keeping).
      3. Retroarch Setup
      Install the latest Retroarch on your NVIDEA Shield (probably works on other Android setups too). You can do this through the Google Play store, but as of writing this, version 1.8.9_GIT definitely works.
      You will need to make sure you have setup a way to load the Retroarch main menu from within games. Go to 'Settings', 'Input', 'Hotkeys' and set the 'Menu Toggle Gamepad Combo' to something like 'Select + Start'.
      Download the latest Commodore - Amiga (P-UAE) core from within Retroarch (use 'Online Updater' menu)
      Now 'Load Core' and choose the P-UAE Core. Start the core, then immediately go back to the Retroarch menu (Start + Select). From the 'Quickmenu' select 'Options'. Change the 'Model' here to something with plenty of power like the 'A1200 (2MB + 8MB)'. Scroll down to 'WHDLoad Support' and make sure this says 'HDFs'.
      (NOTE: ONLY if that last setting doesn't work, try this: Scroll down to 'Global Boot HD' and 'WHDLoad Support' and make sure both of these are marked as 'Files'.)
      One other thing from within Retroarch: having a way to 'Quit' from within games is useful for Hyperspin. So go to 'Settings', 'Hotkeys' choose a button for 'Quit Retroarch' (I use the click of my Left Analogue, but anything will do). You may also need to mess around with button mappings, but most of this should work fine if you have a NVIDEA Shield compatible gamepad. Mouse and keyboard are also, obviously, nice additions for Amiga stuff.
      Go back to 'Quick Menu', 'Overrides' and select 'Save Core Overrides' to make sure your Retroarch Amiga setup is saved.
      Lastly, and very importantly...
      Leave Retroarch. You will need an Android directory viewing program like 'FX File Explorer' for this step. Copy the EXACT kickroms listed above and the WHDload.hdf file you created into the /Retroarch/System/ folder on the INTERNAL drive of the NVIDEA Shield.
      4. Commodore Amiga.ini Commands
      In your Hyperspin setup you should now have all your roms, videos, images, menu setup, and a Commodore Amiga.xml database file all neat and tidy.
      You now need to get Hyperspin to talk to Retroarch properly.
      Back on your PC, load your Hyperspin folder and go to the /Settings_Android/ folder.
      Create or open the Commodore Amiga.ini in a text editor. Most of the stuff in here will be the same as other systems, but you can find my ini file attached here.
      Make sure the top lines in your ini read like this:
      [exe info] path=H:\hyperspin\emulators\Commodore Amiga\ rompath=Roms/Commodore Amiga/roms userompath=true exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture romextension=zip,hdf,lha,HDF,ZIP,LHA parameters=cores/puae_libretro_android.so searchsubfolders=false pcgame=false winstate=HIDDEN hyperlaunch=true Each of these lines corresponds to your setup. So if you have your roms folder somewhere else, you need to tell the file. If you are ONLY using .zip versions of your roms, then you don't need the entire 'romextension=zip,hdf,lha,HDF,ZIP,LHA'  line - you can change this to just 'romextension=zip' and it will work fine. (But my line here covers all the possible rom extensions, so you can leave it). The 'exe' and 'parameters' entries are really important, as this tells Hyperspin to load Retroarch, and then Retroarch which core to load for Commodore Amiga.
      Save your file, and hook your Hyperspin external drive back to your NVIDEA Shield.
      5. Play some games
      Everything *should* be working now. If you are having problems with videos and roms matching up, or entries showing in the Amiga menu on your Hyperspin, then that is an issue with your original setup. There are many tutorials out there.
      I can vouch that THIS EXACT setup works great, and loads and plays most Amiga games I have thrown at it without too many glitches.
      6. Now, please answer me a Q 
      When using an external mouse in Retroarch and playing a game like Lemmings, I get TWO cursors - the in game Lemmings cursor, and the NVIDEA Shield arrow.
      Does anyone know how to get rid of this for good? Thanks
      Commodore Amiga.ini
    • By HyperSeeder
      To anyone following my posts lately, I have been working in modifying HyperSpin so that it can run all modern versions of RetroArch. I know that some of you have been waiting for it since 2019.
      Well, the wait is finally over.
      Download:
      HyperSpin_v0.1.8_HyperSeeder.apk: https://mega.nz/file/uNx0gQQA#f5ktYDOV6nMAWxatrlg6XAYz14ZMdYlkWg994s-1WDg
      MD5: 4692846e4fe9a90bd0da3a6cd9f10ed3
      SHA512: 2f5db6b625983c189b9f82c574bf48781921780825a38ceaf9c1094bd113545f9abdd06c5b4ac8707093e3e2ac0fc1185b9bc939f30f5ee830a41689c68e5b21
      How to configure your Settings_Android ini files:
      Main APK from RetroArch's website and Google Play Store Version:
      exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture RetroArch's website 32bit version:
      exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture RetroArch's website 64bit version and RetroArch Plus:
      exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture Have fun!
      FAQ:
      Can I mix and match multiple RetroArch distributions?
      Yes, you just need to set different exe values for different systems.
      For instance, you can use the 64bit version of RA + Dolphin core for GameCube games (Nintendo GameCube.ini): exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture parameters=cores/dolphin_libretro_android.so
      And the 32bit version of RA + MAME Core (MAME.ini): exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture parameters=cores/mame2010_libretro_android.so  
      Will it load separate configuration files for 32bit and 64bit versions?
      Yes, it will always load the default configuration file for each version.
      Default configuration files are in /storage/emulated/0/Android/data/[package name]/files/retroarch.cfg
      For example:
       
      /storage/emulated/0/Android/data/com.retroarch.ra32/files/retroarch.cfg  
      Can I make Hyperspin launch my own custom compiled version of RetroArch?
      Yes. As long as the package name starts with com.retroarch everything should work.
      Can I configure HyperSpin to load retroarch.cfg from a custom location?
      Not for now. I find that I can accomplish what I want with the default config file + settings overrides.
      If you have a specific use case that would benefit from this feature comment bellow and I'll see what I can do.
      How was this implemented?
      I reversed engineered the original Google Store APK using Apktool and JEB.
      You can find the two lines of code that I've modified bellow. You can use APK Studio to verify my changes.
       
      Has it been tested?
      I tested it with my NVIDIA Shield 2017 and 2019. It worked with all mentioned distributions, RA versions 1.9.0 to 1.9.8 How can I help?
      If you know someone able to get my two lines change integrated in the official build and published to the Google Play Store, please point the person to this topic. Acknowledgment: Many thanks to@zerojay, @yarrick and @Honosuseri for "hacking" their own versions of HyperSpin. While this version is my own work, I couldn't do it without the information that you all made available to the community.
    • By HyperSeeder
      HyperSpin v0.1.8 for Android
      This is an unofficial version of HyperSpin for Android able to launch all modern versions of RetroArch.
      Support topic: https://hyperspin-fe.com/forums/topic/42774-modified-hyperspin-apk-for-retroarch-works-with-all-modern-versions/
      File Information:
      HyperSpin_v0.1.8_HyperSeeder.apk
      MD5: 4692846e4fe9a90bd0da3a6cd9f10ed3
      SHA512: 2f5db6b625983c189b9f82c574bf48781921780825a38ceaf9c1094bd113545f9abdd06c5b4ac8707093e3e2ac0fc1185b9bc939f30f5ee830a41689c68e5b21
      How to configure your Settings_Android ini files:
      Main APK from RetroArch's website and Google Play Store Version:
      exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture RetroArch's website 32bit version:
      exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture RetroArch's website 64bit version and RetroArch Plus:
      exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture Have fun!
      FAQ:
      Can I mix and match multiple RetroArch distributions?
      Yes, you just need to set different exe values for different systems.
      For instance, you can use the 64bit version of RA + Dolphin core for GameCube games (Nintendo GameCube.ini): exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture parameters=cores/dolphin_libretro_android.so
      And the 32bit version of RA + MAME Core (MAME.ini): exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture parameters=cores/mame2010_libretro_android.so  
      Will it load separate configuration files for 32bit and 64bit versions?
      Yes, it will always load the default configuration file for each version.
      Default configuration files are in /storage/emulated/0/Android/data/[package name]/files/retroarch.cfg
      For example:
       
      /storage/emulated/0/Android/data/com.retroarch.ra32/files/retroarch.cfg  
      Can I make Hyperspin launch my own custom compiled version of RetroArch?
      Yes. As long as the package name starts with com.retroarch everything should work.
      Can I configure HyperSpin to load retroarch.cfg from a custom location?
      Not for now. I find that I can accomplish what I want with the default config file + settings overrides.
      If you have a specific use case that would benefit from this feature comment bellow and I'll see what I can do.
      How was this implemented?
      I reversed engineered the original Google Store APK using Apktool and JEB.
      You can find the two lines of code that I've modified bellow. You can use APK Studio to verify my changes.
       
       
    • By iamthamiz
      Hi Guys if your trying to set up M64plus FZ on android this is what i did to get my one up and running with NVida Sheild TV
       
      exe=org.mupen64plusae.v3.fzurita/paulscode.android.mupen64plusae.SplashActivity
      parameters=
      romextension= n64,z64,zip,v64
      searchsubfolders=false
       
    • By Wandurlust
      Hi all, It seems retroarch (at least on android) has removed their Mupen64plus core and replaced it with Mupen64plus-next. My hyperspin (Nvidia shield) won't launch N64 games anymore because it's trying to launch a core that no longer exist. I have tried editing my "Nintendo 64.ini" file with multiple variations to get the new core to launch, but I cannot get it to work. Anyone know the new core parameters off hand? I've searched quite a bit and am coming up empty.  Just to clarify I'm looking for the "Parameters =" line under the exe= that determines which core retro arch will use. I have confirmed manually loading the "Mupen64Plus-Next" core works with content. I just can't seem to get the command line correct to have it launch from hyperspin. Any help is appreciated thanks! I have already switched to it launching "Mupen64 FZ" in the meantime, but I prefer the launch coming from retroarch because FZ resumes mid-game where you left off when starting from hyperspin, and I prefer the WOW factor of games loading from the title screen.
×
×
  • Create New...