Vortex keeps purging when I download and install a mod

[CommunistNinja]

On 6/21/2024 at 3:21 AM, Pickysaurus said:

The issue has been explained a few times in this thread. 

There are two main mod types for Bethesda games, one that deploys files to the game root and one that deploys files to the data folder.

You have (somehow) got a mod in your loadout that is deploying to the game root but it includes a file that is ALSO being deployed to the data folder directly by a different mod. 

If you show the "Mod type" column and look for anything that isn't default/blank you'll dramatically narrow down the possible causes.

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.

[anothersympathetic]

I am having the same issue... it purges repeatedly.   I am not interupting it.  I've watched it purge everything. Then I deployed everything.. after the deploy finished, it automatically started another purge

[belsaros]

So for me, I'm in a purgeloop where:
I need to deploy.
It runs FNIS
After FNIS is done I get a "failed to purge ini edits" warn, and a "There are unresolved file conflicts"
The unresolved file conflicts are between FNIS Data and FNIS Behavior. I tell it to put FNIS Data after FNIS Behavior and it then goes to purge everything again.
After the purge I have to deploy, the deploy runs FNIS, I get a unresolved file conflict and a failed to purge ini edits, then back to the purge, after which I need to deploy, the deploy runs FNIS......
I'm running Vortex 1.11.7

 

vortex.log

[Ryajore]

my culprit was SKSE, just decided to install it manually instead of through Vortex and problem solved.

[blesch]

On 6/6/2024 at 11:12 AM, TennesseeTuxedo said:

Did my final 10 minutes of Vortex purging last night, this time intentional by pressing the "Purge Mods" button in preparation for my move to MO2 which was much quicker than I thought it would be since you can just use the Vortex folders with your downloads and mods already in them.  Thank you @AugustaCalidia and @showler for the links for that.  It only took a couple hours and I am FREE!

I already miss the tighter integration with Nexus but when I downloaded and installed a mod in MO2 in seconds vs 12 minutes+ with Vortex (10 min purge scourge +2 min deploy time), that made up for all, it was so satisfying I was practically giddy.

I had a wonderful experience with Vortex and FO4 (although I understand this purge scourge may have metastasized to other games managed with Vortex), which is why I was so bullish with it for Starfield.  But Starfield Vortex experience has been miserable and I have lost many gaming hours wrestling with these various issues that seem to be getting worse.  This last problem of tacking 10 minutes of purging onto already bloated processes was the 3 ton brick that broke the camel's already sprained back.  But I am in a better place thanks to the community here.

Peace and enjoy Starfield all!

For me, it was Skyrim.

I finally got tired of it and stopped playing Skyrim entirely. Dropped my NM subscription for fast downloads, too, and just went to other games.

[Castyrael]

On 7/2/2024 at 8:13 AM, CommunistNinja said:

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.

THANK YOU SO, SO, SO MUCH. Vortex was driving me insane for weeks with any modification purging the whole load order. I did the same as you for reducing the archive count, since buffout 4 is not updated to NG, and ONE mod was conflicting with F4SE, repacked that mod, Vortex did a last Purge and now everything is back to normal. Thanks again.

[sid00745]

On 7/30/2024 at 2:53 AM, Ryajore said:

my culprit was SKSE, just decided to install it manually instead of through Vortex and problem solved.

I just got into the into the same issue, where it was stuck in a purge and deploy loop. To day I was just adding a few nee mods, and it suddenly had issues with fnis, I resolved that and then suddenly got thr purge deploy loop. After tial and error, I took your advice, removed skse from my vortex, manually installed it by following the readme instruction with the latest version, and boom fix the issue.

Anyone else who finds this thread and has/still dealing woth this issue. Try manually installing skse insted of letting vortex handle it as a troubleshooting soloution