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.

sonkun

Platinum Member
  • Posts

    121
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by sonkun

  1. Yes a new test apk was uploaded in this thread I believe on page 5 or something. Go back a few pages and you'll find it
  2. Nice I'm glad you got it sorted out. Yeah so that's the folder you'll dump all your bios in. You say you plan to add in turbografx etc, that core also needs a bios file that'll need to be put in the same folder you put that saturn bios, along with any other bios you'll need for future cores you plan to add that need a bios. As a bonus here's a wheel you and everyone else can add to their Hyperspin set up It's a Sonic Hack wheel I put together not to long ago, every game on that wheel can be played using the Genesis Plus GX core. Games from Game Gear, Master System, Genesis and Sega CD are all included in that wheel. That should add some more fun to your set up.
  3. Yaba Sanshiro definitely works on Retroarch as I've been doing a lot of Saturn gaming on it all this week even played a game a few minutes ago. Ok let's try a few things, first open RetroArch, go to Settings/Directory. The first thing you should see at the top is System/Bios. Whatever is displayed there is where RetroArch expects you to place all of your bios files so if your saturn_bios.bin file isn't in the folder that System/Bios line shows, that's the reason it shows up as missing when you load up the yaba sanshiro core so get that straightened out first to where it shows the bios file as present whenever you load the yaba sanshiro core, that'll also help with other cores that expects a bios file in the same location. Unless you've changed that location to a different folder of your choice, the default bios path should be: /storage/emulated/0/RetroArch/system So place the saturn bios file in your RetroArch/System folder if that is what you see. Take it a extra step by making sure the naming is correct, I use to have problems with my Hyperspin not loading a game because of case sensitive naming, example being that even though you might have the "saturn_bios.bin" It's possible that it could still show up as missing if it's spelled like "saturn_bios.BIN" so make sure all letters match letter for letter if it's all lower case. Next, delete that system opt file it's not needed. See what happens after doing those two things and get back to me.
  4. Yes, whichever driver output you set it to will save across all cores after you exit and re enter RetroArch, I suggest setting it to vulkan for everything use gl for just mupen64plus gles3 and yaba sanshiro (Assuming you're playing on Shield TV. If you're playing on a newer phone then I suggest using the more accurate Beetle Saturn core and maybe try mupen using both the parallel plugins which those two cores should also be played using the vulkan driver instead of gl.). I'm not sure why you have system.opt files, I only have system.cfg files and game.opt files depending on if I tweak and save a specific game option in the core options. What are in your system.opt? To get to individual core settings you first have to start up any game in any core then head into the quick menu and go down to core options, but that's not how you would set a individual core to just use gl while the others use vulkan etc. To set a individual core to gl while your global setup is on vulkan load up any game, go to the quick menu/main menu/settings/drivers/set it to gl/settings/quick menu again/overrides/save core overrides. After saving I suggest going back to to quick menu and then hit close content to ensure that your settings have been saved properly then go down and hit quit retroarch. Saving a override is also how you create a system cfg in the config folder as well. Now when you load up that system again it will always play in gl driver mode even though your global driver is set to vulkan. For yaba sanshiro, does it not work only when you run a game from hyperspin or it also doesn't work through retroarch alone? If it's through hyperspin try using this: parameters=cores/yabasanshiro_libretro_android.so If that doesn't work let's confirm that it's finding your bios when you load the core so go into retroarch and load up the yaba sanshiro core then go down to information/core information then look at where it says Firmware, the only bios you need is that saturn_bios.bin file, if it says the word Present that means it sees your bios file, if it says Missing then that could be your reason for the crash. If it sees your bios file and it still crashes maybe you have a bad bios which I could help get you a better one through a pm only. Let me know how things go.
  5. I see people here making the switch to RetroArch for this new version of HyperSpin, that's good as I feel RetroArch is one of the best all in one ways to play these retro games. I see people having trouble on RetroArch with the Sega Saturn and Nintendo 64 cores, I'll try to help out the best I can. Mind you I'm still on 8.2.3 on my Shield and will not update it to 9 until I know for sure HyperSpin works again at the least but first thing's first, for Sega Saturn and Nintendo 64 use the Yaba Sanshiro and Mupen64Plus-Next GLES3 cores, the Parallel N64 core use to be good but is now outdated so it's not recommended. For the other Sega Saturn cores Yabuse does work kind of but it's also really old and outdated and the best Saturn core Beetle Saturn is the most accurate but the Shield simply isn't beefy enough to handle it so it runs slow as hell ( I wish it worked). Next, those two cores (Yaba and Mupen) only work fast on the Shield in GL mode so make sure your driver in the settings options is set to "gl" and not vulkan, use vulkan for all other systems though. Next I'll point out that the Yaba Sanshiro core has not been updated in almost 2 years or more, it's still stuck on the old 3.4.2 version and the mod that runs that core refuses to update it for reasons he stated on the libretro forums you can find if you do a search there. For N64 after you load up a game I recommend you go into the core options, there you'll see a few settings, one named RDP Plugin and RSP Plugin. Leave RDP Plugin on the GlideN64 settings and leave RSP Plugin on the HLE setting. Most people would recommend changing both of those settings to Parallel which is suppose to give you better speed but for some reason on the Shield it does the exact opposite and slows games down so I don't use it and it has not been addressed yet. Anyway go into the GlideN64 settings and change all these settings I'm about to list below to give you a better and closer to accurate gaming experience: 4:3 Resolution - 320x240 Bilinear filtering mode - 3point Dithering - On MSAA level - 8 Copy auxiliary buffers to RDRAM - On Background Mode - Stripped Continuous texrect coords - Force Native res. 2D texrects - Optimized Less accurate blending mode - Off GPU shader depth write - On Anything not mentioned you can leave as is. For Yaba Sanshiro I recommend using chd files over the bin/cue format, for some reason when I used bin/cue I had problems with bgm tracks not looping properly and playing bgm from whole different parts of the game instead of the intended stage bgm, that all stopped when I switched over to the chd format. If both the Yaba and Mupen cores crash for you before even loading up try going into into your folder program and the RetroArch/Config and then go into both the Mupen or Yaba folder and then open up the cfg file and look and type in "video_driver = "gl" then save it, that way way even if your video driver setting is set to vulkan those two cores will always start in gl automatically for you. Also make sure you're using the latest version of RetroArch and not some old outdated version, a lot of problems happen because a user is using an old version of RetroArch. Dolphin stopped working on Android RetroArch for almost 3 years now as well so your only choice is the stand alone emulator for that. I'm sure some of you know PS2 now works on the Shield and I posted the parameters needed in the ps2 settings thread to get that up and running on here as well. Finally this one is a little off topic but for those now switching to RetroArch and would like to apply a filter/shader I made some nice looking shader presets you can use to get that old school crt look. I made a shader pack that only works with the vulkan driver and then I put together a gl shader preset you can also use specifically with the Yaba and Mupen cores in gl mode that you can check out here: https://forums.libretro.com/t/please-show-off-what-crt-shaders-can-do/19193/4855?u=sonkun and here: https://forums.libretro.com/t/a-new-little-shader-i-did-glsl/36028/114?u=sonkun Another benefit to switching over to RetroArch is you can use overlay bezels to fill in the black spaces on the side of the screen to get your games looking like this: https://ibb.co/C7Ry3x5 https://ibb.co/9TbRDB1 Any other questions and I'll try to help out the best I can. I can't wait until everything is sorted out and we all can use HyperSpin again new and improved again.
  6. Kind of hit and miss. Best thing about this emulator is that it's like Dolphin where you can long press on an individual game and create specific profile settings. With games I tried, one game may work 100 percent speed with certain overclock settings while those same settings will slow another game to a crawl, just gotta experiment with your games.
  7. exe=xyz.aethersx2.android/xyz.aethersx2.android.EmulationActivity parameters=bootPath Here's the catch for my Shield TV external harddrive users though, your games have to be placed in a readable/writable location so that means they have to be placed in your NVIDIA_SHIELD folder which should be right in the root of your harddrive. My rompath is set up like so: rompath=/storage/86B671FEB671EF55/NVIDIA_SHIELD/Sony PlayStation 2/roms/ so your set up will likely be: rompath=/storage/whatever your drive is called/NVIDIA_SHIELD/where ever you choose to place your games folder Placing games anywhere else besides that nvidia_shield folder on your external drive will always bring you to the "insert disk" screen when you try to launch any game from the wheel. With all of that though your games should launch from the wheel like your other systems, mines definetly do and I can't be any more happier to finally play ps2 on the ol' Shield.
×
×
  • Create New...