Why is vortex so confusing?

[SirDanest]

I used to think that the only thing stopping mod organizer from completely dominating was that it was slightly more complex than NMM. But apparently that's not the case.

[Zanderat]

The thing is, I don't find Vortex complex. Yes, it is different from NMM. I think that is the crux of the issue. Most casual mod users don't have the patience to learn new things or bother to to read the documentation.

[HadToRegister]

I used to think that the only thing stopping mod organizer from completely dominating was that it was slightly more complex than NMM. But apparently that's not the case.

 

 

And what experience do you have with Vortex?

 

NMM isn't difficult at all, because he doesn't have ANY features except as a glorified Download Interface with a Mod Unzipper built in.

[DavinaJo]

I might was well jump on this bandwagon too, since I as well have problems with Vortex, at least mine come from fustration trying to meet Conflict Manager's requirements to fix the conficts Vortex seems to think exist (that don't exist in either NMM or Wryebash (due to LOOT sorting the Load Order) I've tried using Gophers Tutorials on Vortex and most of it seems straight forward however when it comes to the Conflict Manager i just can't wrap my head around it.

 

to give an example Oblivion under NMM you have Oblivion.ESM followed by Shivering Isle followed by knights of the nine followed by all the smaller DLC . normally you add Unofficial patches and they're supposed to be placed after the Game or Mod they affect, Under NMM and Wryebash this is allowable and the game runs fine but you try and do that in Vortex and Vortex's Rules won't let you. (at least it doesn't for me) and I've haven't got the faintest clue how load order rules that Vortex uses works.

 

 

Before Vortex you install your mods, run LOOT or BOSS let the changes take affect and your pretty much good to go, for some reason (beyond this country bumpkin's comprehension ) Vortex doesn't allow you to do that.

 

 

I really wanted to like Vortex and MO as well but neither are a "set it and forget it" mod manager, I want to be able enjoy the modding process not belabour over the minutia which is exactly what this conflict manager in vortex is and does.

 

 

 

@1ae0bfb8, ("it's only confusing if your're thick") you may want to remember that the next time your totally fed up and frustrated by someone else's ideas of how things should be done, there is a word in the english dictionary that means single or different, that word is indivdual and just because you may get something that doesn't mean others will. and you shouldn't be putting them down for it.

 

Thick as defined by the Mirriam-Webster Dictionary "5. Thick - Obtuse or Stupid. (This could be taken as an aborgation of Site Rules.)

[HadToRegister]

I might was well jump on this bandwagon too, since I as well have problems with Vortex, at least mine come from fustration trying to meet Conflict Manager's requirements to fix the conficts Vortex seems to think exist (that don't exist in either NMM or Wryebash (due to LOOT sorting the Load Order) I've tried using Gophers Tutorials on Vortex and most of it seems straight forward however when it comes to the Conflict Manager i just can't wrap my head around it.

 

to give an example Oblivion under NMM you have Oblivion.ESM followed by Shivering Isle followed by knights of the nine followed by all the smaller DLC . normally you add Unofficial patches and they're supposed to be placed after the Game or Mod they affect, Under NMM and Wryebash this is allowable and the game runs fine but you try and do that in Vortex and Vortex's Rules won't let you. (at least it doesn't for me) and I've haven't got the faintest clue how load order rules that Vortex uses works.

 

 

Before Vortex you install your mods, run LOOT or BOSS let the changes take affect and your pretty much good to go, for some reason (beyond this country bumpkin's comprehension ) Vortex doesn't allow you to do that.

 

 

I really wanted to like Vortex and MO as well but neither are a "set it and forget it" mod manager, I want to be able enjoy the modding process not belabour over the minutia which is exactly what this conflict manager in vortex is and does.

 

 

 

@1ae0bfb8, ("it's only confusing if your're thick") you may want to remember that the next time your totally fed up and frustrated by someone else's ideas of how things should be done, there is a word in the english dictionary that means single or different, that word is indivdual and just because you may get something that doesn't mean others will. and you shouldn't be putting them down for it.

 

Thick as defined by the Mirriam-Webster Dictionary "5. Thick - Obtuse or Stupid. (This could be taken as an aborgation of Site Rules.)

 

The person you mentioned at the end of your post that was complaining made it quite obvious that they hadn't even bothered reading any of the tutorials or watched any of the built in videos, then came here to complain because they couldn't work Vortex.

 

 

LOOT is built into Vortex.

The reason those conflicts "don't exist" (THEY DO) in NMM, is NMM doesn't say anything about them conflicting, because it doesn't care, and allows you to have the most dysfunctional load order possible because it doesn't warn you of conflicts.

 

I can already see that your problem is you're trying to force Vortex to have YOUR Hand set load order, while LOOT is telling you that you have plugins in your load order in the wrong place.

If you just remove the rules you set, and hit SORT, your load order will be sorted by LOOT and all set to go.

 

Also, don't go putting every mod you have into GROUPS, GROUPS are also a way to sort mods, they aren't some useless categorization like NMM does.

 

Let Vortex sort your mods, and it will work out

[HadToRegister]

Also, you can't use Vortex or any modern mod manager with Oblivion Mods, because they were made back when manually installing was still a thing, and the likes of OBMM and WryeBash were just starting to show up on the scene.

I wrote a lengthy article about how I spent a couple of weeks manually converting Oblivion mods to work with the likes of NMM and Vortex etc..


Vortex and Oblivion, an experiment

[HadToRegister]

FWIW, I download my mods en masse, over a 100 or more, and then install them one after the other, ignoring all conflict warning etc.
Then, when I'm done installing, I click on each red lightning bolt, and start using the LOAD BEFORE or LOAD AFTER setting by following the instructions on the Mod Page's Descriptions that say to either "load my mod after SO and So's Mod" so I immediately pick LOAD AFTER.

For PATCHES, a good rule of thumb is, a PATCH will ALWAYS LOAD AFTER the mod it is patching