Note that this is option is not visible in HyperHQ, so we'll have to do it manually. To do that, go to G:\HyperSpin\Settings and open up Settings.ini.Ĭhange the HyperLaunch Path into the RocketLauncher path. Don't worry as we can simply redirect it to RocketLauncher in the steps below. HyperSpin v1.3.3 still refers to HyperLaunch instead of RocketLauncher.
Don't worry though, it is simply a pointer to the HyperLaunch.exe which we can easily change. HyperSpin 1.3.3 still refers to HyperLaunch instead of RocketLauncher. Since we are using RocketLauncher we will first have to change the path pointing to our RocketLauncher path.
#Hyperspin tutorial 2019 archive
The archive password is as mentioned in the download page.Įxtract the downloaded RocketLauncher.zip into the RocketLauncher folderĬhanging HyperLaunch Path to RocketLauncherīy default, if you're following Ryan's guide, HyperSpin assumes that the HyperLaunch is located at C:\HyperSpin\HyperLaunch. Just like HyperSpin, you'll need to register as member to download it.Įxtract it into a folder named 'RocketLauncher' under your HyperSpin folder, such as G:\HyperSpin\RocketLauncher. HyperLaunch 2.25c, which is pretty much outdated and replaced by HyperLaunch v3, and now RocketLauncherįirst, download the RocketLauncher v1.0 (Full Install) (65MB) here.ĭownload RocketLauncher v1.0 (Full Install). We are going to replace it with RocketLauncher.
#Hyperspin tutorial 2019 install
HyperSpin v1.3.3 Full Install came bundled with HyperLaunch v2.x, which is a very old and outdated copy of HyperLaunch. This tutorial assumes that you already read through Ryan's guide and downloaded/extracted the following: Think of the modules as a pre-defined CLI (Command Line Interface) that is pre-programmed to handle launching the emulator, e.g. RocketLauncher provides a set of script or modules for basically every popular emulators to date.All configuration steps and settings UI remains the same in RocketLauncher just as in HyperLaunch, so the walkthrough written by Ryan's are still usable.You can still use HyperLaunch, however I recommend to transition to RocketLauncher for any latest updates.HyperLaunch is renamed/rebranded as RocketLauncher to remove its ties with HyperSpin, since it is meant to be a multi purpose launcher for other Front-ends as well.But you could refer here if you're trying to integrate it with RocketLauncher instead of HyperLaunch. Don't get me wrong, I highly recommend you follow Ryan's comprehensive guide to its entirely, which is what I did when I'm starting to set it up. While trying to setup HyperSpin following Ryan's Full Guide on Setup HyperSpin MAME and Hyperlaunch, I found that some extra steps are necessary to integrate HyperSpin with RocketLauncher. Before you read on, this is an extended tutorial on setting up HyperSpin with RocketLauncher, which now replaces HyperLaunch.
0 kommentar(er)
