Jump to content

Moved everything to a new SSD and no mods work


aaa21445

Recommended Posts

Last month I bought a new SSD and set that SSD to become my new C: drive. I moved my entire steam folder, games and all, to my C: drive and moved Vortex and its appdata to C:drive as well. Both were moved manually (which was a stupid decision). Thats when my mods stopped working.

 

I got an error when I opened vortex which said no uninstall key, so I reinstalled Vortex.
I got a prompt when I opened up Vortex saying that some 50+ mods were changed outside of vortex and me being the dumbass I am saved those changes thinking it was nothing.

Whenever enter the game, Skyrim treats it as if no mods were installed. I used SKSE to open Skyrim so thats not the issue.

The game essentially acts like a vanilla install with textures missing on retextured vanilla armors and custom ones gone. Only exception from what I could find is the female bodyslide which is still how I built it though Bodyslide studio a while back.

 

TL;DR: I f***ed up. How do I fix this?

 



Link to comment
Share on other sites

So how do I fix this? Can I fix this?

 

 

Well, I'd say wait for the official word from the Vortex developer on this, but he doesn't go int he game forums, just in the Vortex support forums.

 

But from what I gather, you'll have to delete you appdata folder and reinstall Vortex, because by moving the Files and Folders manually, you've not only copied the hardlinks, but also made a physical copy of the linked files, which is taking up twice as much space now.

 

Let me see if I can get someone in here to help

Link to comment
Share on other sites

Hello? Hello? I got poked...

 

Side item first. Download a very useful tool: NTFSLinksView. This gives you a way to see what is a hard link, and what is an actual file:

https://www.nirsoft.net/utils/ntfs_links_view.html

 

When Steam installs a game, what you see is what you get. The game and all mods manually installed are real files.

Now Vortex is tricksy... What you see is not what you get. Your mod only exists in the Mod Staging Directory.

What gets placed in the game /Data directory is just a hard link back to the Mod Staging Directory.

If you run NTFSLinksView on your game /Data directory at this point, you will see all the hard links.

Now what you need to be aware of, when Windows copys a hard link, it does not copy just the pointer. It copies the file the pointer points to.

This is known as a Deep Copy, and is true if you are moving the game or just making a backup.

Net result: The game grows to the size of the original game plus all the enabled and deployed mods from Staging. So a LOT bigger.

Side effect: Vortex loses control over all those hard linked mods. It is as if you manually overlaid Vortex' hard links with actual files.

 

Proper procedure: Before you move a game directory, or make a backup - issue Purge from within Vortex. That removes the hard links - and Windows will copy only the game.

After the move, Deploy will restore them.

 

Now back to the issue at hand. You moved the game without Purge. Windows helpfully populated your game directory with real files for all those mods.

Use NTFSLinksView on your moved game directory. No hard links - but a lot of files.

 

And the bad part. There is no quick fix, but the options are not too bad.

1) Start Vortex and tell it where the game is now.

2) Issue Purge to get Vortex out of the picture.

3) Clean up your game directory. Delete everything not installed by Bethesda. That includes Data/Scripts, Textures, and Meshes directories. And anything that looks like a mod.

4) Have Steam validate your game. That will replace anything you deleted by mistake. Or you could just have Steam reinstall the game at the new location. You need to tell Steam the new location anyway.

5) Bring up Vortex again. Make sure the game runs from Vortex with nothing deployed; i.e. you fixed any dashboard shortcuts.

6) Back when you saved changes - you destroyed the Staging copy. For each enabled mod, you will need to select the Reinstall dropdown. It is quick.

7) Deploy. With a bit of luck, and maybe some last minute tweaking, you should be back in business.

 

And hang onto NTFSLinksView. It can answer a lot of links related questions.

 

Enough for this book. Happy modding!

Edited by rmm200
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...