CommunistNinja

Okay, this was helpful. It narrowed it down to a conflict with F4SE. There were a handful of loose files mods that were conflicting with files in F4SE. I simply re-packed those mods back into their respective ba2 archives and the purge-loop stopped. Fallout 4 has an issue loading more than ~255 archives and, after I unpacked a bunch of smaller mods to reduce the archive count, Vortex s#*! the bed because there is a conflict between an "engine injector" mod (F4SE) and a normal "unspecified" mod. For anybody having this issue, crosscheck your load order for conflicts with F4SE. If you have conflicts, simply use "Cathedral Assets Optimizer" to pack the conflicting mods into an archive so that Vortex won't detect the conflict and s#*! the bed.

"A bad mod setup" is a vague thing to say. What exactly is a "bad mod setup" that would cause this purge-loop? What is a "cross-modtype" conflict? I've literally got a save with like 25 days on it, still playing with a modlist from nearly a year ago, but it's only been doing this purging cycle for the past few weeks.

Did you ever get an answer for how to turn off this auto-purging? It's insane that it takes me like a half hour to simply enable a half-dozen mods, just sitting and waiting for Vortex purges is not the ideal way to spend my days off.

This is a serious problem, especially for folks with big mod lists. In addition to all the complaints mentioned in this thread, if I, for example, too quickly enable (or disable) multiple mods by quickly pressing the disable/enable buttons before Vortex has finished doing its purging, Vortex will fail to properly handle the game's .ini files, reverting them back to vanilla (or whatever version Vortex uses), forcing me to go back through and dig up every .ini setting one-by-one, from intro music of the vanilla game to enb and physics settings. As already stated, this is happening on both my rigs--the HTPC and the gaming PC. I've had some luck by creating a new profile and added a couple hundred bug-fix mods and others for testing. The purging issue didn't happen in that case, but switching back to the old profile brings back the purge issue. I've already attached a set of log files, but there's been no fix. It's weird that this topic is labeled as though it has a "solution." This problem is destroying carefully curated mod lists that people have spent weeks putting together. It's been more than a couple weeks since this issue has been raised. I've been a long-time user of Vortex and I generally prefer it because I really enjoy some of the "collections" available but, if this doesn't get fixed soon, I'll have to switch over to MO2 because Vortex is proving to be so broken that it's unusable.

Here are the last 4 logs. vortex4.zip

Well, it's now happening on both my my gaming PC and now on my HTPC. So, both instances of Vortex existing on two entirely different PCs are now purging mods like a 90s teen girl with anorexia who purges her lunch. I didn't make any changes to the HTPC today. There were no updates and I made no changes to Vortex, aside from installing a few dozen mods, running xedit a few times to make some patches, and some gameplay to do some testing. Is there a way to rollback to an earlier version of Vortex without borking my modlists?

Great! However, this doesn't answer the primary problem of Vortex purges. I've got v1.11.4 installed on two different PCs--one on the primary gaming PC and the other on the HTPC. The purging issue is only a problem on the primary gaming PC. It's not doing this loop on the HTPC. So far as I can tell, each instance of Vortex is the same. I don't see any settings as set differently. The main difference between the two is that Vortex manages more games and different profiles on the gaming PC. The HTPC only manages Skyrim and Fallout 4 on the htpc.

Am I now the 6th person with this problem? Every time I install, remove, enable, disable, or re-install a mod, Vortex automatically follows with the purge operation. Purging and deploying 100 of gigabytes of data just to tweak an .ini file is super annoying, probably excessive wear and tear on an ssd too.

I think it just means that the plugin is "disabled" in the plugin list within Vortex. I'm not sure how Vortex does this, though. For example, if I create a plugin with xedit, it gets placed in Skyrim's data folder and then shows up in Vortex, but Vortex can enable or disable that plugin. How Vortex "tells" the game to load or not load that plugin--I don't know.

Thanks for looking into this. I didn't find much on the topic elsewhere and was beginning to think that I was the only one with the problem. This slowdown cripples the fun, turning some little tweak like a texture file into an hour-long ordeal where I can go and make some coffee and play with the cats before returning to the game. I only have 2 "disabled" plugins and they need to stay in as empty files because I have dozens of sort rules attached to them. They are old smash patches that I've emptied and, if I remove them, I'd have to redo all those manually added sort order rules. (Score one for MO2's plugin sorting.) If this is a problem with LOOT, why would switching over to the 1.4 beta version of Vortex possibly be a fix, though? I'm hesitant to upgrade to a beta and not even know for sure if there is going to be any advantage. It seems more like LOOT problem, probably something that nobody really bothered to address because 1000+ mods is kind of crazy.

Is there a way to speed up the load order sorting of Vortex's implementation of LOOT? I'm running over a thousand plugins and find that sorting can sometimes take more than 20 minutes. I use a R7 3800x cpu and notice that, whilst sorting, Vortex is only using about 10% of the cpu. Is there a way to make Vortex's LOOT use more cpu threads? Adding mods to the game is fun until I get to around 600+ mods. The sorting process gradually gets slower as I add more plugins and rules, but having to wait for this process to finish is such a waste of time, especially when I have all these idling cores and threads. The deployment of mods is wonderful. I can see that Vortex uses far more cpu resources whilst deploying. It only takes a minute or so to purge and deploy nearly 300 gigs from the nvme.2 drive, but then it just takes so loooong to sort the plugins.

I'm having this same problem at the Elysium Estate workbench. I think it may have something to do with the "general stores" and "dynamic auto sort" mods. Have you found a solution?