Jump to content
reznnate

KNOWN ISSUES: Hyperspin (for Android)

Recommended Posts

z7jPgNL.jpg?1  Hyperspin (for Android) 

Updated 3/18/2017

New Issues

 

Known Issues - 6/10/2015

  • SWF
    • Missing swf sound
    • Slow decode speed when loading jpegs with alpha channel  (Primal Rage, King of Monsters)
    • Incorrect animation speed
      • Boot Hill, Bomb Jack, Ironman ISSOTP, Ninja Gaiden, Red Baron, etc.
    • Rendering clipped by movie bounds, wrong position
      • 1943, Enduro Race, Fever SOS, Hippodrome,  Jail Break, Jungle Hunt, Red Baron, Ninja Gaiden, SAR, Splatterhouse, Super SF2T (world), Tondemo Crisis, Wargods, etc.
    • Crashes
      • Crazy Kong, Heavy Barrel, Super Mario themes (NES/SNES), Sexy Parodius
    • Incorrect animation looping point
      • Assault, Jumping Jack, Life Force,  Metal Slug, Mighty Pang, Millipede,, Konami's Ping Pong, Rabbit Punch, R-Type, Salamander, etc.
    • Missing focal gradient support
    • Missing blend modes (corruption)
      • Galaxy Force 2, King of the Monsters, Lock-On, Night Driver, Return of Invaders, Super Bomberman2 (SNES), Windjammers
  • ANIMATIONS
    • Not yet implemented "type" animations
      • Arc Grow, Arc Shrink
      • Blur
      • Bounce, Bounce Around 3D, Bounce Random
      • Chase
      • Elastic, Elastic Bounce
      • Flag
      • Flip
      • Grow Blur, Grow Bounce
      • Pendulum
      • Pixelate, Pixelate Zoom Out
      • Rain Float
      • Scroll
      • Stripes, Stripes 2
      • Strobe
    • Not yet implemented "rest" animations
      • Squeeze
  • OTHER theme issues
    • bshape="round" unsupported
      • 1on1gov, battletoads, etc.
    • Rotation along the y-axis not perspective correct
    • Particle layer not yet implemented
  • VIDEO
    • Delay before looping on some videos
    • Potential audio corruption/clipping with video playback
    • At least one transition video MUST be copied in the frontend/video/transitions folder
  • WHEEL (features not yet implemented)
    • Missing up/down scrolling animation
    • Missing left/right skipping animation
    • Missing sound effects
    • Missing left/center wheel position
    • Missing text_stroke_size, text_stroke_color, text_color3, color_ratio
    • Crash when loading an empty wheel
    • Sub-wheel, wheel layout parameters
    • Horizontal mode
  • SPECIAL ART
    • Missing special art switching animations
  • Other missing features
    • Favorites, Genres
    • Widescreen mode
    • Render 3D models
    • Touch-screen input
    • Additional settings and configuration hook-up
    • Additional support for more Android devices
  • Upvote 1

Share this post


Link to post
Share on other sites

I need to get Matt and Rondar to chime in, a lot of there flash animated themes causes problems for Android i see

Share this post


Link to post
Share on other sites

Indeed, there is a substantial amount of complexity around playing back .swf without relying on Adobe's Flash player.

After a year of work on this, most of the .swf issues I mention are bugs we've identified and haven't had a chance to root-cause and fix yet.

It's assumed with time and effort, most issues can be fixed but the issues that are still outstanding are likely to be tricky.

 

If you, Matt, or Rondar can shed light on ideas about special modes or features that make those .swf's different from others, that would be very helpful.

The few .remaining swf's causing a crash are the biggest worry and our theory is they might involve actionscript.

For the .swf's that have miscalculated bounding box or position, perhaps there are additional parameters in the source .swf that our parser doesn't understand yet.

 

So, if modified .swf's are possible and can address the problem soon, that would be _awesome_.   That said, many of the problematic .swf's are gorgeous so would really like to see them work and not be degraded in any way.

  • Upvote 1

Share this post


Link to post
Share on other sites

So the coder working on the OpenGL-accelerated flash renderer engine painstakingly looked through all crashing swfs above and they all have one thing in common.  They are using “Generic Vector” types. They are undocumented in the Actionscript Virtual Machine 2 (AVM2) spec and are not supported in Hyperspin for Android.    It may be possible to add them eventually but it's unlikely to happen soon.

 

So feedback to authors of crashing swfs can modify their as3 code to avoid “Generic Vector” types.   I have no experience with actionscript, but I believe they are of the form:

 

Vector.<type>

 

Also, they should also avoid “Runtime Qualified (Late) Names” as those aren’t supported (yet) either. According to the AVM2 spec, they are of the form:

 

var ns = getANamespace();

x = ns::r;

 

Or…

 

var x = getAName();

var ns = getANamespace();

w = ns::[x];

 

 

Reznnate

Share this post


Link to post
Share on other sites

Of the themes you've listed that I've done the one thing they have in common is that they use embedded graphic or movie elements within the main time line.  To use Tondemo Crisis as an example, the head is animated separately when the smoke comes out (after the zoom has happened) and then that entire element is animated rotated left/right on the main time line.

 

There's no action script in any of mine (other than stop, gotoAndPlay).

 

If you want me to send you the source Flash of any of these, then PM me.

 

EDIT : Yesterday's effort, Pulsar, has embedded graphics elements and significant chunks of masking using native Flash shapes.  Might be worth checking that out and going with that source as a test instead?

Share this post


Link to post
Share on other sites

>> EDIT : Yesterday's effort, Pulsar, has embedded graphics elements and significant chunks of masking using native Flash shapes.  Might be worth checking that out and going with that source as a test instead?

 

It looks good -- no issues.

Subzero sent a new aburner theme and it worked fine (and looks gorgeous!) as well.

  • Upvote 1

Share this post


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

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

      ***UAE4ARM BETA APK LINK***

      https://mega.nz/#!TYMQQKob!9pzwooQbkxVd-__mwmqtFWNF9JSR7D7rEgY8tqu31Vg
       
    • By Honosuseri
      Retroarch (Google Play) has updated itself to the latest version 1.7.8 and it seems to have broken compatibility with Hyperspin 😕

      Having done some quick reading (https://www.libretro.com/index.php/retroarch-1-7-8-important-changes-for-people-using-the-google-play-build/) it seems under the "infinite wisdom" of Google. They're forced to build in both 32 and 64bit support for the app, so the device (Shield TV) will default to using the 64bit version as it is a 64bit device. I'm not entirely sure what's gone wrong as I haven't had time to delve further into it, although I know ZeroJay did a modded Hyperspin apk for 64bit support (that doesn't work either). Just wanted to warn users so they don't update and have any aggro.

      You can still side load 32bit versions of Retroarch, I'll do that later and test. I'm actually quite excited about some of the features that have now come in the latest version.

      ***EDIT***

      The retroarch_ra32.apk (v1.7.8) changes the path (typical). So it's now "exe=com.retroarch32/com.retroarch.browser.retroactivity.RetroActivityFuture". Hyperspin doesn't like this and it misbehaves as it did trying to load the original 64bit Google play version, which is why ZeroJay did the modified Hyperspin apk.
       
    • By thatman84
      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".
      Games
      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)
       
      Note:-
      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)
      EDIT:- USA version is working with RetroArch core version 0.2.97.44. Make sure you have the correct RomSet version
      Setup Steps...
      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/
      exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
      romextension=zip
      parameters=cores/fbalpha_libretro_android.so
       
      PLAY SOME STREET FIGHTER .......................
       
      Extra Notes:-
      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)
      Hyperspin-CPS3Android.zip
       
       
    • By Honosuseri
      As we celebrate 25 years of DOOM! John Romero has brought us SIGIL, an unofficial 5th chapter to the original game. So as Retroarch's Prboom core has now been updated to support it...figured I should really add it to my Doom Classics wheel...
      Threw together a Sigil theme, wheel art and video snap. I was pleasantly surprised, that the prboom core now played the midi music natively. Doom 1&2 originally required me to add the music tracks as mp3 files. 
    • 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
      https://drive.google.com/folderview?id=1-8Ofa_GrAdnQ22nf7W7QYVeQoKBQxA_-
      (I am in NO way competent with artwork resolutions but my method works and looks good to me)
      Why...
      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
       
           SCREENSHOT
      3.     
       

       

             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)
       
      SCREENSHOT2
             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)
       
       
      SCREENSHOT3
             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)
      8.   UNTICK MAINTAIN ASPECT RATIO
       
             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
×
×
  • Create New...