DIscrepancy between General Rules and Single Files Rules

[Behelit79]

Hello
I'm having a lot of problems with Vortex lately, i set normally my global rules of deployment but then if i go and manage conflicts on a single file level i can see that sometimes my general rules are already not followed.

I post here one example of what's happening to me with Skyrim SE:

I set Fabled Forest to deploy globally after Fixed Mesh Lighting




But if i look at priority on a single file conflict level, even if Vortex knows that Fabled Forests is the default mod with the deployment priority, many files are listed with the other mod priority.



Switching rules globally doesn't refresh those files status, the only way is changing them manually one by one...
But having a huge modlist, experimenting priorities to chose which mod i would like to use becomes an impossible task.

I even tried the "clear all rules" option and now i'm setting them again from the start.
It seemed everything fine untill it started again behaving like that, after the rules increased.

 

Edited June 29 by Behelit79

[vortexposer]

Try resetting the involved mods folders install to clean/clear out its recent memory, so-to-speak. Might even require full uninstall vs reinstall mod option. Can't remember which fixed it for me. Or whether it was normal "override" or recent mod type conflict "override" which triggered the unresponsive condition to change the incorrectly applied settings.

[Behelit79]

1 hour ago, vortexposer said:

Try resetting the involved mods folders install to clean/clear out its recent memory, so-to-speak. Might even require full uninstall vs reinstall mod option. Can't remember which fixed it for me. Or whether it was normal "override" or recent mod type conflict "override" which triggered the unresponsive condition to change the incorrectly applied settings.

Ok, i tried by completely removing Fabled Forests and installing it again, applied a global overriding rule and it correctly shows in the per file conflict menu.
Then i tried to globlly swap the priority to the second mod and it almost worked, many files correctly changed priority but others not.

Don't know if it's related, but it seems almost all the files that didn't correctly change priority are files that have a third or more mods involved in the priority menu.

[Behelit79]

Since i've found more instances of this behavior in the new heavy modded game profile i was trying to set up, and since Vortex doesn't provide a fast way to know which mod or single file override the others, my solution was to simply uninstall everything and build my new playthrough with Mod Organizer 2.

In the end Vortex is fine as it is but better suited for easy / short modlists so you can even ingnore these bugs.