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

Recommended Posts

On 10/9/2019 at 6:06 AM, Honosuseri said:

MS-DOS is an utter pig, I didn't bother with it in Hyperspin on the STV. I use Magic Dosbox and load it through Kodi's main menu,

I've never managed to work out Magic Dosbox since sideloading it to shield. First problem I couldn't get a mouse cursor to appear using the shield controller, i got a mini usb keyboard to solve that issue but then found i couldnt load games from an external hdd. 

Share this post


Link to post
Share on other sites
4 hours ago, Gingerdilligaf said:

I've never managed to work out Magic Dosbox since sideloading it to shield. First problem I couldn't get a mouse cursor to appear using the shield controller, i got a mini usb keyboard to solve that issue but then found i couldnt load games from an external hdd. 

I have a 1TB SSHD adopted as internal storage to expand the 16GB, never tried doing stuff from external drives. I barely use MDB or play MS-DOS games on the STV. I'm not one of those people that wants to "brag" that they have 300+ wheels in Hyperspin. The wheels I have are stuff I want to play and they're done well.

I'd love to help you out but it would drag this thread off topic and to be honest I'm pretty busy with this Amiga project and PC VR.

Share this post


Link to post
Share on other sites

This is very exciting stuff. Thanks for all the hard work. Love the Amiga & looking forward to this beast set.

Share this post


Link to post
Share on other sites
24 minutes ago, PiperCalls said:

This is very exciting stuff. Thanks for all the hard work. Love the Amiga & looking forward to this beast set.

Thank you!

Just so you are aware. Ransom is also busy covering the Amiga for the Raspberry Pi with Amiberry, although I do know he's helping some other guys out with an Android Hyperspin project. He did ask me nicely if I'd consider teaming up with those guys again (as I frankly know more about the Amiga than they do) but I've refused. It's possible they may finish before me as they are just concentrating on using UAE4ARM.

I want to sort Amiga emulation on PC first. I'm going to have to tinker with some Rocketlauncher modules as well as sort and create media, although to my knowledge I have more Amiga media than anybody else. This gives the Amiberry team time to complete the Android port and then I can turn my attention to uae files for that and the media I've done for PC can be used on Android.

Share this post


Link to post
Share on other sites

You still holding your breath for Amiberry for Android? Really after all these years... ?

With no proof or any evidence the port to Android is possible. I've given up waiting. The dev is way to busy with supporting Amiberry on single board computers then to mess with an unfamiliar OS.

Uae4arm is the way to go forward on Android, and with any issues or hiccups, lubo is surely prepared to at least look at it and or solve it.

 

If or when Amiberry arrives on Android I'll then pay attention to it. Otherwise Ill spend my time elsewhere.

Share this post


Link to post
Share on other sites
12 hours ago, ransom1122 said:

You still holding your breath for Amiberry for Android? Really after all these years... ?

With no proof or any evidence the port to Android is possible. I've given up waiting. The dev is way to busy with supporting Amiberry on single board computers then to mess with an unfamiliar OS.

Uae4arm is the way to go forward on Android, and with any issues or hiccups, lubo is surely prepared to at least look at it and or solve it.

 

If or when Amiberry arrives on Android I'll then pay attention to it. Otherwise Ill spend my time elsewhere.

No I'm not holding my breath. My priority is to finally sort the Commodore Amiga out for Hyperspin! The best emulators (with cycle exact) are on PC and the Lion's share of Hyperspin users are PC based (because the PC version is superior). So that is now my focus and sorting the other Commodore computers that have been sorely neglected.

I'm well aware of the state of Android emulation (you know this). I don't think it was a coincidence that UAE4ARM started working again on Android TV, shortly after I sent the dev a crash log. I didn't see anyone else post one on github, I've done my fair share to help the Android side of things along.

There is already an Amiga set done for Android which was rushed and of poor quality. I'm not convinced the guys working on the new set using your updated hdf files will do it properly. No disrespect to them, the Amiga is a complicated system to emulate. I have my doubts they'll know the games are actually running as close to true speed as possible or know how to create a Workbench environment like I did for Android. I wish them luck with it, I do like seeing people excited about the Amiga which I do adore.

I know you're busy with the RPI, I'll focus on PC and will then turn to Android once that's complete. If Amiberry is still in Limbo come that time, I already have an impressive working set of uae files for UAE4ARM to use as a base to update. The media assets created for PC can be used on Android, I think I'm actually using my time wisely.

P.S

Thank you for the update about Rygar (AGA) that has now been ported to the Amiga (it's an awesome game). I'm sure PC users are excited to get a definitive Amiga set to add to their collection.

 

  • Super Like 1

Share this post


Link to post
Share on other sites

FYI.. I haven't turned my pi on ever since i released my last pi COLOSSAL 256gb Retro image months ago.

Android IMO is a better system to play with. Does far better in emulation and non gaming things.

As for advancing forward. I have a say in how amiga goes forward with HS, and yes, AGA and NON wheels will be implement. Optimized uae configs for each game etc etc. 

It looks like work on this will be doubled up from yourself and the "other side." It's a shame it was never worked "as a team" instead of divide and conquer approach.

Lucky for me, I have 4 other guys willing to help and advance amiga forward with HS and my new hdfs. So i dare say it wont take that long.

Share this post


Link to post
Share on other sites
39 minutes ago, ransom1122 said:

FYI.. I haven't turned my pi on ever since i released my last pi COLOSSAL 256gb Retro image months ago.

Android IMO is a better system to play with. Does far better in emulation and non gaming things.

As for advancing forward. I have a say in how amiga goes forward with HS, and yes, AGA and NON wheels will be implement. Optimized uae configs for each game etc etc. 

It looks like work on this will be doubled up from yourself and the "other side." It's a shame it was never worked "as a team" instead of divide and conquer approach.

Lucky for me, I have 4 other guys willing to help and advance amiga forward with HS and my new hdfs. So i dare say it wont take that long.

Well I have more faith that it will be well done then, if you aren't doing the RPI.

It's not a divide and conquer approach. The Amiga on PC needs sorting out, Rocket Launcher modules need adapting and of course the media sorting (which I've been chipping away at). I don't want to work with others and deal with egos, arguing why I want things done a certain way or teach people, for them to then want to branch off and go their own way.

I started this thread for my Amiga project. It's already helping others who want to do their own setups which is great. It makes no odds to me if people want to use the setup I will eventually release or another, as long as people are still enjoying the Amiga.

Share this post


Link to post
Share on other sites

Hi, i was just wondering if some could post an amiga ini file that uses uae4arm? There were files posted before but they are no longer available.

Edit its ok sorted it myself.

Share this post


Link to post
Share on other sites

Will you be kind enough to share your romset or even just .use files? I am having many headaches trying to get Amiga running on my Nvidea Shield with Hyperspin. UAE4ARM doesn't seem to like my .zip romset, and I can't find a full HDF set with the correct names. Why is Amiga so complicated!? All the other systems load in quite easily.

Share this post


Link to post
Share on other sites

Have u tried the new puae core??...u should because it plays cdtv, cd32, and hdf,adf, and whdload games...give it a try and has full controller support for cd32/cdtv and keyboard and mouse and joystick for amiga

Share this post


Link to post
Share on other sites
Will you be kind enough to share your romset or even just .use files? I am having many headaches trying to get Amiga running on my Nvidea Shield with Hyperspin. UAE4ARM doesn't seem to like my .zip romset, and I can't find a full HDF set with the correct names. Why is Amiga so complicated!? All the other systems load in quite easily.
The Amiga is so complicated because it isn't just a one size fits all system.

There are many many models, with differing memory, cpu configs. There's ocs, ecs, aga etc.. With games released for each. Amiga emulation as a whole is extremely complex and is not something for a beginner to easily pick up!

Then there is the complexity of different formats and ways to store games.. Firstly adf, which is simply a floppy disk image. Often these use cracks and as such a dodgy crack can fall over on different configs. There are then whdload installs, which are usually run from Workbench environment. These can be run as a hdf formst, which is basically a hard drive image, and is possibly the easiest way to get this done.

When everything is taken into consideration you can appreciate how complex this is.

I have been reading and catching up on this, and maybe it's time i got back into getting this running on my shield. I deffo managed to get a lot running a while ago, and right now i have been using arcbrowser as it is simpler to set up..

I might look into creating a pc tool specifically for Amiga hyperspin. A third Amiga project for me..
  • Super Like 2

Share this post


Link to post
Share on other sites

A Hyperspin tool would be great. I just am not having any luck. I need to find a good HDF romset I think. Or a way to convert these zips I have already.

Share this post


Link to post
Share on other sites

I've been trying to suss out Amiga emulation on Android for a long time and think I've finally got it sorted. I never owned an Amiga as a kid although I desperately wanted one. I've never used Hyperspin but I found this thread on Google and I thought it beginner friendly. Also the posted working version of uae4arm for the Shield was very handy (thanks Honosuseri). I just wanted to post my findings.

Initially I had numerous hdf files from another time when I tried and gave up. I didn't realise the ones for RetroArch and the Ransom ones weren't universally compatible. The Ransom ones wouldn't work in RetroArch (with PUAE) and the Retroarch hdf files weren't working in UAE4ARM (until I realised it needed a WhdLoad file as well). Also what was really causing me problems was if I tried to load the hdf from my sd card it wouldn't work at all. Again I realised that once I moved it to the internal storage and ran it from there I had no problem.

Basically I'm now wondering whether to use UAE4ARM or RetroArch? Would you guys have a recommendation? Bear in mind I'm not using HyperSpin. As for that maybe one day I'll take it on. What frightens me is the amount of time I'd end up losing to it!

Again thanks to Honosuseri for his Youtube vids and posting a link to a working UAE4ARM.

Share this post


Link to post
Share on other sites
On 2/29/2020 at 8:47 PM, VanZan said:

I've been trying to suss out Amiga emulation on Android for a long time and think I've finally got it sorted. I never owned an Amiga as a kid although I desperately wanted one. I've never used Hyperspin but I found this thread on Google and I thought it beginner friendly. Also the posted working version of uae4arm for the Shield was very handy (thanks Honosuseri). I just wanted to post my findings.

Initially I had numerous hdf files from another time when I tried and gave up. I didn't realise the ones for RetroArch and the Ransom ones weren't universally compatible. The Ransom ones wouldn't work in RetroArch (with PUAE) and the Retroarch hdf files weren't working in UAE4ARM (until I realised it needed a WhdLoad file as well). Also what was really causing me problems was if I tried to load the hdf from my sd card it wouldn't work at all. Again I realised that once I moved it to the internal storage and ran it from there I had no problem.

Basically I'm now wondering whether to use UAE4ARM or RetroArch? Would you guys have a recommendation? Bear in mind I'm not using HyperSpin. As for that maybe one day I'll take it on. What frightens me is the amount of time I'd end up losing to it!

Again thanks to Honosuseri for his Youtube vids and posting a link to a working UAE4ARM.

Sorry for the late reply, I haven't been on the forum much lately. I've been busy with PC VR with my Rift S, I got the old light gun games working with the touch controllers and launched through Hyperspin with Virtual Desktop. It's awesome but that's a story for another day as it's off topic! ;) No I haven't given up on the Amiga I did slog away at filling in the missing media for Hyperspin!

I'm actually incredibly impressed with what the guys have now done with the PUAE core on RetroArch. Yes it can now do all "Amiga systems" BUT what's most impressive is that it seems to do cycle exact emulation which UAE4ARM and Amiberry do not (last time I checked anyway). PUAE can also cope with zip files, lha (i.e Amiga zip files), hdf, adf, cue, iso (for CD32, CDTV obviously) etc. etc. It is quite fussy about what Amiga Kickstart roms you have though. Please do check the md5 checksum of your kickstarts to make sure they match and rename them as necessary, google it there are sites you can drop the file into and it will give you the md5. I'll link to the PUAE instructions page so you can see how they should be named and the md5 (https://github.com/libretro/libretro-uae).

I threw a handful of tricky games at Retroarch's PUAE with the lha file format. "It came from the desert" was a notorious game for not running at the correct speed on UAE4ARM, hence all that uae file nonsense to configure it to run acceptably. PUAE just ran it perfect first try, no uae file, just loading the lha file directly! Keep in mind I haven't tested every game as there are so bloody many of them, so yes some might need a uae file made. I'll investigate further when I can but yes I did try CD32 games too and they also played great!

What does all this mean for my project? Well I'm now potentially "free" of relying on Ransom's HDF files (which I'm incredibly grateful for all the work he put into and some people might want to still use them for the trainers/cheats) and quite possibly a metric **** tonne of uae files! My long term goal was to have one Amiga Romset for both PC and Android, since PUAE can do zip & lha, I can just use the original Retroplay files Ransom uses to make the HDF files. These Retroplay WHDLoad zips and lha packs get updated over time and their names change BUT I can just rename them to something more sensible so the Hyperspin media and database still matches. 

As you're new to the Amiga, you really should look into the EAB (English Amiga Board), they also have a file server for their members. It won't host Ransom's files as the HDF files include Workbench files which are copyrighted BUT browse the file server as it has lots of goodies for us Amiga lovers. As you're not a Hyperspin user I can recommend the Arc Browser frontend on Android, it will work on your Shield TV and an Android Phone. Yes it costs money but that single purchase covers any device using your google account. It's actively developed by Freelancer, he creates presets for systems and the emulators they use to make setup easier. It can scrape online to get the artwork for your games too, it's not as flashy as Hyperspin but it's incredibly good! I use both on my STV, HS is for show but AB really is more convenient as it supports voice search from the STV homescreen.

Hope this wall of text has helped you out. I'll return to the Amiga and Android when I can focus on it properly, I have some serious family issues to contend with at home currently. All the best with it VanZan

Share this post


Link to post
Share on other sites

Still suuuuuuuuper keen to have a fully functioning Amiga setup on my NVIDIA Hyperspin. How is this coming along?

Share this post


Link to post
Share on other sites
18 hours ago, therourke said:

Still suuuuuuuuper keen to have a fully functioning Amiga setup on my NVIDIA Hyperspin. How is this coming along?

Getting there, I have a lot going on at home with family and friends dying from Cancer. It's done when it's done, I'm giving no release date. The information I share does help others who want to tackle their own setups though. I know Diskmach is working on redoing the wheelart for the Amiga and doing an amazing job of it too!

Much of the delay was down to the emulator to move forward with on Android. I will now be proceeding with the PUAE core and RetroArch, I explained why in a previous post. I have abandoned Ransom's HDF collection, I specifically told him we need static naming BUT he keeps changing the names. I wish him well with his projects BUT this just goes to show why I didn't want to work with and be dependant on others for my project. HDF files are also larger in size than LHA files that's just how it is. Ransom does put cheats and trainers into his files if you want that option, he has made unofficial collections (e.g Batman) which I deem unnecessary and a "waste of space". I have renamed the Retroplay WHDLoad LHA files, how they are named helps the PUAE core load them automatically and give other frontends a helping hand in scraping online for media and metadata.

If you are desperate to have the Amiga on your STV. You can always focus on doing your favourite games, say 20-30 of them rather than the full 3000+. It's not difficult to do an Amiga.xml database file and rename the latest LHA files and media for a few games. You don't need to worry about uae files with RetroArch, providing the game name is suitable. If it's an AGA game have (AGA) in the title, if it needs Fast RAM have (FAST) in the title. The lha files will have "_aga" or "_fast" in their name anyway to help you know.

Share this post


Link to post
Share on other sites

Thanks for the update! 

I have found a pretty decent build, and managed to get it to work with retroarch. Where can I download Diskmach's build? Does it include videos? Not had luck finding it. If you have a link to the latest art and videos I'd really appreciate it.

Share this post


Link to post
Share on other sites
4 hours ago, therourke said:

Thanks for the update! 

I have found a pretty decent build, and managed to get it to work with retroarch. Where can I download Diskmach's build? Does it include videos? Not had luck finding it. If you have a link to the latest art and videos I'd really appreciate it.

I don't use "Hyperspin builds" releasing them or linking to them is against forum rules. When Discmach is done I'm sure his artwork will be available from here on the Hyperspin website, videos are from emumovies

Share this post


Link to post
Share on other sites
On 7/9/2020 at 9:20 AM, therourke said:

Thanks for the update! 

I have found a pretty decent build, and managed to get it to work with retroarch. Where can I download Diskmach's build? Does it include videos? Not had luck finding it. If you have a link to the latest art and videos I'd really appreciate it.

Diskmach is a content creator. He remakes/adjusts artwork to make it as high quality and authentic as possible. Also reworking/updating databases to the original hyperspin database guidance/naming.

He has been working off/on on Amiga wheel art for a year or 2 and releases his work here.

https://diskmach.wordpress.com

 

3rd party builds that include games are not discussed here as it's against the rules.

Most videos can be downloaded from emumovies.com but depending on your database will depend on how well you fair. Naming differences are a major issue with Amiga.

I tried and came up short on Amiga so left it to others that have more passion for it.

  • Like 2

Share this post


Link to post
Share on other sites

I have a fully working build for Commodore Amiga now. It took me a good while to get it up and running (on Retroarch, NVIDEA Shield).

I made a tutorial, so people don't have to repeat my mistakes, which you can find here.

  • Like 1

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 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 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.8.8) newest stable version at time of posting (http://buildbot.libretro.com/stable/1.8.8/android/)
    • 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.
    • 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.
       
×
×
  • Create New...