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

Recommended Posts

Well deserved, I always look forward to your posts. Can’t wait so see what you do with Ransoms HDF files, you guys have put in a hell of a lot of work already, can’t wait to see the results 

Share this post


Link to post
Share on other sites
10 hours ago, rambo32 said:

Well deserved, I always look forward to your posts. Can’t wait so see what you do with Ransoms HDF files, you guys have put in a hell of a lot of work already, can’t wait to see the results 

I should probably do an update video with all the recent developments. In a nutshell though...

I will divide Amiga into ECS (A500) and AGA (A1200) wheels. Create the new statically named database xml files and check the media situation against that. Ransom does an insane collection of Amiga stuff including Demo disks. It might be cool to do a dedicated wheel for them, show the Magazine cover if possible as they won't have a box....we'll see what can be done. WHDload doesn't cover all Amiga games, so maybe a wheel for adf files could be done down the line too

  • Upvote 1

Share this post


Link to post
Share on other sites

I will get around to doing an update video talking through what's been happening. Until then I thought I'd show of my current selection of Commodore Classics with HyperSpeech, to give us a little history lesson on these select systems...
 

 

Share this post


Link to post
Share on other sites

Lubomyr has been pushing out more updates to Uae4arm (beta version) to fix some bugs and crashes. It's still not listed as officially compatible on Android TV devices. When he calms down pushing out updates I'll extract the apk and make the newer build available to you all.

He's been informed that the emulator is now working again on the STV. Hopefully he'll start listing it as compatible in the Play Store again soon, so we don't have to keep sideloading.

Share this post


Link to post
Share on other sites

Hey Honosuseri

Do you have a UAE-config file that can launch hdf-files with Arc browser on the Nvidia shield?

Uae4arm crashes when I try to launch it with Arc browser, just want to see if there is any setting I can change to prevent it from crashing. I do have the beta version of Uae4arm.

Share this post


Link to post
Share on other sites
On 9/10/2019 at 9:14 PM, Kemppe said:

Hey Honosuseri

Do you have a UAE-config file that can launch hdf-files with Arc browser on the Nvidia shield?

Uae4arm crashes when I try to launch it with Arc browser, just want to see if there is any setting I can change to prevent it from crashing. I do have the beta version of Uae4arm.

I do have a complete set BUT it wouldn't really help, you would need an identical setup to me. i.e Kickstart roms, uae and hdf files in specific folders, all as I have them named as each uae file is referencing these files and their locations.

Create a uae file using the UAE4ARM's GUI and make sure the hdf game is loading and playing correctly from with in the emulator. It's VERY important that the uae file name you save has NO SPACES in it! This is the most common mistake people make and is most likely why Arc Browser can't load your games. The WHDLoad file names use underscores (_) in them instead of space, which will work if you use those in your uae file names. However Arc Browser might have trouble scraping from those names.

Hope that helps, if you're still struggling post back.

Share this post


Link to post
Share on other sites

Long over due update video!

Latest version of UAE4ARM is now working again on the STV! More info about the project to let you guys know what's going on AND teasers for some other projects I have planned for the new year ahead
 

 

  • Like 1
  • Super Like 1

Share this post


Link to post
Share on other sites
Quote

"Hahaha lol I just heard the 1st part of your YT clip. lol
FYI HDF progress, 2,810 done and about 900 to go. I am hoping to wrap it up by the end of the month. If not it wouldn't be too far from it.

Straight from the Horse's mouth! Ransom let me know exactly what stage he's at converting the Amiga WHDLoad collection. Looks like I'll be able to crack on with the PC side of things pretty soon :) Once that's done I can see what state Android emulation is in and turn my attention to that.

If you thought Ransom was being "lazy" or "slacking off". Do be aware both of us have been assisting Inolen, the developer of the Sega Dreamcast emulator called Redream. I pushed for launch intent to be implemented and tested it, as well as looking for bugs to be squished. So if you're enjoying using that emulator on your Shield TV with Hyperspin, we both had a little something to do with it. Rest assured Amiga is still a priority though ;)

 

Share this post


Link to post
Share on other sites

Hey Honosuseri, thank you for your answer. Managed to load my hdf with arcbrowser now :)

Where do you find Ransoms hdf-files? I've found a huge torrent for raspberry pie on the arcadepunks website but the file is broken for me when trying go mount it (and I really don't need 128gb worth of files). World be nice to just select the games I want to play.

I could make the files myself but it would be a real time saver to download them if they already are done and I only have to create config-files for them.

Share this post


Link to post
Share on other sites
2 hours ago, Kemppe said:

Hey Honosuseri, thank you for your answer. Managed to load my hdf with arcbrowser now :)

Where do you find Ransoms hdf-files? I've found a huge torrent for raspberry pie on the arcadepunks website but the file is broken for me when trying go mount it (and I really don't need 128gb worth of files). World be nice to just select the games I want to play.

I could make the files myself but it would be a real time saver to download them if they already are done and I only have to create config-files for them.

Glad to hear you're up and going now. FYI if you want to thank us that's what the little mushroom is for on the posts we make ;)

I can't answer that question, not being difficult it's forum rules stopping me. Funnily enough I said to Ransom ages ago that he should do a small base image and the games as separate "packs". He said 128GB cards are cheap and that was that lol

You're better off waiting for him to complete the new HDF collection now, that I mentioned in the previous post. I'm sure he'll do an image for the RPI, although he is working on an Android setup as well as he's an STV owner. He'll finish that before you start from scratch :)

  • Like 1

Share this post


Link to post
Share on other sites

Small update....

Message from Ransom, my friend down under in the early hours of the morning. Out of the 3,500 HDF files, he has just FIFTY of them left to make! He'll then do a file compare to the WHDLoad collection and make sure no games are missing from the collection. It should total around 10GB. He apologised for how long this has taken, as he got slightly side tracked with other things. Honestly it's an insane amount of work he's put into this project. For his own sanity it probably was wise to turn to other projects occasionally....they say a change is as good as a rest ;)

I'm looking forward to getting my hands on the collection relatively soon. Creating the new Databases for AGA and ECS/OCS games, then moving on to check missing media that needs to be sorted out.

  • Like 1
  • Super Like 2

Share this post


Link to post
Share on other sites
2 hours ago, gigapig said:

You've made me excited as well. :sword:

I'm always glad to hear people are still interested in the Amiga and this project.

Obviously I can't say too much about the "HDF game pack" because of forum rules. Although the last collection totaled ~8GB iirc and some of that was "fluff". Ransom is hardcore and included HDF conversions of CD32 and CDTV titles last time round, I expect he'll have done it again for "reasons". It doesn't make much sense for us to use these, as they lack the FMV and the audio. We already use the proper CD rips for those systems anyway and they're both in a pretty good state, as far as the database and media goes.

Share this post


Link to post
Share on other sites

I'm also following this topic as Amiga is one of the 3 systems I have real problems emulating on a shield. I've kind of given up on Ms-dos & scummvm but still hoping to find an amiga solution

Share this post


Link to post
Share on other sites
50 minutes ago, Gingerdilligaf said:

I'm also following this topic as Amiga is one of the 3 systems I have real problems emulating on a shield. I've kind of given up on Ms-dos & scummvm but still hoping to find an amiga solution

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, MDB can have box art and that's good enough for me. ScummVM I sussed out ages ago with Retroarch, the official ScummVM app doesn't work with frontends. Thatman84 didn't care about it but wrote up a guide on here once I told him how it's done. It's a bit fiddly to do but he wrote up a pretty comprehensive guide, the video I had done is now gone unfortunately.

Got a message from Ransom earlier this morning. The HDF collection is now complete, he was checking the games against WHDLoad as we spoke. He did hit me with a slight bombshell though, he has another 1,500 HDF files! 3,500 for WHDLoad, the rest are mostly official Amiga games that are not in the WHDLoad collection with some Homebrew titles thrown in. These extra official Amiga titles will definitely be missing artwork HOWEVER it's awesome to have more to add to the Amiga database. ADF versions of the games can be flaky at best, I have no doubt the HDF versions Ransom has done will work great!

SO...I have even more work to do now BUT the Amiga is finally getting the love it deserves, no matter which platform we choose to emulate it on :)

  • Like 1

Share this post


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

Wassup guys ;)

Saw the Doc today. He said I'm recovering well from what's essentially a life changing injury both physically and psychologically. I can return to work now in a limited capacity, typical we should get to a point where I can really crack on with this project when I now have less free time on my hands ?

I do now have the complete collection of HDF files. There are more titles added to the WHDLoad set, I'll deal with those first and then turn my attention to the "non WHDLoad generic game" set. 

Share this post


Link to post
Share on other sites

Correct.. There are a lot more games in folder 1 which is what youve mainly been waiting for ;) all the rest are extra games.

  • Like 1

Share this post


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

Correct.. There are a lot more folder 1 is your folder you've mainly been waiting for ;) all the rest are extra games.

I noticed very quickly Barbarian + was in there. A HD remake if you will of Death Sword/Barbarian which was awesome to see.

The way you have them named is "static", so still named as your last collection which is great! It's also very easy for me to divide them now as ECS, AGA and Demos rather than having everything stuffed into one wheel. Won't take long for me to do the databases, it's sorting and creating the media which will take the most time. Thanks again for the INSANE amount of work you've put into this collection for the Amiga community!

Share this post


Link to post
Share on other sites

I had all this in the back of my mind to make the HDFs universal friendly.

Yes barbarian + is there, dam too easy game finish it in under 5 minutes lol.

Your welcome mate..

Share this post


Link to post
Share on other sites

As far as msdos goes...its best to load them via conf files....basically the conf file has all the settings and what will be the c drive and what will be the d drive if applicable  for cd based games...they also need to be on internal drive as I had errors loading from my hdd....scummvm is a bit tricky and needs subfolders...basically  each subfolder will hold the game plus a .scummvm  txt file inside which is what u will use to launch the game...the xml must also reflect the subfolders (I have the notepad++ code to reflect the subfolders)....amiga u can use uae4arm or puae core in retroarch...myself and ransome have tested alot of games  and all seem to load good and puae has on board keyboard or u can use a bluetooth keyboard...keyboard  is also good on scummvm and msdos.....

Share this post


Link to post
Share on other sites
On 10/11/2019 at 7:51 AM, sanchezmike01 said:

As far as msdos goes...its best to load them via conf files....basically the conf file has all the settings and what will be the c drive and what will be the d drive if applicable  for cd based games...they also need to be on internal drive as I had errors loading from my hdd....scummvm is a bit tricky and needs subfolders...basically  each subfolder will hold the game plus a .scummvm  txt file inside which is what u will use to launch the game...the xml must also reflect the subfolders (I have the notepad++ code to reflect the subfolders)....amiga u can use uae4arm or puae core in retroarch...myself and ransome have tested alot of games  and all seem to load good and puae has on board keyboard or u can use a bluetooth keyboard...keyboard  is also good on scummvm and msdos.....

Dude you really need to learn to format your posts, nobody likes reading walls of text (just a friendly bit of advice).

1. It's a shame you won't release the config files you made for MS-DOS for the community, if you have I've not seen them. It would help others, personally I'm not bothered about adding the wheel to my STV or I'd do it myself.

2. ScummVM is already written up as I've stated, including the knock on effect to the media folders you neglected to mention.

3. Puae core last I saw, was either set to be an A500 or A1200. You had to manually toggle between the two and restart. Ideally it would have cycle exact emulation so we could just set it and forget it as an A1200 but we couldn't. Games can play but be at the wrong speed, the uae file does NOT configure the type of Amiga it is like the UAE4ARM files do. It also doesn't do the CD based Amiga systems. I know you sunk time into it but you backed the wrong horse.

4. UAE4ARM is now in a better state BUT Amiberry is being ported and will frankly be a better option once done. It will allow spaces in the uae files which means those files will scrape better with other frontends like Arc Browser. I'll sort the Amiga for PC first and those assets will then be useful for Android. I'm not wasting time doing another batch of uae files for UAE4ARM when they won't be compatible with Amiberry.

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
      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.9.0) newest stable version at time of posting (https://buildbot.libretro.com/stable/1.9.0/android/)
    • By iamthamiz
      Hi Guys if your trying to set up M64plus FZ on android this is what i did to get my one up and running with NVida Sheild TV
       
      exe=org.mupen64plusae.v3.fzurita/paulscode.android.mupen64plusae.SplashActivity
      parameters=
      romextension= n64,z64,zip,v64
      searchsubfolders=false
       
    • 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 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.
×
×
  • Create New...