Former Workaround for "Failure to Deploy" No Longer Works

[Vyxenne]

I have previously reported that Vortex was failing to deploy hundreds (thousands at that time) of files for the same reason as everyone else here is reporting- "it must be locked by another application." The logs show that the files in question are all Bodyslide files. The reason Vortex "can't handle it" is that my Gaming drive is an SSD and since I have no need whatsoever of SSD speed in Bodyslide and much need for every byte of space I can clear on my SSD, I created a Caliente Tools Junction Link on my SSD and all my Bodyslide files are on another drive- a traditional HDD with terabytes of available space.

 

The responses I got were not helpful- one questioned why I would want to move Bodyslide off of my SSD :ohmy: and said I should just deal with it, that mine was a unique problem and I shouldn't expect Vortex to do anything about it, which of course it is not- apparently that responder has never dealt with a limited-size SSD before. The other two responders hadn't read my problem statement. I can no longer find my post because it was weeks ago and it doesn't show up under my activity on my profile.

 

I worked around Vortex's destructive behavior by deleting all of Vortex's "xxxxxxxx.osd.vortexbackup" unfiles and manually copying all my Bodyslide files into the (Junction-Linked) Bodyslide folders on my SSD. This worked fine- Vortex no longer complained about those thousands of files "not deploying" and everything worked great. Now, since last week's update, this is no longer the case: Vortex "digs up" the mod 7z Archive and deletes the actual nif, osd, osp and xml files I just spent 2 hours hand-installing and then "reinstalls" all the useless "xxxxxxx.nif.vortexbackup" not-files in their place.

 

So I give up. Nobody seems to care that this is an absurd failure on Vortex's part or that absolutely everyone using an SSD for games will sooner or later have disk-space issues. So I am reduced to removing the 7z mod archives from Vortex's staging folder (or removing the Bodyslide files from them) to work around Vortex's inablilty to cope with a simple Junction link.

 

Does anyone have a better idea for dealing with this? As you can probably tell, I am quite angry right now over Vortex undoing my 2 hours of manual work in under 10 seconds when (a) we shouldn't have this problem to start with since even Windows XP apps know how to deal with Junction Links; and (b) the previous version of Vortex did not do this- once I deleted all the *.vortexbackup files and replaced them with actual usable files, Vortex did not then undo my work every time I deployed mods.

 

Please overlook my anger and frustration and just give me some response/solution that doesn't start with "why are you moving your Bodyslide files off of your SSD? Nobody else does this, it's a problem unique to you and therefore there is no reason for Vortex to take your unique problem into account." If Vortex didn't require me to keep my Utilities (including Bodyslide, but also FNIS, SSEEdit, etc.) files on my SSD to start with and just let me set a pointer to them in Vortex Settings, this wouldn't be an issue.

 

Thanks. :wub:

[HadToRegister]

Don't use junction links, you're trying to make Vortex do something it can't do, and blaming Vortex for it.
Also, I'm not sure why you're jamming your game files on an SSD, when you have a drive with "terabytes of available space" that you could put your game and mod staging folder and not have to go through all of those gymnastics with Junctions.

That would be the sensible solution, instead of fighting with Vortex to do something unconventional for Vortex.

[Emsky968]

Currently having a deploy issue as well though I would be highly shocked if it had anything to do with body slide. I am also curious as to why you think Vortex requires you to keep your tools on an SSD. I have all of my Skyrim stuff stored on my storage drive for the very reason that there wouldn't be enough space. I can agree with you that the fact this is still an issue is pretty dumb. My issue is recent though I am finding a ton of topics on it with no real solutions. I too had all my work of setting everything up destroyed in all of 10 seconds, haha. Your anger is well placed I think. I like vortex the best of all the mod mangers which is the only reason I am willing to put forth the effort to fix this. I just wanna play the game, ya know?

[HadToRegister]

Currently having a deploy issue as well though I would be highly shocked if it had anything to do with body slide. I am also curious as to why you think Vortex requires you to keep your tools on an SSD. I have all of my Skyrim stuff stored on my storage drive for the very reason that there wouldn't be enough space. I can agree with you that the fact this is still an issue is pretty dumb. My issue is recent though I am finding a ton of topics on it with no real solutions. I too had all my work of setting everything up destroyed in all of 10 seconds, haha. Your anger is well placed I think. I like vortex the best of all the mod mangers which is the only reason I am willing to put forth the effort to fix this. I just wanna play the game, ya know?

 

 

Is your Deploy issue because of the newest version of Vortex?

Do you have your Mod Staging Folder and Game on the same drive?

[Emsky968]

 

Currently having a deploy issue as well though I would be highly shocked if it had anything to do with body slide. I am also curious as to why you think Vortex requires you to keep your tools on an SSD. I have all of my Skyrim stuff stored on my storage drive for the very reason that there wouldn't be enough space. I can agree with you that the fact this is still an issue is pretty dumb. My issue is recent though I am finding a ton of topics on it with no real solutions. I too had all my work of setting everything up destroyed in all of 10 seconds, haha. Your anger is well placed I think. I like vortex the best of all the mod mangers which is the only reason I am willing to put forth the effort to fix this. I just wanna play the game, ya know?

 

 

Is your Deploy issue because of the newest version of Vortex?

Do you have your Mod Staging Folder and Game on the same drive?

 

It's all the same drive but different folders. After looking over all the other posts that have happened since the update that seems to be the leading factor. I really want to look at the log but I can't seem to find the right log. All I did was purge my mods after doing somethings and when I went to deploy the error messaged started and nothing will deploy. I've purged and deployed every now and then before the update and never once had an issue.

[HadToRegister]

 

 

Currently having a deploy issue as well though I would be highly shocked if it had anything to do with body slide. I am also curious as to why you think Vortex requires you to keep your tools on an SSD. I have all of my Skyrim stuff stored on my storage drive for the very reason that there wouldn't be enough space. I can agree with you that the fact this is still an issue is pretty dumb. My issue is recent though I am finding a ton of topics on it with no real solutions. I too had all my work of setting everything up destroyed in all of 10 seconds, haha. Your anger is well placed I think. I like vortex the best of all the mod mangers which is the only reason I am willing to put forth the effort to fix this. I just wanna play the game, ya know?

 

 

Is your Deploy issue because of the newest version of Vortex?

Do you have your Mod Staging Folder and Game on the same drive?

 

It's all the same drive but different folders. After looking over all the other posts that have happened since the update that seems to be the leading factor. I really want to look at the log but I can't seem to find the right log. All I did was purge my mods after doing somethings and when I went to deploy the error messaged started and nothing will deploy. I've purged and deployed every now and then before the update and never once had an issue.

 

 

 

Yea, there seems to be some issues with the newest update.

According to Tannin42, it's OK to roll back to a previous version despite the warning

So just download an older version and you should be able to install it right on top of it

[Emsky968]

I

 

 

 

 

Currently having a deploy issue as well though I would be highly shocked if it had anything to do with body slide. I am also curious as to why you think Vortex requires you to keep your tools on an SSD. I have all of my Skyrim stuff stored on my storage drive for the very reason that there wouldn't be enough space. I can agree with you that the fact this is still an issue is pretty dumb. My issue is recent though I am finding a ton of topics on it with no real solutions. I too had all my work of setting everything up destroyed in all of 10 seconds, haha. Your anger is well placed I think. I like vortex the best of all the mod mangers which is the only reason I am willing to put forth the effort to fix this. I just wanna play the game, ya know?

 

 

Is your Deploy issue because of the newest version of Vortex?
Do you have your Mod Staging Folder and Game on the same drive?

 

It's all the same drive but different folders. After looking over all the other posts that have happened since the update that seems to be the leading factor. I really want to look at the log but I can't seem to find the right log. All I did was purge my mods after doing somethings and when I went to deploy the error messaged started and nothing will deploy. I've purged and deployed every now and then before the update and never once had an issue.

 

 

 

Yea, there seems to be some issues with the newest update.
According to Tannin42, it's OK to roll back to a previous version despite the warning
So just download an older version and you should be able to install it right on top of it

 

'll give it ago and report back.

[Tannin42]

 

Yea, there seems to be some issues with the newest update.

According to Tannin42, it's OK to roll back to a previous version despite the warning

So just download an older version and you should be able to install it right on top of it

 

 

To be precise: I said it's ok to roll back 0.18 to 0.17, I didn't say it's ok to roll back to older versions in general.

 

@OP We don't support manually creating junction points for staging files. We never said we supported this. I don't know why you thought we supported this because we never said we did.

This is not a failure of Vortex, you're trying to force Vortex to work like you think it should and it doesn't.

 

I'm not 100% sure what you're actually doing so just to clarify a few things:

a) You can not create a junction point from a different drive into a vortex staging folder and expect vortex to deploy those files, it's not possible.

b) If you're creating a junction point from your manually managed directory to the game directory that works, but you have to make sure Vortex never tries to deploy those same files

c) You seem to be suggesting Vortex "digs up" files from the archive. That's not the case, Vortex never touches the archives unless you're explicitly installing or re-installing the mod. If you purge mods, remove files from a staging folder and then deploy again, those files are gone and don't come back until you, the user, explicitly reinstall the mod.

[Rattledagger]

Hardlink deployment and files physically residing on a separate disk is not possible, this is true even if you're creating a junction link to the separate disk.

 

So you can do one of:

1: put the Bodyslide created files on same physical disk as the staging folder and use Vortex to add/remove these files to data directory.

2: manually add the files to data directory.

3: if Bodyslide puts all generated files into a Bodyslide exclusive sub-directory, you can manually create a junction from a sub directory of data to another disk.

4: don't use hardlink deployment, your only option with Vortex is USVFS, separate download from Nexus, but does only work with 0.17.x versions of Vortex.

 

I doubt 3 is fulfilled, but since it's quickly to check I've included this point.

 

1 and 2 gives the same end result, the Bodyslide created files are physically located on same disk as the data directory, but this is clearly something you don't desire.

 

This leaves option 4, using USVFS for deployment. I'm not sure you'll manage to successfully run Bodyslide, FNIS etc. in this case, since Vortex doesn't include the Override-directory Mod Organizer uses. If all files are successfully created, USVFS gives a large performance hit for starting the game, compared to hard-links. Example, starting full install of Ultimate Skyrim v3.4 off hdd takes 40 second if hard-links, 60 seconds if USVFS in MO2 and 80 seconds if USVFS in Vortex. Not tested USVFS in Vortex off SSD, but the two other gives 20 second hard-links and 40 seconds MO2. Version 4 of Ultimate Skyrim is 50 and 76 seconds.

 

So, USVFS gives a large penalty and Vortex gives an extra penalty on top for starting the game.

[piperman123]

@Tannin42

 

 

Yea, there seems to be some issues with the newest update.
According to Tannin42, it's OK to roll back to a previous version despite the warning
So just download an older version and you should be able to install it right on top of it

 

 

To be precise: I said it's ok to roll back 0.18 to 0.17, I didn't say it's ok to roll back to older versions in general.

 

@OP We don't support manually creating junction points for staging files. We never said we supported this. I don't know why you thought we supported this because we never said we did.

This is not a failure of Vortex, you're trying to force Vortex to work like you think it should and it doesn't.

 

I'm not 100% sure what you're actually doing so just to clarify a few things:

a) You can not create a junction point from a different drive into a vortex staging folder and expect vortex to deploy those files, it's not possible.

b) If you're creating a junction point from your manually managed directory to the game directory that works, but you have to make sure Vortex never tries to deploy those same files

c) You seem to be suggesting Vortex "digs up" files from the archive. That's not the case, Vortex never touches the archives unless you're explicitly installing or re-installing the mod. If you purge mods, remove files from a staging folder and then deploy again, those files are gone and don't come back until you, the user, explicitly reinstall the mod.

 

Sorry for chucking this on here but I can't find much on the topic, this does tie in with the question to a degree and I didn't feel it would need it's own thread.

 

I've been away from the scene for a while now and just came back to vortex. When I last used Vortex I'm pretty sure I had no trouble running a mod folder on another drive but now it seems this is not possible? I'm curious why this is. I get the limitations of hardlinks so I can understand why that needs to be used this way but I'm convinced I didn't have my mods folder and game on the same filesystem last time. Perhaps I was using the move deployment option at the time but this seems to not work now either, which seems to also only work if it's also on the same drive? Does Skyrim SE not recognize junctions or is there another reason Hardlinks are the only method the Nexus team or relying on?