Vortex is now re-deploying all mods everytime I enable or disable one

[TennesseeTuxedo]

At some point a few days ago I got one of those error messages from Vortex that some files (many actually) supposedly had changed without Vortex.  They did NOT change.  It gave me that scary dialog asking if I want delete or revert my files.  I have selected "delete" before and watched it delete my mods, leaving nothing but empty folders.  So, learning from that horror, I selected the "restore"/"revert" or whatever it says that is not delete.  Everything works in game, all my mods are fine.  However, ever since then, enabling or disabling any mod now causes Vortex to re-reploy every mod.  I went from seconds to enable a mod to 2-3 minutes.  I re-installed Vortex but that does not reset it's database or anything, so it didn't change any behavior.  It seems like it thinks there are perpetual changes, is there anyway to reset Vortex without burning all mods and starting from scratch?

 

 

 

[showler]

There should be some settings in the settings menu about automatic deployment.

That said, if you enable or disable mods you should re-deploy unless you are certain there are no conflicting files that need to be updated.

[TennesseeTuxedo]

I have many mods that are just .esms.  I published a mod yesterday that is just a single .pex script.  Enabling or disabling those mods do not overwrite anything (not counting what happens in the plugins.txt).  So it does not make sense for example, that disabling a single esm mod would require re-deploying every mod I have.

And again, it has not done that before for  the months/years I have been using Vortex, and since Starfield's launch.  After that strange error message, that reported just about every mod had changed, it now takes 2-3 minutes to enable/disable any mod, where before it was in seconds.  I've always had auto-deploy on.  That setting only controls when it deploys.

Is there some way to reset vortex or it's state so it can kind of re-inventory all your mods, hopefully without have to re-install them all?

I'm into the Roaming/Vortex folder looking to see what meta information is there and re-reading the logs files.  I know in worst case I have to uninstall all mods, burn Vortex to ground, delete everything Vortex, then re-install Vortex and all my mods again.  I'm hoping there is something I can do short of that.

[Pickysaurus]

Deployment re-runs because Vortex needs to make sure that when a mod is removed all the content actually deployed to your game folder matches what should be there. 

 

As an example, if you had two files that conflicted and disabled the "winner", the "losing" file should be deployed in the absence of its replacement. 

 

Showler already pointed out that you can disable the automatic deployment behaviour in your settings. 

[TennesseeTuxedo]

As I mentioned, I already know about automatic deployment, I've been using this excellent tool that I'm generally very satisfied with for a while, well before Starfield. 

This is behavior that started after the error message where Vortex erroneously detected that most of my mods had changed "outside Vortex" which was not the case. 

As a desperate move, I opted into the BETA and updated to that.  It now moves twice as fast as it did, so that dislodged whatever problem it had.  I saved my logs, including the one I attached to the original thread that I guess nobody looked at before they "diagnosed" my problem as "user error".  I want to compare new BETA logs to that to see what steps were taking longer then vs now so I can pinpoint the problem.  However it appears the BETA doesn't make logs, and can't find where to turn that on.  I might make a thread for that, not sure if that is by design due to being a BETA or a bug.

[TennesseeTuxedo]

Indeed Vortex deploys each time.  Due to another Vortex problem that adds a minute to deploying a mod, I had just NOTICED this more.  I compared logs from 10 days ago to today and can see there are two new events in the log that consume all the extra time.  I will create another thread to address that.