Jump to content
HyperSync, HyperList and FTP are now back online ×


This topic is now archived and is closed to further replies.


(Tutorial) Hyperspin "System Name" Settings

Recommended Posts

Hyperspin Android "System Name" Settings (.ini) Files


What’s covered...


  2. Rompaths
  3. App/Game Launching parameters
  4. Finding App launch parameters
  5. Basic customisation


(All testing done on Nvidia Shield TV Pro)


Before We Start...

For the purposes of this tutorial I will be editing the .ini files with Notepad++ & screenshots on a Windows PC. You can use any Android or PC text editor to complete this task it was just simpler for the purposes of writing.



If using a combined Hyperspin PC and Android setup then you can get more information on the different settings from the notes provided in the HyperHQ program. HyperHQ directly controls all of your .ini files located in Hyperspin/Settings NOT Hyperspin/Settings_Android


For full original listings please see this post


What is Needed:

  1. Your set of .ini files (Located in your Hyperspin/Settings or Settings_Android folder
  2. Text Editor (any will do or use Notepad++)
  3. The set of clean and preconfigured .ini files (Settings_Android.zip) Included in the Android base pack I submitted.






Section 1


            This is where all the magic happens and should be your primary concern...


path=               (<Not Supported>)


rompath=         This will be the file path that contains your games for the specific system you are setting up. There are many options so I have listed the most common below


  1. If your games are contained within your Hyperspin directory then absolute paths are not required. Games stored in this location (Hyperspin/Emulators/Sega Mega Drive/roms) would have


rompath=Emulators/Sega Mega Drive/roms


  1. If your games are stored locally on the internal storage of you device the entry could be


rompath=/sdcard/”rom folder”/”next rom folder”


rompath=/storage/emulated/0/”rom folder”/”next romfolder”


  1. If your games are stored on an external USB HHD or USB thumb drive you will need to add the USB ID to the rompath (You should be able to see the ID by using ES File Explorer or alike)


rompath=/storage/A2CA0AEBCA0ABC13/”rom folder”/”next rom folder”


  1. If stored on a Network Attached Storage (NAS) device you will need to create and share a folder at the root level of your NAS and mount the NAS to your Android device


rompath=/storage/”NAS Name”/”Shared Folder”/



 exe=                           This line will launch the emulator/application


The specific commands written here are easily found in the forum and THIS post contains the most common ones

If you can’t find the launch command you need you can try an app like Quick Shortcut Maker. Install and run QuickShortcutMaker and it will detail all the apps you have installed and provide the different launch commands for the apps. (You will need to play about with this to get it right)


romextension=            This line should contain ALL file extensions for the games you are trying to launch, comma separated NO SPACES (Remember that support for compressed files like .7z and .zip is VERY limited in Android so MOST games need to be UNCOMPRESSED and be supported by the emulator)

                                    Extensions are also REQUIRED for the filtering system in Hyperspin


parameters=                 This line contains commands to launch a specific process for the app launched from the exe= line, also found in the post linked above.

These commands have be discovered by forum users and of course Reznate, by mainly contacting the app developer to request them



pcgame=                     This line is for the purpose of creating a system wheel that launches multiple apps. It will only launch the app or Android game without passing any parameters. The exe= line is ignored.


If set to TRUE you will need a specific SYSTEMNAME.xml in /Hyperspin/Databases/

You use the app launch command as the “game name” entries in the .xml file



Here is an example of a system wheel database named KODI. Setup to launch KODI apk and ES File Explorer apk



Section 2


                        This is the start of customising your setup!!!


 themes_only=             If set to true Hyperspin will filter your games list to ONLY show games that have a theme of MATCHING name located in /Hyperspin/Media/SYSTEMNAME/Themes


Remember ALL Artwork/Themes/Videos and Rom file names MUST match the

 <game name=”example game”> tags in the SYSTEMNAME.xml


roms_only=                If set to true then Hyperspin will filter your games list to only show games that are found in the rompath provided AND matching the extensions provided also


If you get “Missing rom file” error check your .ini rompath= and extensions= lines and make

sure your rom file names match your database xml “game name” tags






Section 3


This is where you enable/disable the transition videos that play when moving between games in your systems games list wheel. (The Hyperspin logo swooping across the screen and similar)


reload_backgrounds= true or false


Override Transitions are .flv videos stored in each one of your systems video folder. If named as a specific game matching your SYSTEMNAME.xml, they will play when moving onto that game in the wheel list


Location          Hyperspin/Media/NAME_OF_SYSTEM/Video/Override Transitions



Finishing Touches


The other options in the .ini files for each system are adjustments to the look of the games list wheel text (if not using images), game text (text in bottom left of screen showing the year, manufacturer and game description) and Special Art settings.


Note. I may do a further tutorial on this but right now I have run out of steam!!!


Special Art is setup in the same way as the Main Menu.ini. Special Art C is for the Genre feature which is not supported on Android so can be ignored




Game Text is best setup manually by changing the corresponding values for colour, shadow, colour ratio and position. To get the values use HyperHQ as directed below. You can also enable and disable what information is displayed. (Although the sticky post shows Not Supported I know that you can disabled the manufacture text from diplaying as I have this off in my MAME wheel)



Wheel Text is best configured by using HyperHQ. Adjust the settings under the options Wheel Settings -> SYSTEMNAME -> Wheel -> Wheel Text


Here you can find the colour HEX values and adjust the shadow and ratios to fit your themes



Lift the settings from HyperHQ or an adjusted PC setup settings file and edit them here



The last section I will briefly cover is...


Navigation settings



This section customises how your games list wheel responds. Most are self explanatory bar one


use_indexes= true or false


This setting along with your database SYSTEMNAME.xml settings determine in what order your games list is displayed. It also allows for proper use of the letter skip function for jumping through the games list by letter.


If your games database xml is NOT in alphabetical order then you must have ONE game entry set to index=”true” AND set the above use_indexes to true. Now your games list will be ordered exactly as they are in the xml not alphabetically


If there are no index=”true” tags in your database then Hyperspin will list your games alphabetically by game description.


All official databases are ordered alphabetically with correct indexes this makes skipping by letter simple.



If you have read this all you deserve a break and a pat on the back!!


This has been a tough one to write so please comment if there are any mistakes. I will update them


Hope this helps someone

Share this post

Link to post
Share on other sites

How do you know what to name the system.ini file? 

​Example:  SNK Neo Geo or Neo Geo?


Hyperspin has to be looking for a spedific name I would guess which also needs to match your database.xml and media folder name for that system correct?


Will it work just as long as you match the main wheel database system name?  Essentially where do you define what that system name is going to be so the structure works?

Share this post

Link to post
Share on other sites

Answered in other thread. Maybe I will add your comment to this guide. Good spot

Btw has this helped you at all? Just wondered if the tutorials are worth the effort

Share this post

Link to post
Share on other sites

Yes helpful.  I have a fully working PC setup in my cabinet but this android build is giving me issues.  I have all the stuff setup but when i hit a rom for a system the screen flashes quick and nothing happens.  Roms open fine direclty in retroarch.  NES and Genesis roms are zipped but i did have this working at some point so dont think thats the issue.  Has to be something in the .ini file but i can't find any issues.  Roms are found, media and everyting is there, database files match the same name as roms so not sure.....

Share this post

Link to post
Share on other sites

Yes helpful.  I have a fully working PC setup in my cabinet but this android build is giving me issues.  I have all the stuff setup but when i hit a rom for a system the screen flashes quick and nothing happens.  Roms open fine direclty in retroarch.  NES and Genesis roms are zipped but i did have this working at some point so dont think thats the issue.  Has to be something in the .ini file but i can't find any issues.  Roms are found, media and everyting is there, database files match the same name as roms so not sure.....


Perhaps your parameters line is incorrect in the .ini file, this determines which retroarch core is used. It could just be a typo or maybe you haven't downloaded that particular core in retroarch's online updater. Yes I know the games are working in Retroarch but you could be say using picodrive in RA when your Sega Megadrive.ini has genesis_plus_gx set to load and hence no dice when lauching from Hyperspin. Long shot but anything is possible, it's always a silly little mistake that trips us up.

I have a USB HDD attached as adoptive storage to the Shield TV, my Roms folder is inside the Hyperspin folder. It definitely works so I'll give you a snippet from my Sega Megadrive.ini if it helps you.


path=/storage/emulated/0/Hyperspin/Roms/Sega Mega Drive/
rompath=/storage/emulated/0/Hyperspin/Roms/Sega Mega Drive/

Share this post

Link to post
Share on other sites
On 28/10/2016 at 2:05 PM, ejay81 said:

Yes helpful.  I have a fully working PC setup in my cabinet but this android build is giving me issues.  I have all the stuff setup but when i hit a rom for a system the screen flashes quick and nothing happens.  Roms open fine direclty in retroarch.  NES and Genesis roms are zipped but i did have this working at some point so dont think thats the issue.  Has to be something in the .ini file but i can't find any issues.  Roms are found, media and everyting is there, database files match the same name as roms so not sure.....

I have the same issue with Retroarch and hyperspin. Games launch fine in Retroarch but only flickers in Hyperspin. Could it be the path settings inside Retroarch?

Share this post

Link to post
Share on other sites

Probably chech the parameter line is using the core you want to use and you have the core installed.


Share this post

Link to post
Share on other sites

  • Similar Content

    • By thatman84
      (FYI having trouble with upping some screenshots and the new formatting so please excuse the wierd format)
      Converting 16x9 Themes for Hyperspin Android
      List of theme animation compatibility
      (I am in NO way competent with artwork resolutions but my method works and looks good to me)
      Because sometimes that theme you really liked just doesn’t display correctly 
      The main reason for theme problems is the use of animation and scripting of the .swf assets in the “theme”.zip
      (It’s best to replace themes that cause Hyperspin to crash out, but you can try to convert them)
       What’s covered...
             1.      Extract PNG assets from swf files
             2.      Reduce HQ artwork to be compatible with Hyperspin
             3.      Further reduce artwork width to allow for Hyperspin 4x3 -> 16x9 stretching
             4.      Recompile your theme
      What is Needed:
      Update on resizing tool.
            Fotosizer is now advised against because of the compression/quality loss it causes.
      pPlease use Photoshop or this program recommended by @IceLancer https://sourceforge.net/projects/easyimagesizer/?source=typ_redirect
      A    A  Fotosizer (http://www.fotosizer.com/) batch resize image files
              B.     Flash Decompiler (https://www.free-dec...flash/download/) extract png’s from swf
              C.     Time and Themes
       I have done a little testing for Main Menu themes. This spreadsheet shows what I have tested and its Android compatibility status. The sheet has download section links for all themes I have tried.
      Let’s get to it... 
      So grab a theme zip you want to play with and Unzip it. Any 16x9 Main Menu, Game or System Default theme will do.
      BakerMan provided me a guide to extracting the PNG’s from SWF but it has since been lost. 
      These are the steps
              1.      Open JPEXS once downloaded and installed from link above
              2.      Click on the “Open” tab and browse to the offending .swf file from your unzipped theme


             3.      Right click on “Images” on the left and click “Export Selection”
      (At this step you may find multiple images. If these images are only parts of one image, say the arms and legs of a character, you will have to lose that image completely from the theme or replace it with another one)
             4.      Click “ok” to PNG file type then choose a location for the exported images (Default is Desktop. Only export one at a time and  then move the PNG out of the output folder as it overwrites each one if not)
             5.      Now browse to that Output location and you will find your PNG’s in an “images” folder.

      You are now ready for phase 2 – Resizing the images
      Note, fotosizer does cause a reduction in artwork quality. If your sensitive to this you may want to use another method. (If you know of a better program please comment) I only run a 37' screen and don't mind myself.
      (Resizing Artwork is covered comprehensively by Avar in his tutorials found HERE)
      Open Fotosizer Add the Artwork that was converted to PNG Reduce the images to 68% KEEP MAINTAIN ASPECT RATIO TICKED (this is the best size for the ones I have done)  
              4.       Move the right side settings bar down and select an Output Folder

      5   Remove that Artwork from Fotosizer
      6.   Add the newly resized artwork back into Fotosizer
      7.   Reduce the Width to 75% (to allow HS to stretch it back when its loaded)
             9.   Now add this finished art back into the theme folder and zip it up again
             10.       Name the zip file the same as you have it in the “Main Menu.xml” database
      Final Thoughts...
      Now when you try this theme out you may find the artwork has slightly changed location. If so adjust the Artwork positions in the theme.xml file within the theme.zip OR load it into Hypertheme and adjust it as required
      Hope this helps someone.
      HS Android Theme Animations.txt
    • By reznnate
      Tested Emulators -- .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 etc...     Dolphin - Gamecube/Wii/Wiiware exe=org.dolphinemu.dolphinemu/org.dolphinemu.dolphinemu.activities.MainActivity parameters=AutoStartFile    Newer Builds from Dolphin Website:-   exe=org.dolphinemu.dolphinemu/org.dolphinemu.dolphinemu.ui.main.MainActivity parameters=AutoStartFile    IrataJaguar - Atari Jaguar  exe=ru.vastness.altmer.iratajaguar/ru.vastness.altmer.iratajaguar.MainActivity  parameters=rom   Real3DOPlayer - 3DO  exe=ru.vastness.altmer.real3doplayer/ru.vastness.altmer.real3doplayer.MainActivity  parameters=cd   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=   Mupen64Plus AE exe=paulscode.android.mupen64plus/paulscode.android.mupen64plusae.MainActivity
      parameters=    Nightly builds exe=org.mupen64plusae.v3.alpha/paulscode.android.mupen64plusae.SplashActivity parameters=     Play! - Playstation 2 exe=com.virtualapplications.play/com.virtualapplications.play.ExternalEmulatorLauncher parameters=   Reicast - Dreamcast  exe=com.reicast.emulator/com.reicast.emulator.MainActivity  parameters=   Redream - Dreamcast exe=io.recompiled.redream/io.recompiled.redream.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.ppsspp.PpssppActivity              parameters=   uoYabause - Sega Saturn exe=org.uoyabause.android/org.uoyabause.android.Yabause
      Yaba Sanshiro
      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   OpenBOR - 2D Game Engine (Some integration issues with Hyperspin)              exe=org.openbor.engine/org.libsdl.app.SDLActivity Parameters=   Launch android app package names in database.xml Determine Android game name through Google Play web interface. i.e. https://play.google....ure.dragonslair   pcgame=true
    • By sanchezmike01
      Ok usually I dont ask for help for android but this is a 1st for me....as I scroll thru the Sega mega drive wheel I added, once it gets to the 1st game starting with letter "O", hyperspin crashes ...even if i navigate using the letters option when i get to letter "O" again it crashes....i use a default theme i made and have cart art, boxart,and wheel for all the games  ...will upload a log as I'm clueless to what happening...thanks
    • By thatman84
      My Attempt at making Andriod, MAC, PC users 1st steps in to Hyperspin Android easier
      This is an adjusted version of the Media and Databases that are included with Hyperspin Full Install 1.3.3
      Tweaked and cutdown for use directly with Android devices (It will not directly work with a PC although you can merge it with a PC setup to aid the building of an Android setup)
      Whats Included
      Indenticle Media files as 1.3.3 with some removals Pre configured Settings files Brief Android Emulator setup notes MAME Adjusted xml for 0.139 ROM set (Default one included also Outdated) Additional Settings files for 123 systems/collections (Provided by Badhemi)  

      Systems Included & Emulators suggested
      Atari 5200 (Retroarch MAME (Arcade) Core)
      Atari Lynx (Retroarch Handy Core)
      MAME (MAME4droid Reloaded (Red) 0.139v romset
      NEC TurboGrafx-16 (Retroarch Mednafen PCE Fast Core)
      Nintendo 64 (Retroarch Mupen64Plus Core or Glupen Core)
      Nintendo Entertainment System (Retroarch Nestopia Core)
      Nintendo Game Boy Advance (Retroarch VBA Next Core
      Panasonic 3DO (Retroarch 4DO Core)
      Sega 32X (Retroarch Picodrive Core)
      Sega CD (Retroarch Picodrive Core)
      Sega Dreamcast (Reicast 73e2691 2016_05_22 Build)
      Sega Game Gear (Retroarch Genesis Plus GX Core)
      Sega Genesis (Retroarch Picodrive Core)
      Sega Master System (Retroarch Picodrive Core)
      SNK Neo Geo (Retroarch FB Alpha Core)
      SNK Neo Geo Pocket Color (Retroarch Madnafen NGP Core)
      Sony PlayStation (Retroarch PCSX Rearmed Core)
      Super Nintendo Entertainment System (Retroarch BSNES Mercury Performance Core)
      See this Thread for details
      (Tutorial) Hyperspin Android Overview & Installation
      Install Notes
      To install this Hyperspin Android base pack
      Step 1 - Combine the download parts
      Extract the "Hyperspin 1.3.3 Android PT1" (Hyperspin.zip) file
      Place the "Hyperspin 1.3.3 Android PT2" (Media.zip) file within the extracted Hyperspin folder
      Extract the "Hyperspin 1.3.3 Android PT2" (Media.zip) file and it will combine the two parts
      Alternativly extract both files and the cut and paste them together
      (Optional Addition)
      Extract the Settings_Android.zip and pick out the settings files you require as you build your setup. Place them in your Settings folder or Settings_Android folder depending on your setup Rename specific systems if needed ADD YOUR ROMPATH  

      Step 2 - READ the Setup Notes.txt
      Step 3 - Organise your roms
      Organise your roms so they are located in the suggested folder structure OR place them in a location of your
      own choice.
      MAKE sure you adjust the "SYSTEMNAME".ini files to reflect your own rompath
      ****Remeber rom names will need to exactly match your Hyperspin databases (.xml) and be in a format that your
      chosen emulator can open****
      Step 4 - Move the pack to your Android Device
      Once you have the complete Hyperspin folder place this at the root of your storage device connected to your android device
      (USB HDD, Internal storage, SDCard or Network drive)
      Step 5 - Download and configure your emulators
      Step 6 - Install Hyperspin Application
      Download and install the Hyperspin application from the Goggle Playstore
  • Create New...