HadToRegister Posted February 21, 2021 Share Posted February 21, 2021 Might be handy to add a scrollbar to the notification area though Link to comment Share on other sites More sharing options...
Pickysaurus Posted February 22, 2021 Share Posted February 22, 2021 What happens if you open out that massive chunk of notifications? Does it get cut off by the bottom of the app? Does it extend into infinity? Link to comment Share on other sites More sharing options...
HadToRegister Posted February 22, 2021 Author Share Posted February 22, 2021 What happens if you open out that massive chunk of notifications? Does it get cut off by the bottom of the app? Does it extend into infinity? It gets cut off at the bottom border of Vortex, it doesn't go outside the frame of Vortex. But it's my usual method of downloading and installing mods.Now I'll go through the list one-by-one and install Link to comment Share on other sites More sharing options...
Pickysaurus Posted February 23, 2021 Share Posted February 23, 2021 Fair. If you haven't already, can you submit this suggestion inside the Vortex app? It gets automatically added to GitHub that way. Link to comment Share on other sites More sharing options...
Zanderat Posted February 24, 2021 Share Posted February 24, 2021 Maybe off topic. But if you are installing 149 mods at once, how do you mange wading through all those conflicts and keep it all straight? Link to comment Share on other sites More sharing options...
HadToRegister Posted February 24, 2021 Author Share Posted February 24, 2021 Maybe off topic. But if you are installing 149 mods at once, how do you mange wading through all those conflicts and keep it all straight? By using the LOAD BEFORE/LOAD AFTER Rule Manager if Vortex reports any conflicts Link to comment Share on other sites More sharing options...
Zanderat Posted February 25, 2021 Share Posted February 25, 2021 Maybe off topic. But if you are installing 149 mods at once, how do you mange wading through all those conflicts and keep it all straight? By using the LOAD BEFORE/LOAD AFTER Rule Manager if Vortex reports any conflicts Yes. I know that. I meant my brain isn't wrinkly enough to keep all those rules straight unless I go one at a time. I was curious if there was more to it than that. Link to comment Share on other sites More sharing options...
Tannin42 Posted February 26, 2021 Share Posted February 26, 2021 Please keep in mind that if you had installed the mods manually or with NMM, it would have asked you to overwrite or not, only difference is that with Vortex you can chance that decision any time.But if you want the full NMM experience, simply sort your mods by installation date descending (newest first), then go top-to-bottom and set them to load after everything they don't have a rule for yet. For a more elaborate selection I would start with the mods that you either care most about or that are the most "specific" (e.g. a retexture for a single outfit rather than a "complete texture overhaul of everything") and set them to "load after" everything without a rule previously assigned. For the rest you can go back to the "newest-to-oldest" approach or simply use the vortex suggestions. What I would also suggest is: use only "load after" rules, don't use "load before". I could kick myself for even including that option.That makes it much easier to keep an overview because any rule simply means "left side more important than right side". Link to comment Share on other sites More sharing options...
HadToRegister Posted February 26, 2021 Author Share Posted February 26, 2021 Please keep in mind that if you had installed the mods manually or with NMM, it would have asked you to overwrite or not, only difference is that with Vortex you can chance that decision any time.But if you want the full NMM experience, simply sort your mods by installation date descending (newest first), then go top-to-bottom and set them to load after everything they don't have a rule for yet. For a more elaborate selection I would start with the mods that you either care most about or that are the most "specific" (e.g. a retexture for a single outfit rather than a "complete texture overhaul of everything") and set them to "load after" everything without a rule previously assigned. For the rest you can go back to the "newest-to-oldest" approach or simply use the vortex suggestions. What I would also suggest is: use only "load after" rules, don't use "load before". I could kick myself for even including that option.That makes it much easier to keep an overview because any rule simply means "left side more important than right side". I always use LOAD AFTER, it's much easier to envision what happens with the files. This is why I like Vortex, because I can install anything on that list in any order and fix it later Have you thought about Removing "Load Before"? And just let Vortex use it internally for when you pick the LOAD AFTER rule on the Rule Manager when a conflict is reported? Link to comment Share on other sites More sharing options...
Guest deleted34304850 Posted February 26, 2021 Share Posted February 26, 2021 +1 for the removal of "LOAD BEFORE" in a future iteration. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.