![]() For example, an armor mod that needs the Dragonborn or Dawnguard DLC to work. Re-evaluate your mod list and check to see if you're missing any requirements. Because if you're lacking the certain DLC for a certain mod or another mod pack to enable THAT mod to work, you'll crash on start-up. I suggest using the Nexus Mod Manager, it's very efficient. ![]() ![]() Some mods need to load up in a certain load order. For example, if the mod creator requires that a mod loads last on the load order list, you boot up your Skyrim Mod Manager (I recommend the Nexus Mod Manager), then drag it all the way to the bottom. So again, re-evaluate the requirements for each mod, then check to see if they need to load in a specific load order (most mods do NOT require specific load orders, just the complex ones). Oh, and make sure you have the latest version of Skyrim Script Extender, because if you have an ancient one, it will NOT be compatible with some new mods. If you don't want to do that, then likely you will just keep encountering the delay.DId you not read my previous comment? I tried to install SKSE using the Gopher's video.1. This facilitates it only doing the validation check once. The solution to alleviate the issue would be to close NMM when using Vortex, then reopen NMM when you close Vortex. This doesn't exactly sound like a bug as it seems to be doing what is intended, which is setting and validating the order as being read from the plugins.txt file. How long it takes per check depends on your computer setup. This could cause NMM to queue up many rechecks to the order which would give the appearance of a lockup while it rechecks it all multiple times. It sounds like you have NMM open while you use Vortex, and have Vortex do the sorting. So it takes a bit to rescan it all if you have many files. This is done to prevent a scenario such as Issue 1. If you have lots of plugin files, each time one is reordered the NMM code revalidates the entire load order to make sure you do not have a file where it shouldn't go. Assuming the former, I'll explain what I believe is happening. Also not clear if you're saying this happens when NMM is open and use Vortex at the same time, or if you were just stating the issue started happening around the time frame of when Vortex came out. RE 2: It wasn't clear if the issue you have for this only happens in FO4 mode, or if that happens in SSE mode too. 圎dit may give you insight into which mod is in the wrong place for tweaking your plugins.txt to quickly resolve it. If you have 圎dit 4.x.x you could try to open it up with your load order set in the order that NMM doesn't like and try to open the whole order as it is. Then when NMM tries to deal with it, they're in the wrong place and NMM isn't sure how to deal with it so it just disallows ordering. Early on I found this usually to be from things trying to sort. I found the cause of this is usually another program improperly sorting the plugin files externally causing the issue with NMM. ![]() This isn't really an issue with NMM as you didn't use NMM to put them in the wrong place. Any files that aren't in that list then get auto sorted to the best guess location and that usually solves it for me. If it did happen that it somehow got glitched up like that, I keep older load order lists to be imported for quick resetting to a previous state. If this ever happens to me (did once, was a broken mod from the author), I go through the whole order just checking which files require what masters and make sure they're not screwed up in the wrong order. RE 1: This usually happens (that I've encountered) when somehow a master got placed after a plugin that required it, or if 2 files somehow were saying they both need each other as a master. Issue 2) NMM locks up for some time when you change the load order through Vortex. Issue 1) You can't manually change the load order inside NMM. Neither issue appears to be a bug in NMM, which I'll explain below. ![]()
0 Comments
Leave a Reply. |