VERY IMPORTANT if you wish to successfully mod your gameĪnd refer to this resource (PINNED TOPIC) for links to guides, tutorials, vids, and other important information:Īnd finally, start small - just add a few mods at a time, test, and then play for a while to ensure there are no issues - don't fall into the trap of adding a bunch of mods and then trying to play. Player and Modding Resources (PINNED TOPIC) by Ilja (Vortex may be easier to transition to, as well as being able to be used for almost any game which Nexus has mods for, MO2 is limited to just Bethesda games, though they recently started to expand their capabilities.) Furthermore, considering that you are asking that, I would strongly suggest that you read the following:Įxcellent advice regarding modding Skyrim (essay written by PeggleFrank - a little outdated, but the basic principles still apply) You should use either Vortex or MO2 - both are excellent managers.
If you're using mod organizer, you can't install it through that you have to manually install it into your skyrim folders for it to work. Originally posted by IXBlackWolfXI:Do you have skse installed? Its a requirement for skyUI. My first guess at least is he has skyUI installed but not SKSE. I seriously thought for a while that turning off the AI let me cross, but actually it didn't I just got lucky the first several times doing that.īesides, looking at this load order, its almost certainly skyUI, given that the other mods as far as I know aren't reported to cause problems like this. Of course, in my case, the crashes were random, so even if I crossed a cell border with all my mods enabled, I could still cross without getting a crash. And don't do the thing where you disable half your load order and see if the issue continues that threw me off from the actual cause of my problem for a YEAR. So no, don't enable your mods one by one disable them one by one. Before, I was just doing that thing where you disable half your load order at a time until you find the problem this was giving me false positives over and over, which is why I'll never do that again. Its what prompted me to finally just test my entire load order one by one. I kept removing mods, only for the crashes to re-emerge over and over again. Keep in mind, I suffered from this problem for probably more than a year. What would've happened is I would've just removed the first mod where I got a crash if it was enabled, unaware that it wasn't actually responsible. Now, what might have happened if I instead enabled mods one by one? Well, the crashes were dictated by how many mods I had enabled, so I wouldn't have been able to get a crash if I had only a few installed. I later found an issue to my problem, by using a fix originally made for New Vegas, but apparently works fine in other creation kit games (I've been using it for a few months now, and haven't had another crash, beside this one time I was screwing around on a test profile and forgot to enable that mod).
The only pattern I found, was that the likelihood of a crash was dictated by how much data my enabled mods took up. After going through my entire load order, I found that not ONE single mod was responsible. I eliminated my mods one by one (starting a new game each time to check if I still crashed at the cell borders in question). Just for an example, I finally decided to fix a cell border crash I was having. You don't look for verification: you look for falsification.