Jump to content
  • Announcement

    The HyperSpin 2 early access beta is here!

    We’re starting the first public testing phase with Platinum Members to keep the scope manageable while we test the current feature set and begin to add more. In the future, we’ll provide a version for basic members as well.  On behalf of the entire HyperSpin team, we look forward to another exciting adventure with our community.

Selecting MAME Crashes Hyperspin [SOLVED]


kmustafa27

Recommended Posts

Posted

Hey everyone,

 

Quick backstory: I had everything set up and running perfectly on my HDD about a week ago. I then decided to move everything over to an SSD to make things even quicker. Instead of mirroring of the HDD to the SSD, I simply copied the Hyperspin folder from the HDD's C: drive, placed it on an external drive, and then from there, placed it on the SSD's C: drive.

 

From there, I found that there was an update to RocketLauncher which I performed with no problems. I went into Hyperspin and double checked all of my systems and all of them worked perfectly...except for one. Everytime I select MAME off of the system wheel, Hyperspin immediately crashes. However, if I run the emulator (mameui64 v. 0.149) outside of Hyperspin, I don't encounter any issues at all.

 

I've tried reconfiguring/reentering things within HyperHQ and RocketLauncherUI, but with no luck.

 

Has anyone experienced this and/or know of what else to look for or check to correct it? My last guess is that it could be that I need to update my MAME, but I don't understand why it would work previously before going to SSD, and not now, unless updating to RocketLauncher caused something. And if it did, how come it's not spitting out a warning within Hyperspin like it normally does when something goes wrong?

 

 

Any suggestions are greatly appreciated. I have included a video link below to give you all an example (sorry for the shakiness, had to shoot from my phone since the arcade computer isn't currently connect to the internet).

 

Video: http://www.screencast.com/t/kPkWo67nU

Posted

Found the solution. After checking the Hyperspin Log (which i didn't even know was there...), I found out that I had the read "Parents Only," and "Roms Only" options turned on within HyperHQ. This wasn't a problem when I was on the HDD, but apparently was on the SSD. After switching those off, it worked perfectly :)

Posted

I'm going to guess that the Roms Only did more damage than Parents Only. Or the combination of both

 

I have Parents Only selected for MAME and I'm using a 500GB Samsung 840 EVO SSD

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...