Greetings! Also..please help

[qualx]

Hello!

I've finally taken the dive and am in the middle of creating a 4 person "portable" emulation station using hypersin as my front end. Creating a cab is something i've always wanted to do but never had the  room. Now I have a house though so it's finally time! I

I have been digging into this for the past couple weeks getting the PC parts and software configured before starting my cab build and was hoping someone might help me with a very odd issue. If I should post this elsewhere please let me know. I'd like to be an active community member and contribute to such a fun hobby.

 

So here's the details:

I am using Rocket Launcher and Hyper Spin and have been able to successfully add multiple emulators with no issues with the exception of MAME. 

I can load roms ( currently using romset 0.196) with no issues through RL, and through mame64 but when I try to load any mame rom through HS it refuses to load.

The Mame initializing screen pops up, you can see the percentage move very fast, then it disappears (about a second or so) and then it goes back to the mame hyper spin wheel

Another weird thing to mention, after unsuccessfully loading a mame rom i'm unable to load any rom for other systems that already work, it just sits at the HS menu as if I didn't do anything.

it's not much to go off of, but here is my HS log

https://pastebin.com/Y51apvYw

It looks like it tries to load any game I choose, but it just..dosent do anything

I have an HD5450 card in my mutilation PC and found a forum where someone had a similar card. They needed to downgrade to the 15.7.1 drivers but that didn't work for me. I've tried several driver sets with no luck.

Other system specs:
I7 870 CPU
8GB Ram
Win10 Pro

I double checked HS & RL, I have the correct rom and emulation paths setup, Extensions are set to zip and chd (hs and rl), and I tried to uncheck the "rom only" box in HS

Not really sure what to try at this point so I was hoping someone else here may have run into this before. If you need other logs i'd be more than happy to send them over, i'm just not sure what you need.

Thanks for any help!

[Bungles]

Welcome,

Sort of looks like Hyperlaunch is being used instead of Rocketlauncher still.

Check your Settings.ini file in the Hyperspin/Settings folder and be sure that Rocketlauncher.exe is set in your default Hyperlaunch_Path.

Also check in RocketlauncherUI that Hyperspin is your Default and Active Front End.

 

However if other systems are working from Hyperspin ... hmm.

 

[qualx]

Thanks Bungles! 

So both are already set as you mentioned,

I did figure out I was missing my mame ini file, so I created it, and set my rom path, this seemed to get me further but now it just hangs at the loading splash screen of any rom I load.  Any other ideas?

 

Edit: here is an imgur link to my screenshots to make it a bit easier to see

https://imgur.com/a/0WRdwyr

 

 

[qualx]

Hi so this is fixed now! In case anyone else has this issue here is what I needed to do to fix it step by step, hope this helps some other poor soul who gets stuck in my position.

 

First, I did not create my Mame ini file, if you need to create one and don't know how:

1. Open a CMD prompt, and change your directory to your mame emulator folder so in my case I had to run it as follows

cd C:\Hyperspin\HyperSpin\Emulators\Mame   (you'll need to replace the directory with where your MAME emulator is)

Then run this command to create the ini
mame.exe -cc

This will create a mame config file in the same mame directory

Open your ini file and add your rompath

 

Once that was done I was able to open my roms, but I could only open one mame rom at a time without having to fully close hyperlaunch.exe form my task bar, it seemed to just hang indefinitely disallowing me from opening anything else. The big takeaway is that i'm (supposed to be) using RocketLauncher, not hyperlauncher.

 

long story short  my hyperspin settings ini  had an extra colon before my rocketlauncher path and that was causing rocketlauncher to not be called and instead hyperlauncher was loading, and not closing when exiting roms.

 

So in case anyone has this god awful issue they can use my poorly worded fix to help them along the way.

 

TIME TO BUILD MY CABINET!

 

 

[griffin518]

Delete your hyperlaunch.exe and don't look back

Welcome to the community.

[qualx]

42 minutes ago, griffin518 said:

Delete your hyperlaunch.exe and don't look back

Welcome to the community.

Yup it's long gone now! I'm so happy it's working the way it needs to. Hoping to start building out the cabinet this weekend

[griffin518]

Next step is for you to pick up a platinum membership here, and a supporter membership at emumovies, so that you can **really** dig into the artwork and customization side of things

 

[qualx]

28 minutes ago, griffin518 said:

Next step is for you to pick up a platinum membership here, and a supporter membership at emumovies, so that you can **really** dig into the artwork and customization side of things

 

Already picked up a membership for emumovies and have been destroying my bandwidth this month. Good thing I dont have a cap, I've downloaded a little over 1TB between a new mame rom set and all the emumovies since last week