dsnyd22 Posted May 11, 2015 Posted May 11, 2015 Anyone know what would be causeing my hyperspin issue. I just did the update to rocketlauncher. I drug everything over from the update. except some modules and my xpadder settings. Now when i go to start a game in hyperspin it never starts. hyperlaunch doesnt even run. I did back up my old hyperlaunch but id like to get the new one working to take advantage of the updates. any help is appreciated.
goateechin Posted May 12, 2015 Posted May 12, 2015 I've been having a similar problem. Can't get RL talking to HS. It's all a clean install, so instead of starting with Hyperlaunch and then making the transition to RocketLauncher I just went straight for RL. But it doesn't seem HyperSpin is set up for it yet - the internal settings still ONLY point to HL - eg: command line preview -HyperLaunch.exe "MAME" "RomName"- and I can't see any way to make it point to RL. Any thoughts??
SIMPLYAUSTIN Posted May 12, 2015 Posted May 12, 2015 Rename R'Launcher.exe to H'Launch.exe? Simply Austin's YouTube
rfancella Posted May 12, 2015 Posted May 12, 2015 Ok, there are a couple of things. Do not rename anything. There is a transition tool that will do all the work for you. All the work. Get it at the RocketLauncher site and the RL Update Pack. Put the Transition tool in some directory other than the HS or HL directory. Run it. Be sure and tell it if you are using HyperSpin 1.3 or 1.4. When it's done, extract the contents of the Update pack into your new RocketLauncher folder and run RocketLauncherUI. It will ask if you want to run updates. Updates to RL are now done through RLUI. Easy Peasy! Thanks, Ron Code Monkey and all around Command Line geek!If you like what someone has said or done for you, be sure and 'Thank' them. And if they changed your life, send them a Beer!
goateechin Posted May 12, 2015 Posted May 12, 2015 Rename R'Launcher.exe to H'Launch.exe? Thought of that - but 1. I presumed that would probably cause trouble down the line as surely something would go looking for R'Launcher.exe at some stage? and 2. I thought it was a bit shortsighted as RL is the future for HL is it not? That's hardly the plan for RL going forward? to need to rename the file back to the replaced version??
goateechin Posted May 12, 2015 Posted May 12, 2015 Ah. Thanks! Do not rename anything. There is a transition tool that will do all the work for you. As I said I am working on a clean install and presumed it would be all set up ready for the update.
rfancella Posted May 12, 2015 Posted May 12, 2015 Hi,That is my bad. I did not even see your post in there. I was responding to the OP. For a clean install, it depends on if you are using HyperSpin 1.3 or 1.4 beta. You would have to be using 1.3 because the 1.4 beta (which has the fix in it for RL) is in the Platinum Dowloads section.Hopefully the beta is soon to be released to everyone soon. In the mean time, there is a fix to this.The issue comes from HyperLaunch being hard coded to look for HyperLaunch and it cannot be changed. The directory can, but it still looks for HyperLaunch.exe. The beta, you specify the full path and exe to the launcher.Yea, blah, blah, blah. Ron, come to the point! Unill the fix is update in HyperSpin, here is how you can setup HyperSpin 1.3 to work with RocketLauncher (skip down to section B ). http://www.rlauncher.com/wiki/index.php?title=Transition_From_HyperLaunch3 Hope this helps some. Thanks, Ron Ah. Thanks! As I said I am working on a clean install and presumed it would be all set up ready for the update. Code Monkey and all around Command Line geek!If you like what someone has said or done for you, be sure and 'Thank' them. And if they changed your life, send them a Beer!
dsnyd22 Posted May 12, 2015 Author Posted May 12, 2015 nice! kinda makes sense to me now. im going to try now again to get it working and use transition tool.
Jobber8742 Posted May 15, 2015 Posted May 15, 2015 So what do I need to do, if anything, to make rocketlauncher work with 1.4 beta on a clean install?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.