Difference between revisions of "RocketLauncher Clean Install"
| Line 15: | Line 15: | ||
=== Updating via GIT === | === Updating via GIT === | ||
| − | + | The installation package will not have the latest files on GIT, only the files at the time the package was made. | |
| + | |||
| + | To get the latest, you will need to install GIT for windows and TortoiseGIT to make using git easier. Follow the guide on the old google site [https://sites.google.com/site/hyperlaunch2/home/downloads here]. | ||
=== Understanding how the ini system works === | === Understanding how the ini system works === | ||
Revision as of 20:58, 9 January 2015
Contents
Demostration Videos
If this is your first time with Hyperlaunch 3 and you want to understand more about what this is all about, please set aside some time to watch those videos which go over all of HyperLaunch 3's features and file and folder structures so you can familiarize yourself with where everything needs to be placed.
How to do a Clean Install
Grab the files
Grab the latest HyperLaunch installation package from the HyperLaunch Download section and extract it to the root of your desired drive, eg. C:\HyperLaunch
Updating via GIT
The installation package will not have the latest files on GIT, only the files at the time the package was made.
To get the latest, you will need to install GIT for windows and TortoiseGIT to make using git easier. Follow the guide on the old google site here.
Understanding how the ini system works
All these files are found in your HyperLaunch\Settings\ folder.
HyperLaunch.ini: This file contains settings not specific to a single system. It would contain keys, paths, settings, etc that you wouldn't change on a per-system basis for whatever reason
Global HyperLaunch.ini: This file contains the same keys found in the system's HyperLaunch.ini, but will have the default settings that affect every system. If you want to turn on and configure a feature on every system without having to touch all the HyperLaunch inis, this is where you do it.
Global HyperPause.ini: This file contains the same keys found in the system's HyperPause.ini, but will have the default settings that affect every system. If you want to turn on and configure a feature on every system without having to touch all the HyperPause inis, this is where you do it. See the HyperPause section for more information.
Global Emulators.ini: This file is where you want to define most, if not all your emulators. Each section in this ini will have an emulator name which is how the system links to the emulator you want to use. The emulators defined in this ini can be used for any system in your Frontend.
SystemName\HyperLaunch.ini: This file contains the same keys found in Global HyperLaunch.ini but is specific for the system. Default values for all the keys are use_global. If you change the value, it will only affect this system.
SystemName\HyperPause.ini: This file contains the same keys found in Global HyperPause.ini but is specific for the system. Default values for all the keys are use_global. If you change the value, it will only affect this system. See the HyperPause section for more information.
SystemName\Emulators.ini: This file contains your [ROMS] section with the Rom_Path and Default_Emulator keys. It can also contain Emulator sections if you want to define an emulator specific to just this system.
SystemName\Games.ini: This file is the replacement for the old <exe> attributes and how games can be mapped to use different emulators from the default one defined for this system.
On your first launch of any new system, HyperLaunch will create all the default inis it needs for that system.
