Goffender Posted June 30, 2018 Posted June 30, 2018 I assume questions on how to go here not in feedback? So it sounds like Hardlink method of deployment is trying to be like MO. And Move Deployment ( experimental ) is the old way. Does that mean that with hardlink (default method ) Vortex will be required to be running in the back ground?
rmm200 Posted June 30, 2018 Posted June 30, 2018 On 6/30/2018 at 3:48 PM, Goffender said: I assume questions on how to go here not in feedback? So it sounds like Hardlink method of deployment is trying to be like MO. And Move Deployment ( experimental ) is the old way. Does that mean that with hardlink (default method ) Vortex will be required to be running in the back ground? Vortex is never required to be running in the background. And Hard Links are nothing like MO.
SkunkMonkey Posted June 30, 2018 Posted June 30, 2018 MO uses a home rolled "virtual" file system. Vortex uses Windows built in file linking. The advantage is that Vortex does not need to be running and any application you run will see your game as the modded version.
Goffender Posted July 2, 2018 Author Posted July 2, 2018 Ok, that IS cool. Also if I am understanding properly I can convert to Move Deployment later correct? Like once I am happy with the install.
Tannin42 Posted July 2, 2018 Posted July 2, 2018 move deployment tries to replicate the behaviour of hard links on filesystems that don't support hard links.It's generally going to be a more complicated and fragile system so I would strongly advise against using it unless hard links are not an option. Apart from compatibility there is absolutely no advantage to move deployment.
Goffender Posted July 3, 2018 Author Posted July 3, 2018 I thought move deployment was basically the old way where the mod is actually written into the data folder?
Tannin42 Posted July 3, 2018 Posted July 3, 2018 What's the difference between a hard link and an "actual file"? I can almost guarantee that you have a misconception about what hard links are. It's true that with move deployment the "original" file gets placed in the data directory and a custom "link" is instead placed in the mod directory so we can reverse the move, but from the user perspective there is no practical difference to hard linking. Any difference would be for the worse.
HeavenNZX Posted July 6, 2018 Posted July 6, 2018 Sorry, but does the "hard link" count as another "copy" of the file, using 2 times the disk space or it's more like a shortcut?
Grestorn Posted July 6, 2018 Posted July 6, 2018 No, no matter how many hard links you create for the same file, the file data is only stored once on the disk. This tool and its documentation might make it clearer: Link Shell Extension
Recommended Posts
Archived
This topic is now archived and is closed to further replies.