Jump to content
HyperSync is currently undergoing maintenance ×
reznnate

SETUP: Hyperspin for Android

Recommended Posts

z7jPgNL.jpg?1  SETUP:  Hyperspin (for Android)
 
 
  • Install
    • Install Android .apk on your NVIDIA Shield portable, tablet, or TV/console
    • Copy data to internal storage or insert sdcard or connect USB hard drive with Hyperspin data
    • Run app
       
  • Android additions 
    • Hyperspin will seek and prioritize /usbdrive/Hyperspin first, then /sdcard1/Hyperspin, then /sdcard/Hyperspin for your data
    • Optional additional database file called "Main Menu_Android.xml" offers a subset or superset of wheels 
    • Optional additional settings folder called /Settings_Android allows both Windows and Android launcher/rompaths to co-exist.
    • Within settings .ini files, you can define multiple emulators on the exe= and parameter= lines (i.e. 2600.emu and Retroarch/Stella) and it will launch the first emulator that is installed.   See the example Android .ini files posted in the download area..
       
  • Upvote 4

Share this post


Link to post
Share on other sites
Supported Hyperspin ini config file settings

 

The two major types of ini config files in Hyperspin are Settings.ini, and the Game System.ini file that each wheel menu loads.    This is the list of currently supported ini config file options that are 'hooked up' in our Hyperspin Android app.    If not 'supported', then there is a hard-coded value or the parameter is ignored currently.

 

 

Settings.ini file

 [Main]

 Menu_Mode=<supports "multi" and "single" menu mode>

  -multi - Default mode that goes from Intro->Main Menu->Game Menu

  -single - Mode that goes from Intro->Game Menu

 Single_Mode=<supports name of directory to use for game level menu>

 Enable_Exit=<not supported>

 Exit_Default=<not supported>

 Exit_Action=<not supported>

 Version=<not supported>

 

 [Resolution]

 Not supported - It always renders fullscreen stretched to display

 

 [Optimizer]

 Not supported

  -It always renders with bilinear filtered textures

  -No support for backgrounds outside of video transitions

 

 [introVideo]

 Not supported - It always plays intro video and stops on keypress

 

 [sound]

 Not supported - Only controllable with Android volume controls

 

 [AttractMode]

 Not supported

 

 [Keyboard]

 [P1 Controls]

 [P2 Controls]

 [P1 Joystick]

 [P2 Joystick]

 [Trackball]

 [spinner]

 Not supported - Only hardcoded support for Android controllers

 

 [startup Program]

 [Exit Program]

 [LEDBlinky]

 [HiScore]

 Not supported

 

 

 

Game System.ini file  

 [exe info]

 path=<not supported>

 rompath=<supports absolute path to menu's rom directory>

 userompath=<not supported, it's always "true">

 exe=<supports package/class format of launching intents>

 romextension=<supports comma-seperated list of rom extensions to use>

 parameters=<supports "cores/emulator_library.so" format for libretro>

 searchsubfolders=<not supported, does not search subfolders>

 pcgame=<supports "true" and "false">

  -true - Looks in database.xml for package/class to launch

  -false - Launches "exe" intent with "parameter" options

 winstate=<not supported>

 hyperlaunch=<not supported, always "false">

 

 [filters]

 parents_only=<not supported, always "false">

 themes_only=<supports "true" and "false">

 wheels_only=<not supported, always false>

 roms_only=<supports "true" and "false">

 

 [themes]

 Not supported

 

 [wheel]

 alpha=<not supported, always "1">

 speed=<not supported>

 vert_wheel_position=<not supported, always "right">

 text_with_images=<not supported, always "true">

 text_width=<supports any pixel width value>

 text_font=<not supported, always uses default font>

 small_text_width=<supports any pixel width value>

 large_text_width=<supports any pixel width value>

 text_stroke_size=<not supported>

 text_stroke_color=<not supported>

 text_color1=<supports hex value color>

 text_color2=<supports hex value color>

 text_color3=<not supported>

 color_ratio=<not supported>

 shadow_distance=<not supported>

 shadow_angle=<not supported>

 shadow_color=<not supported>

 shadow_alpha=<not supported>

 shadow_blur=<not supported>

 

 [pointer]

 x=<supports any x value>

 y=<supports any y value>

 

 [video defaults]

 Not supported

 

 [sounds]

 Not supported

 

 [navigation]

 Not supported

 

 [artwork2 defaults]

 [artwork3 defaults]

 [artwork4 defaults]

 Not supported

 

 [special Art A]

 [special Art B]

 default=<supports "true" or "false" use of default special art in "Main Menu">

 active=<supports "true" or "false" to enable rendering of special art>

 x=<supports x location of special art>

 y=<supports y location of special art>

 in=<not supported>

 out=<not supported>

 length=<supports seconds of how long each special art file should display>

 delay=<not supported>

 type=<not supported>

 start=<not supported, always "none">

 

 [Game Text]

 game_text_active=<not supported, always "true">

 show_year=<not supported, always "true">

 show_manf=<not supported, always "true">

 show_description=<not supported, always "true">

 text_color1=<supports hex color of top of text>

 text_color2=<supports hex color of bottom of text>

 stroke_color=<supports hex color of text outline>

 text_font=<not supported, always uses default font>

 text1_textsize=<supports size of description text>

 text1_strokesize=<supports size of description text outline>

 text1_x=<supports x location of description text>

 text1_y=<supports y location of description text>

 text2_textsize=<supports size of title text>

 text2_strokesize=<supports size of title text outline>

 text2_x=<supports x location of title text>

 text2_y=<supports y location of title text>

 

 [Genre Screen]

 Not supported - Genre Screen not implemented

Share this post


Link to post
Share on other sites
Tested Emulators  

This is a list of tested emulators and their working ini config settings. 

 

Retroarch - Various emulators 

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

 parameters=<choose one of the emulator cores like below>

 

Examples of retroarch core parameters

Atari 2600 core:

 parameters=cores/stella_libretro_android.so

PSX core:

 parameters=cores/pcsx_rearmed_libretro_neon_android.so

 

libretro cores:

 4do_libretro_android.so

 bsnes_mercury_performance_libretro_android.so

 bsnes_performance_libretro_android.so

 catsfc_libretro_android.so

 desmume_libretro_android.so

 dinothawr_libretro_android.so

 dosbox_libretro_android.so

 fb_alpha_libretro_android.so

 fceumm_libretro_android.so

 fmsx_libretro_android.so

 gambatte_libretro_android.so

 genesis_plus_gx_libretro_android.so

 gpsp_libretro_android.so

 handy_libretro_android.so

 mame_libretro_android.so

 mednafen_lynx_libretro_android.so

 mednafen_ngp_libretro_android.so

 mednafen_pce_fast_libretro_android.so

 mednafen_pcfx_libretro_android.so

 mednafen_psx_libretro_android.so

 mednafen_supergrafx_libretro_android.so

 mednafen_vb_libretro_android.so

 mednafen_wswan_libretro_android.so

 mass_libretro_android.so

 meteor_libretro_android.so

 mupen64plus_libretro_android.so

 nestopia_libretro_android.so

 nxengine_libretro_android.so

 o2em_libretro_android.so

 pcsx_rearmed_libretro_android.so

 picodrive_libretro_android.so

 ppsspp_libretro_android.so

 prboom_libretro_android.so

 prosystem_libretro_android.so

 snes9x_libretro_android.so

 snes9x_next_libretro_android.so

 stella_libretro_android.so

 tgbdual_libretro_android.so

 ume_libretro_android.so

 vba_next_libretro_android.so

 vbam_libretro_android.so

 vecx_libretro_android.so

 virtualjaguar_libretro_android.so

 yabause_libretro_android.so

 

NES.emu - NES

 exe=com.explusalpha.NesEmu/com.imagine.BaseActivity

 parameters=

 

MSX.emu - Colecovision, MSX, etc.

 exe=com.explusalpha.MsxEmu/com.imagine.BaseActivity

 parameters=

 

Mame4Droid - MAME

 exe=com.seleuco.mame4droid/com.seleuco.mame4droid.MAME4droid

 parameters=

* rom folder path set inside app (need to request this fix)

 

Reicast - Dreamcast

 exe=com.reicast.emulator/com.reicast.emulator.MainActivity

 parameters=

 

Drastic - Nintendo DS

 exe=com.dsemu.drastic/com.dsemu.drastic.DraSticActivity

 parameters=GAMEPATH

 

Fpse - PSX

 exe=com.emulator.fpse/com.emulator.fpse.Main

 parameters=path

 

ePSX - PSX

 exe=com.epsxe.ePSXe/com.epsxe.ePSXe.ePSXe 

 parameters=com.epsxe.ePSXe.isoName

 * change romext=cue in settings.ini, iso did not work for me

 

PPSSPP (FREE version) - PSP

 exe=org.ppsspp.ppsspp/org.ppsspp.ppsspp.PpssppActivity

 parameters=org.ppsspp.ppsspp.Shortcuts

PPSSPP Gold - PSP

 

 exe=org.ppsspp.ppssppgold/org.ppsspp.ppssppgold.PpssppActivity

 parameters=org.ppsspp.ppssppgold.Shortcuts

 

Gearoid - Sega Game Gear

 exe=com.androidemu.gg/com.androidemu.gg.EmulatorActivity 

 Parameters=

 

Colem - Speccy ZX - fMSX VGBANext

 Emulators from Garage Research

 PAID

 com.fms.colem.deluxe - Colem - Colecovision

 com.fms.fmsx.deluxe - fMSX

 com.fms.ines - iNES

 com.fms.emu - VGBAnext - GBA/GBC/GB Emulator

 com.fms.vgb - VGBc - Gameboy Color

 com.fms.mg - Master Gear - Sega Game Gear

 com.fms.speccy.deluxe - Spectrum Sinclair ZX

 FREE

 com.fms.colem

 com.fms.fmsx

 com.fms.speccy

 

 Set "??" to "com.fms.emulib.MainActivity" for all products but VGBAnext. 

 For VGBAnext:

 ??=com.fms.vgba.MainActivity for opening *.gba files

 ??=com.fms.vgb.MainActivity for opening *.gbc/*.gb files

 

Launch android app package names in database.xml

Determine Android game name through Google Play web interface.


 

pcgame=true
  • Upvote 2

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Similar Content

    • By massaker77
      I bought it in 2015 but adding constantly mods and software.
      Finally I added extra leds, light guns and a custom integration with HyperSpin described here : https://github.com/cboudereau/ArcadeCab
      I also added more and more emulators, updated the hardware and used a Logitech Z5500 digital.

    • By Honosuseri
      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.9.0) newest stable version at time of posting (https://buildbot.libretro.com/stable/1.9.0/android/)
    • 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 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 '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 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...