simsrw73 Posted March 3, 2018 Share Posted March 3, 2018 OK. There is something goofy here. LOOT's master list is at : %localappdata%\LOOT\Skyrim Special Edition\masterlist.yaml Containing the rule: - name: 'Unofficial Skyrim Special Edition Patch.esp' global_priority: -120 after: - 'Lanterns Of Skyrim - All In One - Main.esm' For the test, so that there are no user rules, I moved my rules stored at : %appdata%\Vortex\SkyrimSE\userlist.yaml => userlist.yaml.bak Because Vortex/Loot doesn't sort rules for which there are no rules, I leveled the playing field by backing up and then alphabetically sorting: loadorder.txt I opened up Vortex, and it automatically sorted... WRONG. Lanterns was in the wrong place. I closed Vorted, uninstalled LOOT, and deleted %localappdata%\LOOT\. Resorted loadorder.txt. Then launched Vortex which recreated and fetched all the LOOT files to '%localappdata%\LOOT\', and sorted... CORRECT. Closed Vortex, resorted loadorder.txt, installed LOOT, and launched it. LOOT sorted... CORRECT. Launched Vortex, and it sorted... WRONG. Closed Vortex, resorted loadorder.txt. Deleted '%localappdata%\LOOT\', Launched Vortex and it sorted CORRECT. I'm confused. No idea what is going on, but there is some evil interplay between LOOT and Vortex/loot-api that's breaking Vortex. It's like Vortex isn't picking up the masterlist when LOOT has taken ownership of the masterlist. BUT Vortex knows about the rule, because it shows up when you click the dependency graph. It just doesn't obey the rules. Workaround until someone smarter figures out what is going on. Uninstall LOOT. You don't need it and Vortex works correctly without it. Link to comment Share on other sites More sharing options...
HadToRegister Posted March 3, 2018 Share Posted March 3, 2018 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. Just curious, and most likely a very stupid question, but you gotta rule everything out.But are those two mods actually being put in the wrong order, or do you have your "Load Order" column set to reverse? I have my Load Order column on the Plugins pages so it reads 0, 1, 2, 3 now you can click on the up/down arrows on the load order column and reverse it so it reads 3, 2, 1, 0 Could that be the problem? That's Vortex IS ordering them right, but you have the Load Order display set to reverse? Because that would make it look like one mod is improperly loading before the other. Link to comment Share on other sites More sharing options...
sopmac45 Posted March 3, 2018 Author Share Posted March 3, 2018 OK. There is something goofy here. LOOT's master list is at : %localappdata%\LOOT\Skyrim Special Edition\masterlist.yaml Containing the rule: - name: 'Unofficial Skyrim Special Edition Patch.esp' global_priority: -120 after: - 'Lanterns Of Skyrim - All In One - Main.esm' For the test, so that there are no user rules, I moved my rules stored at : %appdata%\Vortex\SkyrimSE\userlist.yaml => userlist.yaml.bak Because Vortex/Loot doesn't sort rules for which there are no rules, I leveled the playing field by backing up and then alphabetically sorting: loadorder.txt I opened up Vortex, and it automatically sorted... WRONG. Lanterns was in the wrong place. I closed Vorted, uninstalled LOOT, and deleted %localappdata%\LOOT\. Resorted loadorder.txt. Then launched Vortex which recreated and fetched all the LOOT files to '%localappdata%\LOOT\', and sorted... CORRECT. Closed Vortex, resorted loadorder.txt, installed LOOT, and launched it. LOOT sorted... CORRECT. Launched Vortex, and it sorted... WRONG. Closed Vortex, resorted loadorder.txt. Deleted '%localappdata%\LOOT\', Launched Vortex and it sorted CORRECT. I'm confused. No idea what is going on, but there is some evil interplay between LOOT and Vortex/loot-api that's breaking Vortex. It's like Vortex isn't picking up the masterlist when LOOT has taken ownership of the masterlist. BUT Vortex knows about the rule, because it shows up when you click the dependency graph. It just doesn't obey the rules. Workaround until someone smarter figures out what is going on. Uninstall LOOT. You don't need it and Vortex works correctly without it. Very interesting simsrw73 .... let's hope that Tannin read your post and probably he answers to it and fix it if it is not working properly. I am using only Vortex to sort my load order. LOOT is still installed but I have not used since I installed my game. But I noticed that LOOT changes the load order after Vortex sorted it out so I decided not to use both but only Vortex. I admit, this is weird. Link to comment Share on other sites More sharing options...
MarchinBunny Posted March 4, 2018 Share Posted March 4, 2018 Ya, I can verify from my load order that Vortex is for sure sorting Lanterns of Skyrim correctly. So it seems like something odd is going on if you are using both loot and vortex at the same time. Hopefully, Tannin can take a look and see what is up, because that can cause issues for a lot of people if it's not fixed. Link to comment Share on other sites More sharing options...
DFiNo Posted March 4, 2018 Share Posted March 4, 2018 I also noticed things being sorted wrong. The following procedure is working for me: 1. Make sure my Vortex plugin list is sorted by load order. 2. Turn off Vortex autosort and keep it off. 3. Sort plugins with LOOT (I also visually inspect the resulting sort order). 4. Restart Vortex. (I have found that Vortex will not change the plugin sort order right away, like NMM does, but will reflect the LOOT sort order after a restart.) This is working for me, for now at least. Update: Added some mods and sorted by LOOT. Tried just changing the view from Plugins to Mods and then when I went back to Plugins the changes made by LOOT were correctly shown in Vortex. Probably not necessary to do a restart, just changing views seems to work. Link to comment Share on other sites More sharing options...
sopmac45 Posted March 4, 2018 Author Share Posted March 4, 2018 I also noticed things being sorted wrong. The following procedure is working for me: 1. Make sure my Vortex plugin list is sorted by load order. 2. Turn off Vortex autosort and keep it off. 3. Sort plugins with LOOT (I also visually inspect the resulting sort order). 4. Restart Vortex. (I have found that Vortex will not change the plugin sort order right away, like NMM does, but will reflect the LOOT sort order after a restart.) This is working for me, for now at least. Update: Added some mods and sorted by LOOT. Tried just changing the view from Plugins to Mods and then when I went back to Plugins the changes made by LOOT were correctly shown in Vortex. Probably not necessary to do a restart, just changing views seems to work. I'll do in a few minutes and get back here with my result. I will also add this problem to Vortex feedback hoping that I am not the only one providing it so probably Tannin will take a look when he sees a trend issue. Thanks ... :cool: Link to comment Share on other sites More sharing options...
sopmac45 Posted March 4, 2018 Author Share Posted March 4, 2018 I am confirming that LOOT is changing my load order previously set by Vortex ... way off by the way ... I already entered my feedback in Vortex, hoping they can see it and pay attention to it. At this point and for now, I am just relying on Vortex sorting which is obeying my dependencies and load order rules. Don't know why LOOT is not reading / applying my rules and is on the contrary, throwing its own load order. P.S. By the way, does anybody know how to print our load order from Vortex as we could do it back in NMM ? Thanks ... :cool: Link to comment Share on other sites More sharing options...
Olivir2019 Posted March 4, 2018 Share Posted March 4, 2018 I think that the user rules made in Vortex are just for Vortex. Vortex uses Loot API for sorting, but your LOOT installation is completely separate and any user rules made in LOOT also would not be available in Vortex. There is no way these applications could know about user rules set up in the other application. EDIT: Loot API allows Vortex to reach for the masterlist, but that's it (As I understand it). Link to comment Share on other sites More sharing options...
BeowulfSchmidt Posted March 4, 2018 Share Posted March 4, 2018 Just curious, and most likely a very stupid question, but you gotta rule everything out.But are those two mods actually being put in the wrong order, or do you have your "Load Order" column set to reverse? I have my Load Order column on the Plugins pages so it reads 0, 1, 2, 3 now you can click on the up/down arrows on the load order column and reverse it so it reads 3, 2, 1, 0 Could that be the problem? That's Vortex IS ordering them right, but you have the Load Order display set to reverse? Because that would make it look like one mod is improperly loading before the other. Sadly, that's not it. I would have been happy were it user error. :) Link to comment Share on other sites More sharing options...
sopmac45 Posted March 4, 2018 Author Share Posted March 4, 2018 I think that the user rules made in Vortex are just for Vortex. Vortex uses Loot API for sorting, but your LOOT installation is completely separate and any user rules made in LOOT also would not be available in Vortex. There is no way these applications could know about user rules set up in the other application. EDIT: Loot API allows Vortex to reach for the masterlist, but that's it (As I understand it). I do understand that but the whole purpose of Vortex and LOOT are to sort the load order to its best and make it closer to perfection. If LOOT is not playing any rol in what Vortex does and Vortex is not playing any rol in what LOOT does as well, what is the purpose to sort via Vortex after setting dependencies and load order rules and / or to run LOOT before playing ? I set my dependencies in the Mods tab ( resolving conflicts between mods ), then I manually place some mods in the right place according to mod author suggestions and sort it out via Vortex; at this point everything is handy-dandy ... so what is the point to run LOOT ? The other way around it is to resolve conflicts in the mod tab, manually place some mods according to mod author suggestions and run LOOT ? I do not mind at all which way I should go for but I just would like to be clear, path A or B ... simple like that ! What's your opinion J.O.D. ? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.