Speaking of mklink I was wondering if mounting a drive to a folder would allow me to keep hyperspin organized to one directory. I have a Z: drive mounted at startup with shortcut in "C:\Users\\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup" with target set to "C:\Windows\System32\subst.exe Z: "F:\Hyperspin Drive"" I haven't gotten around to extracting all the hyperspin archives with packs yet but I'm assuming it would work. I like to keep the root of my drives organized and this seems like a viable solution. EDIT: Dean, sure you know this I added all the details for other hyperspin users. I'm 99% sure it will work as long as your doing all your linking threw the Z: drive and not the source directory which is why you would want mounting on startup or at least mounting before you start Hyperspin or RocketLauncherUI.
@@deanseavy7316 Ya so extracting all Hyperspin files into a dedicated Hyperspin Directory called "Hyperspin Drive" in my case is it on my F: drive I can then mount that directory as a virtual drive. In this case I used Z with command "C:\Windows\System32\subst.exe Z: "F:\Hyperspin Drive"" This allows me browse F:\Hyperspin Drives contents by accessing Z: drive. It's the same idea of mounting a network drive but local. The only issue with this is making sure you use the Z: when configuring any hyperspin/rocketlauncher and not your source directory.
Speaking of mklink I was wondering if mounting a drive to a folder would allow me to keep hyperspin organized to one directory. I have a Z: drive mounted at startup with shortcut in "C:\Users\\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup" with target set to "C:\Windows\System32\subst.exe Z: "F:\Hyperspin Drive"" I haven't gotten around to extracting all the hyperspin archives with packs yet but I'm assuming it would work. I like to keep the root of my drives organized and this seems like a viable solution.
EDIT: Dean, sure you know this I added all the details for other hyperspin users. I'm 99% sure it will work as long as your doing all your linking threw the Z: drive and not the source directory which is why you would want mounting on startup or at least mounting before you start Hyperspin or RocketLauncherUI.
But the root is organized. Everything is in the hyperspin folder. Maybe I am missing something
@@deanseavy7316 Ya so extracting all Hyperspin files into a dedicated Hyperspin Directory called "Hyperspin Drive" in my case is it on my F: drive I can then mount that directory as a virtual drive. In this case I used Z with command "C:\Windows\System32\subst.exe Z: "F:\Hyperspin Drive"" This allows me browse F:\Hyperspin Drives contents by accessing Z: drive. It's the same idea of mounting a network drive but local. The only issue with this is making sure you use the Z: when configuring any hyperspin/rocketlauncher and not your source directory.
Simple find and replace in the rocket launcher settings ini's