Jump to content

Honosuseri

Recommended Posts

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

 

Link to comment
Share on other sites

  • Replies 70
  • Created
  • Last Reply

Media is not my main concern. I already have an impressive collection but I need to do the renaming and audit it against the new xml. 

So doing the xml & uae files are my primary concern. I will then return to the media, focusing on wheel art first. I can live with missing some box, disk art and video snaps initially. 

My hope is that the new HDF collection becomes the gold standard, for everyone to use on all platforms. No disrespect to the Whdload creator as without those, there would be no HDF files! My preference is to emulate the Amiga on PC but also having the games on my Shield TV and Android phone, all sharing the same "game rom set" does make a lot of sense! 

Once these xml files are released, I'm hoping content creators will welcome the static naming. ECS and AGA versions of the same game, will share the same name. This will allow sharing of some artwork between them, making life easier. 

My free time is limited, so I need to prioritise what I do. In time, the talented content creators can do what they do best! 

Link to comment
Share on other sites

CD32 UPDATE... 

Spent most of the weekend looking over the CD32 and have made some good progress... I've had this wheel configured for a long time now BUT control issues kept me from testing it.

I want to thank Ransom1122, for the time he put into sussing the CD32 controls (whilst I was busy in Denmark servicing the family yacht). I had emailed him recently about these settings for the uae files BUT he didn't get back to me... He's a very busy guy! So I took matters into my own hands!

Uae4arm for some strange reason will NOT allow us to bind the CD32 blue button to our gamepad via the GUI. Big problem as some games (e.g Battle Chess) require you to press blue to load the game! The fix is to manually input the bindings into the uae file, figuring out the correct settings was not fun though! 

Having made my way through the CD32 wheel, I can say the controls do now work, CD32 blue is B on the STV pad. I came across a few problem games on the wheel BUT I have a feeling this is down to bad CD rips rather than the emulator itself. 

I'll further investigate these "problem games" to fix them and get this collection complete. Expect a CD32 showcase video relatively "soon" :)

Link to comment
Share on other sites

CD32 Showcase video!

Keep in mind this is still a work in progress. There are still a handful of problem games, at the end of the video you can see the Zool games have serious graphical glitches. The controls were my main concern, I've loaded up a few games like Battle Chess to show I can play games that require the CD32 blue button.

I'll do another video explaining my findings trying to fix these games at a later date...when I have some more free time.

 

Link to comment
Share on other sites

Having done some serious play testing on both the Shield TV and my Android phone. I have come across some problem games. Zool is a good example, with serious graphical glitches in game. Here's a video to show the problem and a workaround for now, until the emulator is updated to fix it... 

 

Link to comment
Share on other sites

  • 2 weeks later...

I hope you all enjoyed the Christmas Holiday. I've put up a video to keep you guys up to date with my Amiga Project.

Uae4arm the Amiga emulator for Android devices got an update on Xmas day. I also show off my "patchy" PC setup for the Amiga and try to explain why this system does need overhauling so desperately in Hyperspin
 

 

Link to comment
Share on other sites

7 hours ago, ransom1122 said:

@Honosuseri Merry Christmas & A Happy & Safe New Year to you and your family.......

On a side note would all whdload lha names renamed to something more "normal" work? Or is HDF the way forward? 

 

And you my friend :) 

HDF is the way forward to have one set to share across all systems, to emulate the Amiga. Of course the downside is needing uae files to match, as you're well aware.

The PC can load the lha files but on Android we can't use them directly. They need extracting out into folders and we know Horace the Spiders' bootloader was a bit hit and miss. On Android we need uae files either way, through hdf or using a bootloader and the game folders.

Link to comment
Share on other sites

  • 2 months later...
On 3/28/2019 at 7:54 PM, franciuipapi said:

i have  a complete HDF set with matching uae config files. When i run the uae files through Rocketlauncher i just get the workbench image. What am i doing wrong pls? thanks :)

Sorry for the lack of communication in my thread. I fractured both bones and the ankle of my right leg in January. I haven't been able to sit at the desk to use my PC. 

This thread is primarily for the Android version of Hyperspin, we can't use rocket launcher. So you're obviously doing this for PC. 

You don't have to use HDF files on PC. You can use zip and lha files of the games, this means you don't need uae files. 

I don't know what you're using.There's a good chance the uae files you have are for a different emulator such as Amiberry, uae4arm or Retro arch's p-uae core. Uae files are not universal so this is most likely your problem, unless you made the uae files yourself? 

For simplicity's sake you're probably better off using zip and lha game files, until I get around to doing a uae file collection for Winuae on PC and a separate set for Android. 

Link to comment
Share on other sites

  • 1 month later...

Thought I'd better post an update to the thread....So you know it's not been abandoned!

Yes my leg is still busted but I've been soldiering on, creating media to fill in what's missing for the Amiga. The emulators on Android are still in Limbo, if this carries on I'll just concentrate on getting the Amiga done for PC with static naming instead. Whichever android emulator "wins out", I'll cater to that when the time comes. 

I have heard from Ransom the HDF creator/collector recently. Said he's maybe a couple of months away from getting the updated set completed. Converting all the WHDLoad zips to HDF with some bonus perks built in. Once I have all these HDF files I can get to work, creating the new database files and renaming the media to match.

Link to comment
Share on other sites

  • 2 months later...

Little update. The latest version (1.0.3.0) of Uae4arm now works on the STV BUT it is still not listed as officially compatible. So as you won't find it on the Google Playstore to install for Android TV devices, I'll provide a link to the apk file I have extracted from my Nokia Android phone.

I only got the update pushed to my phone today and just got around to getting it side loaded on to the STV (I'd been side tracked with the recent changes to Retroarch). So my testing so far has obviously been limited, it does seem to behave better than the old "working" version BUT still doesn't exit gracefully back to Hyperspin on quitting sadly.

https://mega.nz/#!TYMQQKob!9pzwooQbkxVd-__mwmqtFWNF9JSR7D7rEgY8tqu31Vg

Link to comment
Share on other sites

3 minutes ago, rambo32 said:

Sweet, thank you!! Will give it a whirl

No worries, every time Lubomyr has pushed out an update I've tested it on the STV also.

There's still no support for CDTV, although many of the titles from that system will play on CD32 settings. It's looking more and more like Amiberry will be a better emulator WHEN it gets ported to Android, at the moment Uae4arm is still the best option we have.

Link to comment
Share on other sites

Well really appreciate all your efforts with Amiga and In general on this forums, I take a look daily. I am super impressed with what Freelancer is doing but I still have not made the jump, Im still an old school hyperspin guy 

Link to comment
Share on other sites

27 minutes ago, rambo32 said:

Well really appreciate all your efforts with Amiga and In general on this forums, I take a look daily. I am super impressed with what Freelancer is doing but I still have not made the jump, Im still an old school hyperspin guy 

I've heard Launchbox is also coming to Android which will probably give Freelancer some competition. Hyperspin on Android sadly is missing many features that the PC version has and other competing Frontends on Android for that matter (favourites anyone?)...still looks awesome when you get it setup though :)

I'm not really a fan of Launchbox on PC. "Pro" users will integrate it with Rocketlauncher anyway, so for me there's no real reason to "abandon" Hyperspin. I promise I'm still committed to doing the Amiga justice! Ransom told me recently he's done over 2000 HDF files for the new WHDload collection, with built in trainers to choose from the boot menu. I'll concentrate on PC first, create the extra Amiga wheels/databases and check the missing media, once I get hold of his collection. This gives time for the Amiga emulators on Android to pan out.

Thanks for the kinds words

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...