Top Missing Features
8 members have voted
1. Top Missing Features from PC Version
Collections (launch multiple emulators from one wheel)4
Favourites/Genre (anyway to customise a full set without duplicating media)3
Horizontal Main/System wheels1
Other (please comment)0
2. Extra Features (over and above PC)
Default System Media to save space (default video, wheel, box, cart)3
Fix Libretro intent to allow custom CONFIGFILE path5
Please note my knowledge of this system does not run deep but everything here works and plays fine.
What is it?
Capcom Play System III or CPS-3 is an arcade system board that was first used by Capcom in 1996 with the arcade game Red Earth. It was the second successor to the CP System arcade hardware, following the CP System II. It would be the last proprietary system board Capcom would produce before moving on to the Dreamcast-based Naomi platform.
How to emulate in Android (Shield TV)
Quick and simple way is with the FBA core of RetroArch and matching FBA romset.
At time of writing current versions are:-
Core:- FB Alpha v0.2.97.42 (commit 6b7a701)
FBA:- 0.2.97.42 (9 July 2017)
Other options are MAME core in RetroArch or MAME4Droid reloaded (0.139mame romset). I believe the CHD files are needed for some games and with MAME4Droid, at least, I had to "install" the game when it 1st launched in the emulator. That process took about 20-30mins and not all worked. Redearth was one I tested and "installed".
JoJo no Kimyouna Bouken: Miraie no Isan (Japan 990913) = (jojoba.zip)
JoJo's Venture (USA 990108) = (jojo.zip)
Red Earth (Euro 961121) = (redearth.zip)
Street Fighter III 2nd Impact: Giant Attack (USA 970930) = (sfiii2.zip)
Street Fighter III 3rd Strike: Fight for the Future (EUR 990608) = (sfiii3.zip)
Street Fighter III: New Generation (USA 970204) = (sfiii.zip)
I replaced this entry in the official database with the european version as I could not get it to launch in FBA.
Street Fighter III 3rd Strike: Fight for the Future (USA 990608) = (sfiii3u.zip)
1. Open RetroArch and download the Arcade (FA Alpha) core.
Main Menu -> Online Updater -> Core Updater
1a. Transfer your games to your prefered location (You only need the six zip files listed in the database and above)
2. Add the "Capcom Play System III" system to your Hyperspin setup with HyperHQ on a PC and transfer the files/folder to your device or by manually creating all the relevent folders to your device. (Download at bottom of guide)
3. Add Capcom Play SYstem III to your Main Menu.xml or Main Menu_Android.xml
4. Add these lines to your Capcom Play System III.ini file found in Hyperspin/Settings/ or Hyperspin/Settings_Android/
PLAY SOME STREET FIGHTER .......................
Under the FB Alpha "Quick Menu -> Options" you can select between different regions. Choosing a different region will give you the different loading screens along with other things I'm not sure about.
Street Fighter III 3rd Strike (Default)Euro
Street Fighter III 3rd Strike (USA)
ANDROID MEDIA PACK AND DATABASE (Get your videos from emumovies.com)
This is the start of the WIP guide and Amiga Project thread
DONT REPLY TO THIS THREAD
REPLY TO THIS ONE(clicky)
For now this will become a tempory guide to UAE4arm setup with the Ultimate Amiga Raspberry Pi Project a helpful source of information in google
Step 1 - Install Uae4arm (beta)
You need to follow this link to sign up to be a beta tester to gain access to the apk that can launch games directly from Hyperspin.
Link above taken from the English Amiga Board and the post below
Step 2 - Install Kickstarts
Database taken from this thread post
More to follow
Hyperspin Android Overview & Installation
And anyone I have forgotten helped me learn this
My guides are only an extension of Reznnate's sticky posts
PLEASE READ the OTHER sticky posts
What is it?
An Android version of Hyperspin that works with existing themes and data directly from the Hyperspin community. It launches both Android games and Android emulators.
Android hardware is getting faster and faster. Emulators for Android are getting better and better. We wanted to play with our Hyperspin setups outside the house. I wanted to replace the old PC in my MAME cabinet with a mobile device so I could justify leaving it on all the time. It needed the ultimate launcher!!!
Since the Windows version of Hyperspin is dependent on Adobe Flash, it was necessary to build the app from scratch. With performance in mind, the Android version is highly-threaded and renders with the GPU using OpenGL.
Android 4.4+ NVIDIA OpenGL drivers ONLY Tegra4, Tegra K1, Tegra X1 Drivers (Tegra Mobile Device List) Confirmed working device, but not limited to, Shield Portable, Tablet and TV, Google Nexus 9, MiiPad, ADT-1 Tested Emulators Release statements
RocketLauncher is not available for use on Android but the settings files it uses within a PC setup are compatible.
Vertical Systems/Wheel list only No Touch Screen Input (Controller required) Favourites list feature not supported Genre feature not supported Searching subfolders for ROM’s not supported Games list only supports launching of one emulator (multiple emulators can exist in settings line and the 1st one installed will be launched) PC based animations and themes not fully functional. See this detailed post HERE
Never used Hyperspin before?
As Hyperspin Android was originally designed to allow PC users to have another way to experience their setup you will need to first decide how you would like to proceed with your Hyperspin Android setup
**Skip to Installation section if NOT using a PC**
The easiest way is to install the PC version for testing and building your Android setup (Follow Avar’s official tutorial videos HERE or follow step by step guides HERE Alternatively build your Hyperspin Android setup from iOS computer or directly from your Android device.
Already using Hyperspin on a PC?
You can co-exist your PC and Android Hyperspin setups in one Hyperspin folder by making the following additions.
Optional additional database file called "Main Menu_Android.xml". Located in your Hyperspin/Databases/Main Menu folder. This will allow for a specifically tailored Main Menu for your Hyperspin Android setup
Optional additional settings folder called /Settings_Android. Located in your Hyperspin directory and populated with your Android specific Main Menu.ini, Settings.ini and SYSTEMNAME.ini’s. This allows both Windows and Android launcher/rompaths to co-exist in separate .ini files within the same Hyperspin directory.
Some of your PC Themes and features may not be compatible with your Android setup so it may pay to build a specific Hyperspin folder for your Android setup. If you take this opportunity to trim unneeded files to save storage space it will likely mean some 3rd party tools (Don’s Filter list and Hypertools) may not function correctly.
Also adjustments to your Android set of settings will need to be done manually with a text editor
A file explorer installed on your Android device (ES File Explorer in this case) Optional: PC to make life easier Step 1 – App Installation
Note: The device you are using and your chosen Hyperspin folder location (local, sdcard, external HDD or NAS) will directly affect your steps and settings file values
All testing was done on my NVIDIA Shield TV Pro 3.2 Marshmallow 6.0, slight differences may be found on other devices
On your device open Google Play Store and search for Hyperspin
2. Install as any other Play Store app, accepting all permissions when prompted
You will now see the Hyperspin app in you devices menu
Step 2 – Build your Hyperspin directories
To function, Hyperspin pulls all data from an installation folder NOT included with the app installation. Without this directory you will see the below screen when trying to launch Hyperspin
Note: New users without a Hyperspin directory and not installing a PC version of Hyperspin please download
Hyperspin Android base pack
(Adjusted from BBB's Hyperspin 1.3.3 file)
Existing users please locate your PC Hyperspin directory and copy this to the root of your preferred storage device (USB, SD card, internal storage or NAS) see below details.
Decide on Storage Media & Location...
I will now show you how to install Hyperspin onto the internal storage of your Android device. You are free to place your Hyperspin directory on a different storage device, including SD cards, USB storage and Network Attached Storage (NAS), but please be aware Hyperspin will seek and prioritize booting 1st from
for your data.
Also note that on the Shield TV Pro /storage/Emulated/0 & /storage/sdcard are in fact the same location
If you will be using a NAS to store your Hyperspin directory, please be aware that there can only be one directory level between your devices /storage directory and your Hyperspin directory. For this to work, you will need to share your Hyperspin folder from your NAS device and the map that device to you Android device through its storage settings. It should then be seen in your devices /storage folder (I will cover this in detail in subsequent tutorials)
Example of correct NAS Path:- /storage/MYNAS/Hyperspin
Example of incorrect NAS Path:- /storage/MYNAS/SUBFOLDER/Hyperspin
My TEST path screenshot
Is my Local device directory /storage Is the name of my NAS Drive sdcard1
Next – Get a file explorer
I Installed ES File Explorer (ESFE) by searching ES in your Play Store app and install as any other.
Launch ESFE and navigate to the 1) Local then 2) Home - option. Place your Hyperspin folder here 3)
Note: For a HSA to work the ONLY required files/folders for an Android installation are as follows
/Emulators (optional ROM location structure for ease of setup)
Please now exit to your home screen and launch the Hyperspin App, to test everything is correct. Depending on your correct choice of Hyperspin directory you should now be greeted with the Hyperspin intro video and your Main Menu wheel of systems.
The base pack download will look similar to this example.
This is what you get with the default Hyperspin 1.3.3 version I have adjusted
Now you have completed the basic installation there are some settings that require adjusting and reviewing to enable games to be launched.
Also the per system/wheel settings are covered here