HadToRegister Posted November 19, 2018 Share Posted November 19, 2018 One last try here: Don't install Loot on the Dashboard, don't tell Vortex where Loot is - and don't run Loot from the Dashboard.Vortex maintains it's own copy of Loot. Trying to apply anything a Loot that you run does will not turn out well.Unfortunately, I already seem to have done that in ignorance just earlier today. But I won't be using LOOT from Vortex ever, I use it from my desktop shortcut. Yea, definitely go back to NMM if you refuse to use LOOT that's already built in so you can screw up your load order with the external version of LOOT. People tried to help you, and instead you decide to ignore their help. Good Day, and thanks for wasting our time.User added to Ignore List. Link to comment Share on other sites More sharing options...
JimAbaddon Posted November 19, 2018 Author Share Posted November 19, 2018 Sorry but I'm not willing to bother with Vortex if I have to do all the sorting myself. I don't know how to, I'm not that savvy with mods and how they interact with each other, this is why I use LOOT. If Vortex can't work along with LOOT then I prefer to stay with NMM. I know that mods that update each other must be placed in the appropriate order, but that didn't seem to be the problem today, there were conflicts I had never noticed with NMM. Thanks for showing me the custom install location though, I missed it because I got Vortex from elsewhere in the nexusmods website. Vortex already HAS LOOT BUILT IN.I was just showing ALL of the other options you have for sorting when Vortex reports a conflict.If you're not even going to be arsed with solving conflicts, then go back to NMM and be completely unaware of Conflicts.I've wasted enough time trying to help you. Yes, I'm aware of that. I managed to discover the basic way to sort plugins on my own when trying to fix any issues. Unfortunately, the problems I encountered where a little more complicated than just between a basic file and an update file that needs to overwrite the basic file. I'll need to look it up again with Vortex and see if I can sort the collisions. I did try to specify whether the mod will load before or after, but it didn't seem to fix everything. I don't remember quite well what the conflicts where, probably something caused by the Book of Silence series, once I try again I'll look into it. Link to comment Share on other sites More sharing options...
JimAbaddon Posted November 19, 2018 Author Share Posted November 19, 2018 You never need to start LOOT. Vortex sorts the plugins itself, and it uses an integrated version of LOOT to do that. I used the Sort Now option to fix the conflicts but it didn't seem to change the load order at all. Even had auto-sort enabled to do just that but nothing changed. Link to comment Share on other sites More sharing options...
Grestorn Posted November 19, 2018 Share Posted November 19, 2018 then it was already properly sorted. Link to comment Share on other sites More sharing options...
rmm200 Posted November 19, 2018 Share Posted November 19, 2018 You never need to start LOOT. Vortex sorts the plugins itself, and it uses an integrated version of LOOT to do that. I used the Sort Now option to fix the conflicts but it didn't seem to change the load order at all. Even had auto-sort enabled to do just that but nothing changed. Sort Now applies to esp's and esm's shown on the Plugins page. Nothing to do with conflicts shown on the Mods page.If Sort Now did not change the sort order it is because it was already correct.If you have a plugin (esp or esm) that you really want last, put it in the dynamic patch group. Link to comment Share on other sites More sharing options...
JimAbaddon Posted November 19, 2018 Author Share Posted November 19, 2018 Whatever the issue was, I don't think I'll find a solution at the moment. Switching to Vortex from NMM is going to require a clean installation of all my SSE mods and some of the tools I've used like FNIS and XPM32 have remained in older versions which I kept from updating for simplicity's sake. I prefer not to mess around with sensitive tools like that since I'm not that experienced. Once I know what I'm doing to update them, I'll attempt to fix any problems Vortex shows and get it running properly. Thanks for your time and help. Link to comment Share on other sites More sharing options...
fore Posted November 19, 2018 Share Posted November 19, 2018 some of the tools I've used like FNIS and XPM32 have remained in older versions which I kept from updating for simplicity's sake. I prefer not to mess around with sensitive tools like that since I'm not that experienced. ESPECIALLY when you are not experienced you should not stay with older versions of tools and mods. There is a reason why FNIS or XPMS have been updated. Either because of issues, because of necessary compatibility with other mods, because of functionality added in view of Vortex, or, or, or.. Do you want all of you problems being sorted out by more experienced people? Link to comment Share on other sites More sharing options...
sopmac45 Posted November 20, 2018 Share Posted November 20, 2018 Whatever the issue was, I don't think I'll find a solution at the moment. Switching to Vortex from NMM is going to require a clean installation of all my SSE mods and some of the tools I've used like FNIS and XPM32 have remained in older versions which I kept from updating for simplicity's sake. I prefer not to mess around with sensitive tools like that since I'm not that experienced. Once I know what I'm doing to update them, I'll attempt to fix any problems Vortex shows and get it running properly. Thanks for your time and help. Sorry JimAbaddon, but not one put a gun in your head to obligate you to jump to Vortex and not one is trying to convince you either to stay with Vortex. Understand that this is tool, and whatever you do with that tool is entirely up to you. You are one more that belong to the group of people that do not read, investigate, watch videos or ask valid questions about Vortex but complain about, without knowing anything at all about the tool you are trying to use. Be serious and do not blame the tool but yourself !!! Link to comment Share on other sites More sharing options...
rmm200 Posted November 20, 2018 Share Posted November 20, 2018 Whatever the issue was, I don't think I'll find a solution at the moment. Switching to Vortex from NMM is going to require a clean installation of all my SSE mods and some of the tools I've used like FNIS and XPM32 have remained in older versions which I kept from updating for simplicity's sake. I prefer not to mess around with sensitive tools like that since I'm not that experienced. Once I know what I'm doing to update them, I'll attempt to fix any problems Vortex shows and get it running properly. Thanks for your time and help. Jim, just because you might not recognize names, Fore is the author of FNIS. He speaks with some authority. Link to comment Share on other sites More sharing options...
BigBizkit Posted November 21, 2018 Share Posted November 21, 2018 Hi Jim, I think I know where your confusion is coming from. LOOT sorts your plugin list in a sensible fashion to prevent inter-plugin conflicts. LOOT, therefore, arranges your plugin load order. Your "mod load order" or rather, as we call it in Vortex, "mod install order" is not arranged by LOOT. In NMM when two mods edit the same file you will be prompted during installation to decide if you want to keep the old version of the file, or overwrite it with the new one from another mod. Once you have made your decision that's that. In order to reverse it, you would need to reinstall the mods. In Vortex, you can change your decision any time dynamically. This is explained here: https://wiki.nexusmods.com/index.php/File_Conflicts:_Nexus_Mod_Manager_vs_Vortex Managing file conflicts is further explained here: https://wiki.nexusmods.com/index.php/Managing_File_Conflicts Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.