OldWolf63 Posted January 22, 2019 Author Share Posted January 22, 2019 After seeing these last posts, I went into Vortex and checked the things asked about. I'd actually already seen the enable option right in the middle of all of those error messages, and clicking it did what it was supposed to do. Mods are still being installed, enabled and deployed the way they're supposed to be. I'm still playing the game with no more than the usual random CTD now and then. I've put it down as more of a minor irritation than an actual problem, but I would still like to know what's causing it and if it can be removed. If not, it's something I can live with. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted January 22, 2019 Share Posted January 22, 2019 After seeing these last posts, I went into Vortex and checked the things asked about. I'd actually already seen the enable option right in the middle of all of those error messages, and clicking it did what it was supposed to do. Mods are still being installed, enabled and deployed the way they're supposed to be. I'm still playing the game with no more than the usual random CTD now and then. I've put it down as more of a minor irritation than an actual problem, but I would still like to know what's causing it and if it can be removed. If not, it's something I can live with. Glad to hear your game's working OK in spite of that irritating warning. In regard to superfluous rules, did you notice any such rules in your mod conflict rule book? These superfluous rules do not generate destructive cycles, but my suspicion is that they trigger the warning you keep getting. Link to comment Share on other sites More sharing options...
OldWolf63 Posted January 24, 2019 Author Share Posted January 24, 2019 I honestly have no idea what or where a mod conflict rule book might be. Like I said, I'm no computer expert by any means. I can say that, when I check conflicts on Vortex, everything shows green. Link to comment Share on other sites More sharing options...
HadToRegister Posted January 24, 2019 Share Posted January 24, 2019 I honestly have no idea what or where a mod conflict rule book might be. Like I said, I'm no computer expert by any means. I can say that, when I check conflicts on Vortex, everything shows green. If everything is green then you're good Link to comment Share on other sites More sharing options...
AugustaCalidia Posted January 24, 2019 Share Posted January 24, 2019 I honestly have no idea what or where a mod conflict rule book might be. Like I said, I'm no computer expert by any means. I can say that, when I check conflicts on Vortex, everything shows green. Well, I guess I confused you with my term "rule book." My apologies. There's no actual book or catalogue of rules. "Rule book" is just my shorthand way of referring to the any and all rules a user has set to resolve file conflicts. Anyway, HadToRegister is right - if everything is green then you're good. Link to comment Share on other sites More sharing options...
OldWolf63 Posted January 27, 2019 Author Share Posted January 27, 2019 Understood. And, no, I was very careful to avoid the A-B-C-A loop. I do appreciate the advice, however, so thanks. I'll just ignore those errors until and unless they become an actual problem instead of an irritation. Link to comment Share on other sites More sharing options...
nymaen Posted January 27, 2019 Share Posted January 27, 2019 There is a cool feature in Vortex I recently stumbled onto that helps with this issue. Simply click on the [show] button and you can see the list of conflicted mods. If you click on that list, it take you to a page that presents a relationship graph of all the dependencies. You can then click on them to remove a dependency. Repeat until the cycle is broken. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted January 27, 2019 Share Posted January 27, 2019 In Vortex 0.17.1 (Testing) there is now a "Manage Rules" button on the taskbar that allows you to see and manage all mods with file conflicts. Also, the conflict menu has been redesigned in order to prevent the accidental creation of cyclic rules. Link to comment Share on other sites More sharing options...
OldWolf63 Posted February 16, 2019 Author Share Posted February 16, 2019 Updated to the new version and the error messages have stopped. Must have just been a glitch in the older version. Thanks for the helpful advice. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.