Jump to content
thatman84

Top features Poll

Top Missing Features  

13 members have voted

  1. 1. Top Missing Features from PC Version

    • Collections (launch multiple emulators from one wheel)
      9
    • Favourites/Genre (anyway to customise a full set without duplicating media)
      3
    • Horizontal Main/System wheels
      1
    • Other (please comment)
      0
  2. 2. Extra Features (over and above PC)

    • Default System Media to save space (default video, wheel, box, cart)
      5
    • Fix Libretro intent to allow custom CONFIGFILE path
      8


Recommended Posts

I love hyperspin Android and been using it for sometime now.

Everything else can be worked around without much hassle but there's a couple of issues that really impact the browsing experience for me.

1. Launching multiple emulators in one wheel is my top one

i dream of adding collections

2. Next is some way to have a favourites list without duplicating all my media

3. The holy grail is fixing the libretro intent so we can customise the CONFIGFILE path per system wheel

Share this post


Link to post
Share on other sites

Actually, I'd say "All of the above". But I guess it needs prioritizing.

One of the things, I would put into the "Other" section: Has somebody looked into the possibility of using HTML5 instead of Flash? I'm no expert here, but I think HTML5 libraries might be more readily availble for Android than manually recoding an swf library. At least, that was what I read out of the Android Issues thread, you had to do the decoding yourself. Correct me, if I'm wrong there. Just wondering, if this is a viable option.

Share this post


Link to post
Share on other sites

I would like to see the genres added to the android version so we do not have to duplicate Database / media / settings files. This can create a lot of duplication especially in the case of MAME !!!!

Thanks 

  • Upvote 2

Share this post


Link to post
Share on other sites
On 5/22/2017 at 2:23 AM, EyMannMachHin said:

One of the things, I would put into the "Other" section: Has somebody looked into the possibility of using HTML5 instead of Flash? I'm no expert here, but I think HTML5 libraries might be more readily availble for Android than manually recoding an swf library. At least, that was what I read out of the Android Issues thread, you had to do the decoding yourself. Correct me, if I'm wrong there. Just wondering, if this is a viable option.

Could you point me in the direction where I would find information on how to do that? Several of the mario themes have SWF files that will crash the nvidia shield.

Share this post


Link to post
Share on other sites

U can extract the images of the flash file and then join them 2gether via photoshop to use it as a png image for use in themes on android ....thatman has linked the tutorial on it....its a hit or miss with swf and android so I just go with themes all in png format....pain the azz cause I gotta go thru each one and change it from swf to png but worth it at the end for a nicer look

Share this post


Link to post
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

  • Similar Content

    • By Honosuseri
      I realise there is already a thread for the Commodore Amiga in the Android section. I should know, as of late I've essentially taken it over! It's one of the most viewed threads in the Android section, so clearly many of you adore the Amiga as much as I do. 
      That thread has become quite long and it's quite confusing with people choosing to emulate the Amiga in different ways. I decided it would be best to start my own thread, streamlining it to show the best way to get this done. As I do have a "proof of concept" setup working! 
      This project I've taken on is a mammoth undertaking, as the Amiga is quite a complicated system to do. I'll try to explain why and how I've decided to proceed, keeping you guys up to speed with my progress here. 
      The first real issue is the naming that Hyperspin has been using for some time now. It's based from the Whdload zip file names, which was a logical choice BUT the problem is these zip names keep changing over time as they get updated. This throws the database entries and all media assets out of whack. It's my belief that this naming is what is really holding us back doing the Amiga justice.
      Second problem for us Android users anyway, is that we can't use the zip files directly with an emulator. They needed to be extracted out and we used a bootloader to patch the files for the emulator and launch the games. All seemed well and good until I started testing games and found many wouldn't work. Very confusing as the same game files worked fine from a workbench environment I'd set up, with it's own bootloader I added in. I suspected it was the "ultimate amiga" bootloader for the Hyperspin wheel at fault, which proved to be correct. 
      So the best way to launch these Amiga games from the Hyperspin wheel, is to actually use HDF versions of the games. This removes the need for the bootloader. I decided to keep the game folders extracted from the whdload zip files. Continuing to use these with the workbench (Amiga's OS) hdf I created. Having this is a nice nostalgic nod, I'm sure genuine Amiga fans will appreciate. 
      Unfortunately we can't just point the emulator to these hdf files, it's not that simple. Each game requires a config file that points to where the particular hdf game file is, what kick-start (i.e Bios) to use, video settings, control bindings etc. These files are known as uae files, as that is the extension we tell Hyperspin to look for. We trick it into thinking these uae's are the actual "game Roms".
      Sadly uae files aren't universal between emulators. So choosing the right emulator to begin with is important. Many people had chosen to use RetroArch. Which can't do the CD32, so I'll strike it off for that reason alone (although there are other reasons). I spent a long time waiting on Amiberry to be ported to Android but the devs haven't delivered. I'm not waiting any longer, so I'm continuing to proceed with Uae4arm. 
      As I write this, the latest version of Uae4arm crashes on Android TV (i.e Shield TV) but does run fine on Android phones. The devs are aware and trying to resolve this. There is an older apk version we can install for now, which does work. Another slight annoyance is that Uae4arm is quite fussy about how the uae files are named. They can NOT have special characters in them (e.g a space) or the emulator won't launch them!
      My next complaint was that Hyperspin has "rules" about what games should be included in the xml database file. I do NOT agree with these "guidelines". I want a definitive collection of Amiga games. 
      I've decided to branch the Amiga out into different wheels, ECS, AGA and CD32. As an analogy think of Sega's Megadrive and it's hardware addons. Megadrive=ECS, Sega32X=AGA (better graphics chipset on later Amigas) and finally the MegaCD=CD32 (better audio track and FMV).
      There is a "HDF game set" floating around. However... I got to know the creator, from doing videos on my proof of concept setup. I've persuaded him to rename the files to something more sensible, that should help other frontends scrape for metadata and artwork. These names will not change over time as he updates the collection. He does release notes, so this info can be used to keep the xml database file up to date. Currently he's overhauling the hdf files so they take up less storage and even adding cheat and trainer options to the loading splash screen....very cool stuff!
      I'm working on creating missing artwork (wheel, 3D box, diskette and video snaps), keeping busy until this new hdf collection is complete. Then I can start creating the uae files needed. This will be laborious, as Uae4arm doesn't do cycle exact emulation. I need to make sure each game is configured correctly to run at the proper speed, I'll also bind commonly needed keyboard keys to the gamepad on a per game basis.
      If you're confused, that's OK! It should all make sense, once I get around to uploading some more videos. Yes I will make my assets available to you all (minus the games obviously due to Hyperspin rules), once I'm happy with the collection.
       
       
    • By thatman84
      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.
      https://play.google.com/apps/testing/atua.anddev.uae4arm
      Link above taken from the English Amiga Board and the post below
      http://eab.abime.net/showpost.php?p=1158186&postcount=349
       
      Step 2 - Install Kickstarts
      WIP
       
      Database taken from this thread post
       
      More to follow
       
      Amiberry Android progress threads
      https://github.com/midwan/amiberry/issues/206
      https://github.com/midwan/amiberry/issues/241
    • By thatman84
      Hyperspin Android ScummVM with RetroArch
      Credits
      JLeaver
      Norkusa
      reznnate
      badhemi
      sting
      honosuseri
      sanchezmike01
      aftermath17
      Pouteur
      krater9
       
      What is it?
      ScummVM is a program which allows you to run certain classic graphical point-and-click adventure games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the games, allowing you to play them on systems for which they were never designed!
      Assets and Links
      Latest ScummVM release at time of posting Dec 17, 2017: ScummVM 2.0.
      Diskmach Updated Database ScummVM 2.1
      Latest HyperSpin database ScummVM 1.8

      Working RetroArch core at time of posting scummvm 2.0.0 93d1ca1
      Location of current core
       
      How to setup...
      Grab these setup files as they will be needed.
      (Includes the Android XML and "Official" XML databases)
      Follow this guide to set up RetroArch ScummVM core directly Get your games and place them in folders named after this spreadsheet OR download the above setup files and create folders for them (with help of the below guide) Follow this guide to setup the folder structure for Hyperspin Android "folder trick" Use the below ini file settings for reference and add the system to your Hyperspin wheel as any other exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
      romextension=scummvm
      parameters=cores/scummvm_libretro_android.so
      Run Hypersync with the NON android xml as its not compatible with sync.
      The progress sheet below was adopted on the RetroArch documentaion and holds all my findings. I did duplicate 1 game to aid with android setup
      I created a "simon" folder for the Simon the Sorcerer's Puzzle Pack as all the games are in one folder.
       

      Backup of Working Core
      scummvm_libretro_android.so.zip
      Helpful Links
      https://github.com/scummvm/scummvm/tree/master/dists/engine-data
      https://www.scummvm.org/
      https://www.scummvm.org/compatibility/2.0.0/
      http://wiki.scummvm.org/index.php/Datafiles
×