Jump to content
Download Section Back Up, Navigate the Right Hand Menu to find files, ignore the 0s

Hyperlaunch Installation Best Practices


onesikcoupe

Recommended Posts

Just have a quick question regarding best practices when installing Hyperlaunch and HyperlaunchHQ. Should these two be placed in the root of the Hyperspin directory (folder) or in a subdirectory (folder) or are there any advantages or disadvantages of a subdirectory?

TIA

SIK

Link to comment
Share on other sites

Best practice is Hyperlaunch in a folder within Hyperspin, and Hyperlaunch HQ in a folder within the Hyperlaunch folder. But you could put them where you like, but I see no reason to.

Check out my mame video guide if you need more help.

Link to comment
Share on other sites

Hyperspin/Hyperlaunch/HyperlaunchHQ

the good thing about putting Hyperlaunch in the Hyperspin folder is that you can use a relative path in your Hyperspin settings ini file.

Hyperlaunch_Path=HyperLaunch\

This is the same folder structure you will find when you update your files using GIT. It makes it very easy to upgrade when you simply copy and past the Hyperlaunch folder into your Hyperspin folder.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...