Issue with PCSX-Reloaded Launching from Hyperspin

[StevePhoenix]

Hi All, 

 

I am currently working on setting up Hyperspin. I have been able to get the emulators running for SNES, Genesis, and NES working perfectly but am having issues with PSX. I have tried a couple of the different emulators (liking PCSX-Reloaded the best). When opening up PCSXr outside of Hyperspin, I click run ISO, select the game (BIN format) and it works fine. When I try to go through Hypersin I get the following error:

 

There was an error waiting for the window "ahk_class PCSXR Main". Please check you have the correct version emulator installed for this module, followed any notes in the module and have this emulator working outside your Frontend first. Also turn off Fade to see if you are hiding your problem.

 

The version of PCSXr I have is 1.9 while the Hyperlaunch HQ has listed 2.0.4 as the version to use. I am unable to find this version anywhere. Do I need a different version of PCSXr to get this to work or is the problem somewhere else?

 

Any help is greatly appreciated. Thanks!

[32assassin]

I'm using version pcsxr-1.9.93-win32 and the current module works fine.

 

 

you need to provide details of how your set up your PlayStation system.

 

and your log (set to trouble shoot)  would help.

[StevePhoenix]

Thanks for your response. It's good to hear that the emulator works with Hyperspin and it is just user error. Not sure what specific details are needed to troubleshoot. I attached the hyperspin log but it doesn't look like it gives any information about the error. 

 

I have used both HyperHQ and HyperlaunchHQ to set the emulator/rom path and ensure that it is reading all of the different ROM types (I updated it to use Img and BIN file types). So far I have tested with BIN, IMG, and 7z file types and have received the same error for each one. I have been able to launch and play the BIN and IMG file types outside of hypersin.

 

Let me know what other information is needed or how to run a more specific trouble shooting log and I will post it.

 

Thanks for your help.

log.txt

[32assassin]

I need your Rocketlauncher (make sure is set to trouble shoot) log not your Hyperspin log.

 

this sounds like a Rocketlauncher setting issue.

 

 

you only need to add rom paths in HyperHQ if you are using rom filtering.

I filter by "wheel only"; I have no rom paths or extensions in any of my HyperHQ settings.

 

.

Make sure you have demon tools disabled for your Sony Playstation system if you wan't to load bin/images directly.  

 

 

 

edit,  

 

sorry  I just noticed that you are using an old version of Hyperlaunch

I'm not sure if you will be able to load a bin file directly.

[StevePhoenix]

So I should try the latest version of HyperLaunch? Will I have to update both Hyperlaunch and Hyperspin to be able to launch the BIN/IMG files directly from Hyperspin?

 

With a newer version of Hyperspin will I have to reconfigure any of my settings or can I just update to a newer version within Hyperspin/Hyperlaunch?

 

Sorry for all the questions but thanks for your help!

[32assassin]

the latest version of Hyperlaunch is version 2

 

you are using Hyperlaunch3,  this has been updated and renamed to rocketlauncher.  Hyperlaunch3 no longer exists.

 

I'm pretty sure you can load your Bins directly,  I did when I used Hyperlaunch3.

 

like I said Hyperlaunch3 no longer exists and you will not find any updates for it.  you are better of updating to Rocketlauncher

 

You can use the transtion tool  rename your all your Hyperlaunch3 components to rocketlauncher then update

discussion

http://www.rlauncher.com/forum/showthread.php?948-RocketLauncher-v1-0-Release!

 

directions

http://www.rlauncher.com/wiki/index.php?title=Transition_From_HyperLaunch3

 

 

You do not need to update Hyperspin unless you screw something up using the transition tool.