Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Announcement

    Sorry for the recent downtime. Still much to do but we have the site updated, secure and back online.  Expect more changes.

Honosuseri

User
  • Posts

    843
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Honosuseri

  1. No, you clearly misunderstood the situation by saying just don't update RA. Hyperspin on PC and Android are two very different animals. When M$ does a Windows update which messes up Hyperspin, I'm confident it'll be fixed as that's happened many times. On Android I'm not as confident but hope for the best, the fact Launchbox has abandoned their Android version should tell you enough to be concerned. It's sound advice to warn new users about the changes to Android and the knock on effect it will have on HS with the STV. Arc Browser is a superior frontend with better features, being actively developed AND it's also compatible with phones/tablets when HS is not. When the Android OS changes kick in on the STV and HS is known to be working, I'll recommend HS "for show" and help people set it up. Until that day comes, I agree with Hyperseeder and new users should wait before sinking in a lot of time learning and setting up Android Hyperspin. I have a very nice Hyperspin PC setup, people are perfectly "safe" sinking time into that, many of the assets can then be shared with an Android setup later.
  2. Worst case scenario is that when the STV is updated to Android 11 or 12 that Hyperspin won't work, it's not about RetroArch but the changes Google is making to the OS. Perfectly valid post for him to make, I'd be livid if as a new user I sunk in a lot of time setting up HS for it just to stop working out of the blue. I help people with HS plenty BUT still recommend Arc Browser as it is a better frontend being actively developed. I've used HS on the STV for what 5 years, there's a suggested features thread here on the forum BUT nothing new has been added. I hope that HS will be updated when the Android OS changes kick in BUT I can't say for sure that it will be.
  3. To my knowledge it's @reznnate who we have to thank for the Android version of HS. I believe he created it originally for the Shield Portable device. I seem to recall the official HS app was updated, when it stopped working because of previous Android changes many moons ago. Of course I can't speak for future development. I applaud your efforts on modding and maintaining your version of the APK. I modded it solely for RA32 as IMHO adding the 64bit version of RA for it's limited benefits were not worth my time. I was aware of these Android changes coming, the dev for LaunchBox has stated they've stopped development of their Android version iirc. I hope FreeLancer will continue on with Arc Browser. All the best, I'm sure many people are thankful for your efforts
  4. No you don't have to guess, I've told you what to do. I explained in one of your other threads that the 64bit version of Retroarch is missing cores, it's why I modded Hyperspin to use Retroarch_ra32 (32bit). Hyperseeder took things further and his HS build allows you to have 32+64bit versions of Retroarch installed and Hyperspin launches what you want via the .ini file.
  5. Then you'd want the Mame2010 core. It's probably still missing in the 64bit versions of RetroArch. You said you were using Hyperseeders modded Hyperspin SO...Install RetroArch_ra32 and install the mame2010 core, follow Hyper's thread to ensure you do the .ini file correctly to launch RA32.
  6. The Play Store is the Devil! Their changes have caused us no end of aggro. They now limit the size of the .apk and force the device to use 32 or 64 bit depending on what's native to the device. I haven't checked in a while BUT the 64bit version of RA was missing some cores to do some popular systems, hence me modding HS to use RetroArch_RA32. I suggest you download Retroarch 32 and 64 bit versions from the Libretro website and "sideload" them through a file manager like X-Plore. Your call of course, all the best with it.
  7. You use the name of the core. You can find them listed at the Libretro buildbot which is where the downloader pulls them from, ignore the file extension (.zip) https://buildbot.libretro.com/nightly/android/latest/armeabi-v7a/ so... cores/snes9x_libretro_android.so On a side note @HyperSeeder modded the Hyperspin.apk to use any version of Retroarch (he continued on from me modding it for RA32). I would use that over the stock Hyperspin app, check his thread here on the forum to ensure you are doing the .ini files correctly.
  8. Awesome! Yes you can resize the artwork, there's free PC software called "Fotosizer" which can do the lot in a batch job. You will lose some picture quality using that though, maybe someone else knows of a better free tool for the job.
  9. I'm sure the theme you sent will be very helpful indeed. OP asked how the artwork folders are used. That was the point of my post to help them understand why the artwork wasn't showing in some themes they may have. Teach a man to fish and all that Jazz
  10. MAME doesn't have boxart as they're arcade cabinets, so it's unlikely the themes you have will make use of artwork folders. Any who...to answer your question. It's the actual system theme (Default.zip) that decides what is shown and where in the theme.xml file. Most have artwork 1 & 2 in the .zip file these are usually the video snap box border and a logo for the system. Artwork 3 & 4 can be your box and disc/cart artwork taken from your media folder. I'll give an example from a SNES theme.xml... <Theme> <video w="408" h="417" x="312" y="427" r="0" rx="0" ry="0" below="false" overlaybelow="false" overlayoffsetx="0" overlayoffsety="0" forceaspect="both" time="0.5" delay="0" bsize="0" bsize2="0" bsize3="0" bcolor="0" bcolor2="0" bcolor3="0" bshape="square" type="none" start="none" rest="none"/> <artwork1 x="312" y="429" r="0" time="1" delay ="0.5" type="none" start="none" rest="none"/> <artwork2 x="512" y="102" r="0" time="1" delay ="0.5" type="ease" start="top" rest="none"/> <artwork3 x="750" y="435" r="0" time="0.5" delay ="0.2" type="bounce" start="top" rest="none"/> <artwork4 x="900" y="560" r="0" time="0.6" delay ="0.9" type="none" start="right" rest="none"/> </Theme> Artwork 1 is the video snap border box, artwork 2 is the SNES logo, these are assets within the .zip file. Artwork 3 is the boxart it drops down from the top of the screen and bounces when it lands, artwork 4 is the cartridge it slides in from the right of the screen. If you use Hyperspin on PC there is the Hypertheme software for creating your own themes. You can do it manually tinkering with the .xml file BUT you might struggle with those x and y co-ordinates, which position things on the screen. You can be quite creative with it. I have a Mega Drive theme where Artwork 3 is an asset of the console in the .zip file, artwork 4 is the cartridges from the media folder, they lower down "slotting" into the console. THEN because of the "delay command" the video snap plays as if the console has loaded the game...looks pretty awesome!
  11. You're welcome! FYI you can load the core in RetroArch and go to core info, worth going there anyway to see if the core requires BIOS files and what file extensions are supported. You'll now find an option to backup the core which puts it in the RetroArch Downloads folder which you can view with a file manager like X-plore. The core's filename is what you use in the parameters line of the .ini file, it's handy to backup cores in case the online buildbot goes down or the core goes AWOL. Mame 2010 did disappear for a long time and without root access on the STV we couldn't backup the cores back in the day.
  12. try "parameters=cores/mednafen_vb_libretro_android.so" and "parameters=cores/mednafen_supergrafx_libretro_android.so"
  13. I have very little interest in emulation on Android now, so it's been a very long time since I touched the STV, RA & HS. I can tell you that it used to install by default to shared storage and the RA paths were different to when on internal storage. So I had to go into apps select RA and move it before running it, once run RA set the paths automatically. If you use adopted storage and everything works with your HS build then that's awesome, nothing to worry about. I only mentioned it as people use different setups, some just have HS and "roms" on an external drive with others using adopted storage...maybe both.
  14. @reznnate is the guy who did the original build to have HS on his Nvidia Shield Portable. Not sure if he published it to Google Play BUT he's the guy we are all really thankful to. Congrats on your project, sadly I don't really have the time to test it out. Those who use adopted storage might need to install RetroArch and then immediately move it to internal storage before running, worth testing that out to prevent people saying your build doesn't work.
  15. Honestly I have very little interest in Emulation on Android these days. If anything it was more for my phone to be able to play decent games out and about (not that we can do that now with the current global situation). I'm more known for Amiga emulation here and have been chipping away at the missing Amiga media (videos, disks & boxart etc.) for a while now, with what little free time I have. Most of the emulation I've done lately is in PCVR with EMUVR and New Retro Arcade: Neon. My Youtube channel also takes up much of the free time I do have. So no I'm not looking to start any other projects, I wish you all the best with the Hyperspin modification.
  16. As I said NOT ALL apps have launch intent implemented. Best thing to do is message the developer and ask for them to add the feature. I did this a looong time ago for Redream (Sega Dreamcast) and tested the APK before it was released on the Playstore. Arc Browser has no profile for Duckstation standalone, only the RetroArch core. Freelancer adds profile updates for us to use for popular emulators, of course it's possible he's not done the profile yet BUT from what you've said it sounds like launch intent isn't being used in DS.
  17. Try "org.devmiyax.yabasanshioro2/org.uoyabause.android.Yabause", that's for the free version not Pro though. I'm not paying the developer again when the old version could have been restored on Google Play, if he wanted it to be. Remember not all apps will work with launch intent which is how frontends load them. Download QuickShortcutMaker from the Playstore to your phone and install the app you want to know the settings for and it will list the activity names.
  18. To my knowledge this is the only dual Retroarch Hyperspin build and iirc it doesn't work correctly, as it can't load the config files for the 64bit version (if that's been fixed I apologise in advance). I only had a brief look at what RA Plus was and noticed the missing MAME cores and that was the end of that. I haven't abandoned HS on the STV, I invested A LOT of time making artwork and doing custom wheels for systems. I made my own HS build to use RA_32, I don't use Google Play versions and when 64bit catches up with core count I'll switch to that. Stuff like Dolphin (standalone or RA core) isn't worth bothering with on phones or the STV, it's better to use Gamestream (or similar) to have a PC version of Hyperspin play on the STV to do more demanding systems. I can't remember which core I use for PSX, I did do some tweaking which helped it run better. Don't remember what I did BUT I remember doing it for Ridge Racer as we had a competition here for fastest hot lap. I did share what I did in the thread to help stop the stutters so people could post a faster time! End of the day AB is a superior frontend, although not as "flashy" it's actively being improved. HS I use as a party piece to impress friends BUT day to day use (including my phone) I use AB more.
  19. Had a look, I won't be bothering! RetroArch Plus is just RetroArch64 rebranded. Libretro are having to jump through hoops to abide by Google Playstore rules. Size of the apk is restricted to 100MB and the cores must download from google servers NOT the Libretro buildbot. I'll stick to sideloading Libretro's versions that DON'T have assets cut out to make the 100MB apk size. 64bit versions are still missing MAME cores, so I see no real need to switch from using RA_32 yet.
  20. I've not done any emulation on Android in quite sometime honestly. I'd need to look at RetroArch Plus and see what cores it offers, it's new to me! I modded the Hyperspin APK to solely use RetroArch_ra32, which is why I linked the ra32 download in my thread. The 64bit versions were missing cores, yes they did Dolphin for Gamecube and Wii BUT not well enough to warrant me losing the other cores for MAME etc. When I have some free time I'll look at RAP and decompile Hyperspin to modify it IF it's worth doing. NO I'm not faffing around trying to get BOTH 64 and 32bit versions working, it'll be for RAP 64bit. My go to frontend on Android is actually Arc Browser as it works on both my phone and STV. Yes you have to buy it BUT Freelancer (the dev) actively maintains it and has system profiles for using 32bit and 64bit version of RetroArch.
  21. You'd know better than me, you are the one who downloaded the file and installed it. Retroarch.apk is the 32bit, aarch64 is 64bit, ra32 is a separate dedicated 32bit build. Hyperspin needed modding to use ra32. Sounds to me like your issues are the rom path as you're doing it over a NAS. It can be done, someone mentioned earlier in this thread they are running multiple STVs from a samba share. Edit one of your .ini files so under filters "roms only = True". If you load that wheel and nothing shows then then rompath is wrong. If set as "roms only = False" it's just showing everything listed in the database.xml file whether you have it or not.
  22. Happy to hear you sussed it out. Part of the reason I modded Hyperspin to use RA32 was so we got that Mame2010 core to use, it's missing in the 64 bit version of RetroArch. All the best with your setup, have fun with it!
  23. Do your MAME games work in just Retroarch? There are different cores to use for different MAME romsets and I have no idea which set you are using. it's best to know the games play first before you worry about the frontend Hyperspin. Remember your .ini files to be used live in the "Settings_Android" folder. "Settings" is for a PC setup, these folders are separate for those who want to use an external USB drive and switch it between a PC and an STV
  24. That's a shame, thank you for letting me know. It will show a cursor when the mouse is connected because of the Android OS, it won't add one for a virtual controller RetroArch is using. In Android Oreo the feature was added for apps to "capture the OS cursor" but it has to be written into the program (I think DosBox, Uae4arm and a few other emus do use it iirc). So this is an issue that needs to be raised with Libretro, I wouldn't be surprised if it's not already. It's a very niche problem. People who do emulation are a very small percentage of Android users and of them even fewer are emulating classic computers that use a mouse.
  25. Try pressing the "scroll lock" (try "Fn + Capslock" if there is no dedicated key) on the keyboard to activate game focus mode, this disables the keyboard shortcuts like "F1" opening the RA quick menu. It will hide the system mouse cursor on PC so you'd only see the "Lemming hand" cursor, I have not tried it on the STV yet as it's packed away...let me know how it goes.
×
×
  • Create New...