Jump to content

Honosuseri

User
  • Content Count

    786
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Honosuseri

  1. I don't expect an official fix until the 64bit versions are actually worth using! If there's enough demand, I'll do a video & provide the apk to get RA 1.7.7 installed and working with Hyperspin again for those who updated and are struggling.
  2. From what I read Launchbox on Android imports from a PC setup you have to already have 🙄 I use AB and Hyperspin. AB works with the voice search which is a nice feature. If I say Mortal Kombat, AB shows the games and KODI shows the movies I have in their Libraries. Although yes HS looks more "flash" with the animated themes but AB does now support video files. I think we need the dust to settle. Retroarch 64 has been in a sorry state for a while now BUT with Google forcing devices to use 64bit if it's native to the device, we should start to see RA64 improve. When RA64 is in a better state Hyperspin could then be made to use the 64bit version as default, as it's only compatible on the STV which is a 64bit device.
  3. 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
  4. Yes you can do that, although you may notice input lag. I can recommend the alternate Frontend Arc Browser. I told the developer about the Retroarch issue and he's already implemented a fix to use the retroarch_ra32.apk. I know it costs money to buy the app but seeing as it's actively developed and Hyperspin on Android isn't, you can't really complain. You can use it on the Shield TV and an Android phone, it also can be shared with your family if you use that account feature with Google Play. He creates presets for the systems and their emulators so setup is actually very easy to do, it can scrape the internet for metadata and artwork too.
  5. If we click on them it loads a page with the image. Circo has been on the case lately working on the website to fix issues, he's been laid up for months with a broken leg (as have I). Raise the issue on the site maintenance thread and I'm sure he'll look into it. Nice looking little cabinet. Loved seeing the Lemmings walking off the blocks, that's a nice touch us Amiga fans can appreciate
  6. 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
  7. Can we now download from the attachments made in posts Circo? Hope you're recovering well, I broke my leg end of January and still not 100%. So I do quite literally feel your pain.
  8. 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
  9. 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.
  10. No worries. I've now updated the link with the new uae4arm (beta).apk https://mega.nz/#!TYMQQKob!9pzwooQbkxVd-__mwmqtFWNF9JSR7D7rEgY8tqu31Vg
  11. Not to my knowledge. The G29 if memory serves has 900 degrees of rotation and has a force feed back motor, it doesn't rumble it actively fights your input. I honestly don't really spend anytime in my MAME wheel at all, although it obviously has some classics in there my friends do want to play. The Arcade PC driving games are actually pretty good, my friends got a kick out of the Initial D series of drifting games as they were Japanese (I've never seen them in the UK). I actually haven't built a cabinet yet to mount anything on, although my Uncle showed great interest having one on the family Yacht. I can't decide between a traditional stand up cabinet, an "arcade coffee table"/cocktail cab or a Pinball style with the Arcade sticks mounted on. I intend to grab a Rift S VR headset in the holiday sales. I do have New Retro Arcade: Neon setup with lots of MAME games. It's literally a virtual arcade so I'm thinking it would be kind of cool to stand in front of a stand up cabinet in the real world and use it's controls to play games in the "virtual world". Whatever I end up building I'll do a build log on here.
  12. 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.
  13. Get the G29, basically the same BUT has more buttons so a more versatile wheel! That's a lot to pay just for Mame games. Although there are plenty of good driving games if you also do Arcade rips (more Modern Arcade cabinets that are actually PCs) and of course the proper PC racing games/sims
  14. 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.
  15. 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...
  16. 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.
  17. 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
  18. 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
  19. 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
  20. 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.
  21. 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
  22. 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
  23. 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.
  24. 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...