Vortex Mod Cycling Problems can't fix

[Dragslor]

I got a mod cycling problem, but I don't know when it happened when I changed dependencies. So I clicked on show at "Mod rules contain cycles" but with this cycle overview(Attached to this post)...I can't really solve anything because it always just shows such a small portion. And I tried to zoom out or make it bigger but nothing works.
Anybody knows what to do? Can you zoom out somehow or move in the window?

Thanks for the help!

PS: The cycle detail shows that there are several mods in this cycle conflict, So I cant really tell from the written information either, where the cycle is.

[HadToRegister]

Every single one of those orange lines is a bad cycle, read the instructions at the top of the screen and get clicking on those lines to remove the rules

Are you trying to manually sort your ESPS, because this usually only happens when someone tries to force THEIR load order on Vortex, rather than letting Vortex sort it for them.

[Dragslor]

I was following a tutorial and set up Dependencies as they showed, but there were still conflicts so I set up the rules that were missing and suddenly after 1 change there were all these cycle problems. I try to remove all of those rules and try again

[HadToRegister]

I was following a tutorial and set up Dependencies as they showed, but there were still conflicts so I set up the rules that were missing and suddenly after 1 change there were all these cycle problems. I try to remove all of those rules and try again

 

 

Which tutorial was it?

I'd like to watch it

[Dragslor]

Okay, I fixed it, I removed all those cycle conflicts and made my own dependencies rules on those that were missing rules after that and now it works...I really don't know what was the problem before, thank you ^^'
It was this:

[HadToRegister]

I wouldn't recommend following that video after 22:00 minutes, because for some unknown reason, he sets up dependencies for Non-Conflicting Mods.

He only shows one mod with a Red Lightning Bolt, and instead of sorting the mods by UNSOLVED (red lightning bolts) he sorts them by "Conflict" which is wrong, because it's going to show both SOLVED and UNSOLVED conflicts.

There was no need for that big long list of LOAD BEFORE / LOAD AFTER if he did it properly and only solved the Red Lightning Bolt.

Don't follow that Video, he was having you create a ton of unnecessary rules, that's why your cyclic rules looked like a bird's nest.

But, glad you got it straightened out now.

In the future, only worry about the RED lightning bolts, not the green ones like the video incorrectly shows.

[BigBizkit]

I wouldn't recommend following that video after 22:00 minutes, because for some unknown reason, he sets up dependencies for Non-Conflicting Mods.

 

I am not sure that is actually what is shown.

 

I think Ultimate Immersion is simply going through the list of mods with resolved conflicts to show the rules he has set up, all of which appear to be addressing file conflicts (i.e. the rules are not superfluous).

 

That being said, I am not sure why you would leave "No rule" on some of the mods conflicting with SMIM on SMIM's side, and rather address them on the other mods' side. You can ofc do that, and it works just as well, it's just more confusing and harder to maintain.

 

I believe achieving what UltimateImmersion is showing here would be much easier in Vortex 0.17.x with the "Multiple" conflicts view.

 

Likewise, the new and improved UI for cycle resolution that 0.17.x has is easier to understand than what OP is showing in their screenshot.

 

 

Long story short: Ultimate Immersion is not doing it wrong per se, but it seems that it would be fairly easy to slip up and add redundant rules which would result in a cycle (or several). The good thing is that with Vortex you can always undo these without having to reinstall any mods.

[HadToRegister]

 

I wouldn't recommend following that video after 22:00 minutes, because for some unknown reason, he sets up dependencies for Non-Conflicting Mods.

 

I am not sure that is actually what is shown.

 

I think Ultimate Immersion is simply going through the list of mods with resolved conflicts to show the rules he has set up, all of which appear to be addressing file conflicts (i.e. the rules are not superfluous).

 

That being said, I am not sure why you would leave "No rule" on some of the mods conflicting with SMIM on SMIM's side, and rather address them on the other mods' side. You can ofc do that, and it works just as well, it's just more confusing and harder to maintain.

 

I believe achieving what UltimateImmersion is showing here would be much easier in Vortex 0.17.x with the "Multiple" conflicts view.

 

Likewise, the new and improved UI for cycle resolution that 0.17.x has is easier to understand than what OP is showing in their screenshot.

 

 

Long story short: Ultimate Immersion is not doing it wrong per se, but it seems that it would be fairly easy to slip up and add redundant rules which would result in a cycle (or several). The good thing is that with Vortex you can always undo these without having to reinstall any mods.

 

 

 

I use 226 mods in Skyrim SE, and 252 in Fallout 4, and neither of my Rules Lists are nowhere near as long as in that video

I don't know why he didn't sort by UNRESOLVED, rather than CONFLICT, as we could've seen all of the Red Lightning bolts.

 

 

[Dark0ne]

I think the point is that he had already resolved all of the conflicts. In the video he needed to show how he'd resolved those conflicts so that the users of the video could setup their Vortex like he had, so that's why he switched to "conflicts" rather than "unresolved".