Deployment failed and redundant mods.

[UnknownUnnamed13]

No matter what I seem to do, it gives me these two errors. (Skyrim Special Edition)

I'll have all of the 8 or so mods I have disabled except for SKSE Script Extender, and it'll do this. This is on a fresh install of the game, and Vortex.
I did recently install a new hard drive, but both the game and vortex are installed on the same drive (the new one) so I don't know if this part matters at all.

Help?

[rmm200]

Did you copy anything to the new drive from the old?

We will probably need the information posted here:

https://forums.nexusmods.com/index.php?/topic/7332636-how-to-post-request-support-for-vortex/

[UnknownUnnamed13]

  On 8/1/2020 at 10:29 PM, rmm200 said:

Did you copy anything to the new drive from the old?

We will probably need the information posted here:

https://forums.nexusmods.com/index.php?/topic/7332636-how-to-post-request-support-for-vortex/

I did try and copy everything over to the new drive, but I ended up uninstalling all the games, and reinstalling them. I ended up reinstalling Windows 10, so I had to reinstall all my programs anyways.

 

I'm on Vortex 1.2.20.

 

Are you thinking there might be some old mod data left on the old hard drive? If so, where would I check?

[rmm200]

If you Deploy mods to the game directory, then use Windows to copy that directory to a new drive, Windows will do a Deep copy.

All the Vortex hard links are changed to the actual mod code. This takes up a lot more space (you have two copies of all the mods),

and there is a good chance the mods will show up as redundant if you try to have Vortex manage them.

Note for the future: Purge your mods from Vortex before moving the game directory. That removes the hard links.

How to fix it: Issue Purge from Vortex now so it gets out of the way.

Clean your game directory. At this point, for you, it is probably best to delete the entire game directory and install from scratch.

Now, for each enabled mod in Vortex, hit Reinstall. That will restore your mods from the download directory.

Finally - hit Deploy - and you should be back in business.

[UnknownUnnamed13]

  On 8/2/2020 at 3:05 AM, rmm200 said:

If you Deploy mods to the game directory, then use Windows to copy that directory to a new drive, Windows will do a Deep copy.

All the Vortex hard links are changed to the actual mod code. This takes up a lot more space (you have two copies of all the mods),

and there is a good chance the mods will show up as redundant if you try to have Vortex manage them.

Note for the future: Purge your mods from Vortex before moving the game directory. That removes the hard links.

How to fix it: Issue Purge from Vortex now so it gets out of the way.

Clean your game directory. At this point, for you, it is probably best to delete the entire game directory and install from scratch.

Now, for each enabled mod in Vortex, hit Reinstall. That will restore your mods from the download directory.

Finally - hit Deploy - and you should be back in business.

I deleted all my mods, uninstalled Skyrim, and deleted all the Skyrim related files I could find.

 

I reinstalled Skyrim, downloaded and installed the unofficial patch, and got the same errors. I have no idea what to do at this point.

 

PS: I also did my best to check both hard drives for files.

PPS: I also took the time to uninstall Vortex, and delete all the Vortex related files I could find, reinstalled, to no avail.

[UnknownUnnamed13]

If this helps at all, here is my log.
https://drive.google.com/file/d/1s6FwQ4aMiLVBXbCrQqcj-xhx9h839OYu/view?usp=sharing

[ToSh6996]

I'll start my own thread

glad yours is working all sweet for you :D

[Tannin42]

In your log we have these lines:

  Quote

Fri, 07 Aug 2020 06:04:13 GMT - warn: failed to link link=Unofficial Skyrim Special Edition Patch - Textures.bsa, source=Unofficial Skyrim Special Edition Patch-266-4-2-3-1587854191, error=EXDEV: cross-device link not permitted, link 'C:\Users\spadr\AppData\Roaming\Vortex\skyrimse\mods\Unofficial Skyrim Special Edition Patch-266-4-2-3-1587854191\Unofficial Skyrim Special Edition Patch - Textures.bsa' -> 'F:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\data\Unofficial Skyrim Special Edition Patch - Textures.bsa'

So your staging folder is on C, the game is on F. You shouldn't have been able to deploy like that at all because the bethesda games only work with hard links deployment and hard link deployment only works if staging and game are on the same drive.
I have no clue why Vortex didn't warn about this, the fix for now would be to go to settings->mods and set your staging folder to be on F (you can probably click "Suggest" and it should put in a valid path on F)

[rmm200]

And for those of you that have 100GB or so in mods between Bethesda games like I do - don't leave the default in Appdata on the boot drive.

Put it someplace easy to see and keep track of - like F:\Vortex.

Don't get me wrong - Appdata is a great place for Vortex private data. Just not game stuff.

[UnknownUnnamed13]

  On 8/7/2020 at 8:28 AM, Tannin42 said:

In your log we have these lines:

  Quote

Fri, 07 Aug 2020 06:04:13 GMT - warn: failed to link link=Unofficial Skyrim Special Edition Patch - Textures.bsa, source=Unofficial Skyrim Special Edition Patch-266-4-2-3-1587854191, error=EXDEV: cross-device link not permitted, link 'C:\Users\spadr\AppData\Roaming\Vortex\skyrimse\mods\Unofficial Skyrim Special Edition Patch-266-4-2-3-1587854191\Unofficial Skyrim Special Edition Patch - Textures.bsa' -> 'F:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\data\Unofficial Skyrim Special Edition Patch - Textures.bsa'

So your staging folder is on C, the game is on F. You shouldn't have been able to deploy like that at all because the bethesda games only work with hard links deployment and hard link deployment only works if staging and game are on the same drive.

I have no clue why Vortex didn't warn about this, the fix for now would be to go to settings->mods and set your staging folder to be on F (you can probably click "Suggest" and it should put in a valid path on F)

Holy crud, this fixed it! Thank you so much!