Moved Game files to new drive - Hardlink Deployment issue

[Rikuyo]

Hey,

So I moved my whole steam library into a new SSD where I want to keep all my games. It's my G: drive currently.

I'm not able to deploy as the method hardlink deployment is unavailable because: Filesystem doesn't support hard links.

Probably should've looked up some more info before moving stuff around, figured it would be as easy as relinking to the new paths, but I was obviously incorrect.

[HadToRegister]

Your SSD drive needs to be NTFS

Hopefully you PURGED before you moved steam, otherwise you physically copied the link as well

[rmm200]

One small addition.

If you move your game to a different disk, you must also move the mod staging folder to the same disk.

Have Vortex move it for you; don't try moving it yourself.

It does not matter where your Vortex Downloads folder is.

[Rikuyo]

Thank you, I'll make the necessary changes to my SSD, seems I might need to reformat it to NTFS as it was exFAT before (coming from an old MAC backup.)

[Rikuyo]

A

 

Hey,

So I moved my whole steam library into a new SSD where I want to keep all my games. It's my G: drive currently.

I'm not able to deploy as the method hardlink deployment is unavailable because: Filesystem doesn't support hard links.

Probably should've looked up some more info before moving stuff around, figured it would be as easy as relinking to the new paths, but I was obviously incorrect.

Ah, I also didn't purge before moving. Yikes. Could I purge once I move back?

[HadToRegister]

Thank you, I'll make the necessary changes to my SSD, seems I might need to reformat it to NTFS as it was exFAT before (coming from an old MAC backup.)

 

 

Move everything BACK before you format!

 

Uhm, if a IIRC what rmm200 said about copying or moving, what happens is Windows replaces the Hardlinks with the Actual physical Files, so, probably not

[Rikuyo]

A

 

Hey,

 

So I moved my whole steam library into a new SSD where I want to keep all my games. It's my G: drive currently.

 

I'm not able to deploy as the method hardlink deployment is unavailable because: Filesystem doesn't support hard links.

 

Probably should've looked up some more info before moving stuff around, figured it would be as easy as relinking to the new paths, but I was obviously incorrect.

Ah, I also didn't purge before moving. Yikes. Could I purge once I move back?

So I moved skyrim back to my old directory and now Vortex is giving me a message saying that 'Mods have been changed on disk' I've not hit " Apply Changes." Wondering what I should do here. Last time I moved skyrim vortex took care of everything.

The kicker is really that Vortex forces me to either apply the changes or quit vortex, so I don't have any room to maneuver within the actual program.

 

To give a bit more context here: I've been backing up and moving stuff around since I got ahold of an SSD that I was using for something else. I moved my steam library over, each game I moved over through steam. When I moves SkyrimSE over I launched Vortex and started relinking to the new directory paths, and I didn't get a message about how my 'Mods were Changed on Disk" to my knowledge, Vortex itself moved my files for me. I checked the SSD and saw my Mods folder in it. Currently, I made a copy of the folder but have not erased it from the SSD.

 

I once again moved my steam library to my original drive so I could reformat the new one to NTFS.

[rmm200]

When you copied your game directory using Windows, Windows replaced those small hard links with an actual copy of the mod.

As far as Vortex is concerned, those mods were replaced by someone else.

At that point I really recommend Purge from within Vortex, delete your game directory, and have Steam reinstall it.

Then you have to repair all those mods that Vortex though you changed. For each enabled mod, click the dropdown that says "Reinstall".

If all goes well, "Deploy" after that should get you going.