Vortex sorting tool and LOOT

[sopmac45]

Still I do not know the difference between Vortex sorting and sorting the load order with LOOT. What is the difference ? Should I only use one of them or both ?

 

I can see when adding a new mod and after it has been deployed, the PLUGINS tab start to roll, meaning that Vortex is automatically sorting the list and placing the new mod where Vortex believe it should be and so far, I have not have any problem. So at this point, should I also re-run LOOT or not ?

 

I am not against LOOT at all, I do believe it is a great tool but Vortex is also doing the sorting. I know that under my settings I have Automatically Sorting on, and I could turn it off but my question is if I should just let Vortex sort the load order or let LOOT does it.

 

What are the differences and what are the consequences ( if any ) by just letting Vortex do the sorting and forge about LOOT ?

 

Can anybody help here please ? I understand that LOOT must be used to clean the master files and that is not in question here.

 

Thanks for your help ... :cool:

[HardwareSc8]

Actually, xEdit is used to clean dirty files. As far as the sorting goes, you don't need to run LOOT to sort. I mean, you could, but it's redundant. LOOT sorting is included in Vortex as part of the program; that's what the Plugins tab is doing when it sorts.

[simsrw73]

There is no difference except that Vortex applies the additional rules that you create within Vortex. Loot doesn't know about those. You should only sort with Vortex (which uses loot-api + your rules).

[HadToRegister]

Can anybody help here please ? I understand that LOOT must be used to clean the master files and that is not in question here.

 

 

 

To clarify, LOOT does NOT clean Master files.

Here's how I currently do it with WryeBash

 

I currently use WryeBash for everything, you can integrate loot into it's interface, along with the Xedit programs

 

I run loot from the Wryebash interface, only for its report on which esms/esps need to be cleaned, I don't use it for sorting, because for me, it has never suggested a good sort order (it insists on putting mods such as "Sands of Time" at the top of the load order, even though the mod author says it need to go at the very bottom, and other things like that)

Anyway, I use Loot to see what needs to be cleaned, then I run Xedit from the Wryebash interface, and pick each esm/esp that needs to be cleaned (ONE BY ONE), and highlight the esm or esp, then I pick 1. Apply Filter for Cleaning. then 2. Remove "Identical to Masters" Records. then 3. Undelete and Disable References. then I click on the X to close Xedit and the esm/esp is saved.

 

Then I run Loot again and see what else needs to be cleaned., repeat

 

Loot is allegedly supposed to sort things. It's Xedit aka tes5edit, fo4edit, tes4edit that does the actual cleaning.

 

[HolyMosey]

so no need to use LOOT if I use vortex for say, fallout new vegas?

[HadToRegister]

so no need to use LOOT if I use vortex for say, fallout new vegas?

 

Loot is built into Vortex

[sopmac45]

There is no difference except that Vortex applies the additional rules that you create within Vortex. Loot doesn't know about those. You should only sort with Vortex (which uses loot-api + your rules).

 

​Excellent .... thanks also to HadToRegister and everybody else who posted .... Vortex sorting it is then.

 

​Thanks so much guys, simple answers and straight to the point ... :cool:

[BeowulfSchmidt]

There is no difference except that Vortex applies the additional rules that you create within Vortex. Loot doesn't know about those. You should only sort with Vortex (which uses loot-api + your rules).

 

I'm not sure that's 100% true. I get different results when I sort with LOOT than I do when I let Vortex sort. For instance, LOOT sorts Lanterns of Skyrim before Unofficial Skyrim Special Edition Patch, but when I select "Sort Now" in the plugins tab, the order is reversed. I know from reading LoS's Nexus page that it should in fact go before USSEP, so perhaps it's simply a matter of Vortex, for some reason, not having an updated rules list?

 

I'm using LOOT version 0.12.3 downloaded from github just a week or so ago.

[sopmac45]

 

There is no difference except that Vortex applies the additional rules that you create within Vortex. Loot doesn't know about those. You should only sort with Vortex (which uses loot-api + your rules).

 

I'm not sure that's 100% true. I get different results when I sort with LOOT than I do when I let Vortex sort. For instance, LOOT sorts Lanterns of Skyrim before Unofficial Skyrim Special Edition Patch, but when I select "Sort Now" in the plugins tab, the order is reversed. I know from reading LoS's Nexus page that it should in fact go before USSEP, so perhaps it's simply a matter of Vortex, for some reason, not having an updated rules list?

 

I'm using LOOT version 0.12.3 downloaded from github just a week or so ago.

 

 

​That is why I made the question. I've seen LOOT sorting the load order in a different way that Vortex does it ... however, in relation to this particular mod : Lanterns of Skyrim, I setup a rule in Vortex to load this mod first and before USSEP so when I run LOOT, this mod remains in the position I told Vortex. And what you pointed out about this mod is strange, because back in NMM, Lanterns of Skyrim was ALWAYS placed before USSEP by LOOT, so I do not know what is going on with your setup.

 

​I recommend to setup a rule in Vortex; choose USSEP to "load after" Lanterns of Skyrim and RE-DEPLOY ( button located under MODS tab ) so changes will apply. After that, run LOOT and see what happens. LOOT should respect your decision and if it does not, then use the feedback in Vortex but I doubt it that you would have to do that.

[BeowulfSchmidt]

 

 

There is no difference except that Vortex applies the additional rules that you create within Vortex. Loot doesn't know about those. You should only sort with Vortex (which uses loot-api + your rules).

 

I'm not sure that's 100% true. I get different results when I sort with LOOT than I do when I let Vortex sort. For instance, LOOT sorts Lanterns of Skyrim before Unofficial Skyrim Special Edition Patch, but when I select "Sort Now" in the plugins tab, the order is reversed. I know from reading LoS's Nexus page that it should in fact go before USSEP, so perhaps it's simply a matter of Vortex, for some reason, not having an updated rules list?

 

I'm using LOOT version 0.12.3 downloaded from github just a week or so ago.

 

 

​That is why I made the question. I've seen LOOT sorting the load order in a different way that Vortex does it ... however, in relation to this particular mod : Lanterns of Skyrim, I setup a rule in Vortex to load this mod first and before USSEP so when I run LOOT, this mod remains in the position I told Vortex. And what you pointed out about this mod is strange, because back in NMM, Lanterns of Skyrim was ALWAYS placed before USSEP by LOOT, so I do not know what is going on with your setup.

 

​I recommend to setup a rule in Vortex; choose USSEP to "load after" Lanterns of Skyrim and RE-DEPLOY ( button located under MODS tab ) so changes will apply. After that, run LOOT and see what happens. LOOT should respect your decision and if it does not, then use the feedback in Vortex but I doubt it that you would have to do that.

 

 

I think you might have misunderstood. LOOT already puts LoS and USSEP in the right order. It's Vortex that puts them in the wrong order. I'm well aware that I can set up a rule to make Vortex do the right thing, but that's not the point. If Vortex is supposed to be doing the same thing that LOOT is, it's not. That cause might be the version of LOOT I'm using versus the version of the LOOT API that Vortex is using, or it might be that, for whatever reason, Vortex isn't using the same master list that LOOT is, or it could be because I'm doing something wrong.

 

I'd prefer to find out what the actual problem is before I go an try to fix it. For now, LOOT is doing the right thing, so that's the method I'm going to use. I will happily change things around, if necessary, when I know what the actual issue is.

 

FWIW, I've submitted feedback from within Vortex. I'll be happy to perform any addition test tannin thinks might be helpful.