Jump to content
Sign in to follow this  
waddlecaudle

Hyperspin with Retroarch black screen on all but the most recently loaded

Recommended Posts

So I know this is specific, but it seems some other articles/posts run into a somewhat similar issue. I have Retroarch, and from the RocketLauncherUI I am able to successfully load all of the emulators I want to. However, from Hyperspin, only the most recently emulator loaded directly from Retroarch will successfully load, all others go to a black screen.

Example. If I load Super Mario 64 from Retroarch using detect core it loads perfectly. I can then go into Hyperspin and load Goldeneye64 no problem. Now if I go to load Sonic the screen goes black. Back out, open Retroarch, detect core load Sonic. Loads fine. Go back to Hyperspin, load Lion King for Sega and all is well. Go to load Goldeneye64 and get a black screen.

This can be repeated for other systems, so it seems it is dependent on the most recently loaded system.

I have turned on settings per core and turned them off. Off it loads a window with an overflow of gibberish (likely from the bad core config). This goes for the settings in RocketLauncherUI and Retroarch. I can't figure it, but it is so close to working... Rather frustrating. Also, have the specific cores selected for each system in the system specific Retroarch configuration within RocketLauncherUI.

Any help is appreciated. Windows 8.1.

Share this post


Link to post
Share on other sites

@thcdgaf just updated to the latest stable version. Now I'm getting a blank console and retroarch doesn't load (similar situation as explained before just console instead of blank screen). The roms should be good, just used random ones as an example but all of them I have run directly through retroarch run.

Thanks for all suggestions.

Share this post


Link to post
Share on other sites

Sounds like you have config problems I would set everything back to default or re-download it and start over. just download all your cores you want run all of them to make sure they work. Set retroarch up just like any other emulator in the global setting then just set your rom paths for your systems and select retroarch as your emulator. If you want different setting for  each systems lunch it through rocketluncher or hyperspin and hit F1 then set your setting as you like then hit save new config. Then go to your config folder in retroarch and name the new config file the same name as your system. easy way to find the recent file is sort by date should be the top one.

 

I hope that helps you.

Share this post


Link to post
Share on other sites

Are you saying you can't run it in rlui if so you gotta have have name of config file same as xml name convention then on rlui go to modules then go to retroarch module and edit global settings point the config to config of system you are wanting to run and the do configuration per core to yes

Sent from my LGL16C using Tapatalk

Share this post


Link to post
Share on other sites

Hey @kylecp1979 I was hoping to avoid a full reinstall. I can assume (since updating retroarch didn't work) it is something in my HyperLaunchHQ configuration for the individual wheels that is causing it or the RocketLauncherUI configuration for the emulator so I am going to try setting some of those back to default and see how it goes.

@thcdgaf I can open all games fine from RocketLauncherUI, it is only from Hyperspin I am having any issues.

Thanks for the help/recommendations guys

Share this post


Link to post
Share on other sites

which hyperspin are you using? look at your hyperspin log file i notice sometimes you have to do transition tool even though its not required to make hyperspin work

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Similar Content

    • By Honosuseri
      As we celebrate 25 years of DOOM! John Romero has brought us SIGIL, an unofficial 5th chapter to the original game. So as Retroarch's Prboom core has now been updated to support it...figured I should really add it to my Doom Classics wheel...
      Threw together a Sigil theme, wheel art and video snap. I was pleasantly surprised, that the prboom core now played the midi music natively. Doom 1&2 originally required me to add the music tracks as mp3 files. 
    • By Honosuseri
      As you probably know there is a RetroArch core to play Daphne games BUT currently it's broken! I wish the developer luck getting the official core stable.

      Thanks to @Reznnate. We now have access again to the working test core (HERE: https://drive.google.com/open?id=1frcFNWPinSkfyafsBXsnfHd46_kS1yIY). We can install this .so file through a new feature in RA, an install core option under "load cores" has been added. I've put together a video to help you peeps understand the Daphne game files and the settings required to get the games playing through RA and Hyperspin. I hope it's of help to some of you....
       
       
    • By zerojay
      A few days ago, I decompiled and edited the Hyperspin APK to allow users to use 32-bit and 64-bit installations of Retroarch together. It's been confirmed working by the community and you can find that edited APK here: https://zerojay.com/nextcloud/index.php/s/3QfPqYM4A6ymjr4
      It works as you would have originally expected using a 32-bit or 64-bit version of Retroarch to work, so in your Settings_Android system ini file, change the exe to com.retroarch to use the 32-bit version or change it to com.retroarch.aarch64 to use the 64-bit version.
      32-bit Retroarch: exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture 64-bit Retroarch: exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture Currently, both 32-bit and 64-bit versions of Retroarch will be called using the 32-bit configuration files, however I will likely be updating the APK to allow you to use the 64-bit configs as well for those who may wish to use different settings for both. When that happens, I'll keep both versions of the APK available so that you can decide what you want to use.

      So now that the community has solved the Retroarch 32-bit problem, it would be really helpful to compile a list of cores and the version of Retroarch that it works best under. In some cases, certain cores currently only function under one or the other, but not both. In some rare cases, cores stopped working like Daphne, so again, these are things that we would like to call out. (By the way, for anything like Daphne where more recent cores no longer work, I can host them for the community if needed. Just let me know (and I do myself still need to get that working Daphne core myself).

      I'll update the top post here to reflect the community's findings so that people only need to come to one place to find the info they need.
      --- Core Information ----
      atari800 - non-functional on 32-bit due to Android security changes, use 64-bit Retroarch core.
      mame - Latest version of MAME core only recently started compiling on 32-bit, not available yet on 64-bit.

      EDIT: Updated link for latest updated build.
×
×
  • Create New...