Jump to content
Site is currently back up for stability test, we think we have isolated the issue. If the site starts crashing again we will take it offline to continue repairs ×

Honosuseri

User
  • Content Count

    799
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Honosuseri

  1. It's the special artwork e.g Hyperspin/Media/Main Menu/Images/Special. Open HyperHQ. Choose the Wheel Settings tab and select Main Menu (or whatever system) in the drop down tab. Select Special Art and you can either enable or disable them, even adjust their X and Y positions.
  2. 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...
  3. The 64bit version does fix the Atari 5200 system if iirc, other than that there's no real need to switch from the 32bit currently. I would appreciate it if ZeroJay could knock us together a custom HS apk to strictly use just the nightly 32bit 1.7.8 version (https://buildbot.libretro.com/nightly/android/RetroArch_ra32.apk), if and when he has the free time of course (my free time is also scarce). RA 1.7.8 has some cool features like AI text to speech translation, which would be awesome for the many Jap games we have across systems.
  4. 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
  5. 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
  6. I need to look into it further. It's possible my STV put the install to my adopted drive rather than the internal storage which can cock things up. Just wanted people to hold off updating until we're sure it works okay with Hyperspin. I hate having to tinker with this stuff when it goes wrong, so I know I'm not alone
  7. 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.
  8. 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
  9. No worries. With the recent forced changes to Retroarch breaking compatibility with Hyperspin, using Arc Browser which is actively developed makes even more sense now
  10. Those 3 cores lack the dynarec (dynamic recompiler), work is being done to get it put into Pico and PCSX. It is drastically bad! There are many Mame cores missing in the 64bit build, Mame2010 I use for Cave. The Daphne test core doesn't work in the 64 bit version either, I'm sure there's other stuff I can't recall off the top of my head. I've never wanted to use the 64bit version, it was Mikty who kept harping on about Hyperspin using it because it has a Daphne core (which is currently pants)....hence @zerojay being kind enough to do a custom HS.apk. I guess the dust will have to settle and we shall see what happens, my vote is for HS to use the dedicated RA 1.7.8 32bit apk. I'm confident Freelancer will fix any issues with RA and his frontend Arc Browser (he has already implemented support for both 32 and 64bit versions), I use that more than Hyperspin on Android anyway.
  11. 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.
  12. Try to avoid using cdi, the groups who release them sometimes tinker with the "metadata" within the file. I've heard of games showing up with the wrong name because of this. Also some data can be cut out of cdi versions to compress them. Really old cdi files don't selfboot and I'm fairly sure redream will ignore those. Ideally you want gdi versions and convert them to chd (you can't convert cdi), I explain why in the video. I think I only have a handful of games as cdi. If a game isn't working, you're better off joining the Redream discord chat. The developer (inolen) always responds quickly and resolves issues as promptly as he can.
  13. There isn't a Reicast core anymore, it's been renamed to Flycast. You could also use the Redream emulator instead, it's your preference. I've already done a thread on here about understanding Sega Dreamcast and the Redream emulator, it should hopefully put you on track...
  14. My honest advice would be to purchase Arc Browser on the Google Play store and use that. It's actively developed and being constantly improved upon and sadly Hyperspin isn't. I actually have both configured on my STV. That single purchase can be shared with your family account and/or used on your Android phone, so although it costs money you can get quite a lot of use out of it. Arc Browser has ready made system presets and can scrape artwork online for the games. It integrates with the voice search which is a nice feature, you can say "Sonic" and all the Sonic games from all the systems you've added to AB's library will show. It now supports video previews, you can add favourite games (Hyperspin doesn't do that), choose to use Retroarch 32 or 64 bit versions for separate systems...I could go on and on. In short it'll make your life easier and is honestly a better frontend. Hyperspin will have to be configured manually through the ini files in the "settings_android" folder. Yes the Hyperspin themes do look more flash than Arc Browser BUT many of them use swf in the zip files, so aren't compatible on Android (trust me I know, having tested and fixed soooo many of them for my STV). It's definitely worth the time doing Hyperspin and Rocketlauncher on PC, as you can do many more systems than on Android. It's your decision of course but hopefully some advice from an experienced retro gamer (i.e me) helps.
  15. It also has a preset for the CDTV-CR (aka CDTV II). It's frustrating seeing single board computers getting love while Android development moves at a snails pace. Although we are assured the port is being worked on. So you see now why I haven't devoted much time to Amiga on Android when the emulators are in "hiatus". I'm more committed to overhauling Amiga on PC with static named hdf files, this will help content creators fill in the missing media. If/when Android emulation improves these media assets will obviously be used
  16. Just heard back from Ransom. The new build of Amiberry DOES have CDTV listed under the Extra Chipset (he sent screenshots). When it will be ported to Android is anyone's guess though. Apparently the devs are dodging questions about it's progress.
  17. I'm already doing that, I have my own thread on the Amiga it's worth a read as what I intend to do. I actually did an Amiga analogy with the Sega Mega Drive and it's hardware addons, MD=OCS/ECS, 32X= AGA (better graphics), Sega/Mega CD= CD32 (games with FMV and CD audio). In short we have found the WHDload collection converted to hdf files is best, adf files can be used for games not in that collection but Hyperspin has no database or media for those games (yet). The emulators on Android don't do cycle exact emulation, so each game needs to be checked it's running at the correct speed and changes to the uae files made accordingly. Ransom is doing a new collection of hdf files, he told me recently he's maybe a month or two away from completion (last I heard he's done 1,800 titles). Once I have these files I can get to work, he should also get back to me about the CDTV "Extra chipset" and Amiberry soon.
  18. I have absolutely no issue with the CD rips being renamed if it helps auto generate uae files. I may in fact rename my set to the Hyperspin naming convention for PC use, although personally I'm more bothered about the Amiga than the CD32 currently. All the best with it
  19. I thought so. I can confirm the CD rip names don't need to be changed, I've had this system configured and working for a looong time now. Same goes for CDTV games, this guide essentially covers that system too although we seem to be limited to the CDTV games that are compatible with the CD32 system. In regard to the Kickstart roms. It might be worth mentioning that although uae4arm suggests purchasing the Amiga Forever essentials app on the Playstore, as it will auto detect those Amiga kickstart (i.e BIOS) files. The kickstarts for the CD32 are NOT included, so need to be sourced elsewhere. Just an FYI in case it confuses users at some point.
  20. No worries. Can I ask, why you are renaming the cue files? Is it to do with you auto generating the uae files? I'll give an example of a game Akira. I have it in it's own folder Akira (CD32) and the files are Akira (1994)(ICE)[!].cue & Akira (1994)(ICE)[!].iso. (Full path is /storage/emulated/0/Hyperspin/Roms/Commodore_CD/games/Akira (CD32)/Akira (1994)(ICE)[!].cue You'll note that I do have spaces in the directory and file names and they don't actually match the Hyperspin naming convention. The uae file can NOT have the spaces though, so yes replacing those spaces with "_" is required. Hyperspin is looking for the uae file as we list that as the extension in the CD32.ini file, so the name of the CD rip isn't important as long as it's contained within the uae file. Because the uae files can NOT have spaces, the Amiga CD32.xml database file does need editing to include the underscores. Obviously all uae and media files must match the names used in the xml file, Hyperspin is incredibly fussy about naming as people new to it will discover.
  21. I'm not Super liking this just because I was given credit. This is one of the best written tutorials I've seen on the forum! I'm glad my adventures in all things Amiga have helped others along I'll provide a link for people to download Uae4arm 1.0.0.19 which was supplied by the Developer Lubomyr. Although Uae4arm is on the Google Play Store it has now been listed as not compatible for Android TV devices, so we have to "sideload" this apk (https://drive.google.com/file/d/1N6lR5QWREPhXXdUdDOOa5gnMD99kDX4V/view) to use an older version.
  22. I use CHD for Sega CD (to save space). Just tested Tom Cat Alley on my Shield TV to make sure all is okay after the update and it plays directly from Hyperspin. I don't think the Picodrive core supports CHD but Genesis Plus GX does (even if it's not listed in the info section).
  23. Yeah it wasn't listed where you'd expect it in the download section, sometimes it's better to just do a search. You can see what I've knocked together below...
  24. There is actually already a pretty decent theme pack made with all the assets you need (xml file, video, wheel art, pointer etc). Bjalready used png files in the zip file so it should be Android compatible
×
×
  • Create New...