Shadriss

In general, no. Not unless there are specific problems you are troubleshooting.

Actually, I think I use MO2 in Instance mode, and have had no problems with merges Tech. Is there an easy way to tell which mode you are using?

I'll check those ones specifically, but as the error seems to be in the Conflict Resolution Merged, I'll check to make sure that merge is correct first. But in answer, yes I have the latest files, but I may not have rebuilt that merge patch when I needed to. The only thing that makes me unsure that this is just a ME problem is the other poster who mentioned a lot of Black Face issues. Regardless, I'll check into those others, rebuild my patch, and report back. Quoted for truth. EDIT: Brelyna had the problem as well, Using Rikke's pieces. Rikke was fine, and I found no entry on Frea - I'm assuming a misspelling or some such, so can you remind me who this char is? In the meantime, I'm going to rebuild the conflict resolution merged patch and see what results. EDIT the Second: Rebuilding the Conflict Resolution Merged Patch seems to fix the problem, looking at the SSEEdit records after rebuild. I went back and looked at the changelogs, and saw no mention of needed to rebuild this merge in the last month - not placing blame, just pointing out that if that part of the changelog is to remain, we might want to be sure that ALL merges that need to rebuild get listed instead of relying on the user to ID that requirement - things like this happen otherwise. On the upside, I learned how to better use SSEEdit today, so no loss at all. :) EDIT the THIRD!: Re-Engaged ENB, as of AUG02 claims to support Night Eye. Of course it's after we moved to Phoenix... though according to the posts on Phoenix, the author is attempting to find help to get it working as well.

Back on the black face for Aela - I pulled up the load list in SSE and found something very interesting... all of Aela's face parts (and even her armor...) were replaced with those of Ignun Black-Briar in the Conflict Resolution Patch... which if memory serves was recently updated? If that's the case, could a large number of accidental changes be causing this problem? I'm testing this theory by moving the records from the NPC Retexture to the zEdit patch. I'm going to hunt down Aela and see if it made any difference. EDIT: CONFIRMED. Face and armor were back to what was expected, with no black face at all. Theory: Somehow, in the most recent version of the conflict resolution patch, records were swapped around. Aela, as I've mentioned, was assigned Ignun's armor and face records, as an example, and when I moved the Aela records from the NPC merge to zEdit (used it cause it was last in the conflict paths), she appears as she is supposed to. I suggest, for those who see this bug at the moment, that you check SSEEdit to see if the same is true of other NPC's we've seen with the problem lately. I was putting it down to a strange interaction between Krypt's SSE mods and the original load order, but it may be inherent in the files we were given by Lexy instead. Can anyone else confirm they see something similar? EDIT the Second: The offending records are coming from the Conflict Resolution Merged file, which means the one I generated through Merge Plugins. Not Lexy's fault on this one - though it seems that the Merge isn't carrying over records as it should either. Anyone have recommendations?

It is one thing to say "I took a look at this mod, found bugs, and fixed them. I posted this as a stand-in until the original author fixes them him/herself or until I get permission to take over the mod's maintenance," and quite another to say, "All them other mods are broke as anything, they suck, I rule, this is how it should have been in the first place, worship me." Unless you are Sheson, in which case the worshiping part is fine.

As of the time of this post, it's not locked. Is Nexus flip flopping over there?

SKSE is sort of a two part install - for more detailed instructions, look here. It was written with SE in mind, not LE, but the basic instructions are identical. Just ensure that you are grabbing the LE version of SKSE, and all should be fine.

Already in process of figuring this one out - this mod and it's companion were discussed a few pages back. Thanks for the link though! Not at iNeed specifically - needs mods in general. That said, as far as I can tell from the description, it doesn't provide the same flexibility that iNeed does - which is why all the scripts are needed in the first place. Honestly, between his slams right out of the gate and the lack of flexibility, I have no real desire to look at this further.

Part the First: Yes, that's a workaround - the one I was mentioning didn't need that, as it was built around ENB to begin with, and so worked 'out of the box' with no need for it. This is why I've been attempting to get it working in SE. Part the Second: No idea about it's eventual placement, but I see it either being used as part of the NPC merge with an updated CR, or standing alone with an updated CR. Until the team figures that out, I'm sitting them low on the left pane and LOOT sorted on the right.

From the quick look I did, this is, in essence, the same thing we do with our own conversion process, minus the actual disabling of features. No real gains here, though it may be easier for those new to the guide to get it up and running. Spectacular was originally designed to work with ENB, and did so without modifying any ENB files... so why would this not work now? Just the new ENB code, or some such? A better question, I suppose, would be what needs to be modified in any ENB to make it work with night eye... as opposed to limiting our choice of ENB, why not post what the specific problem is, and a way to make that change locally? Phoenix obviously doesn't, and I do not wish to change ENBs if it's not needed... a file edit is, in my mind, far more desirable and simple.

And suddenly, in makes more sense... for you. *sigh* In other news, I'm trying to find a night eye effect mod that works with ENB. I used to use Spectacular Night Eye (Precipice effect) in the SE days, so I've converted that and will let you guys know if it works or not.

Didn't see it on Janessa, but haven't been up to the College to check those. Where do you have the Krypt mods located? That may be a part of why we're seeing different effects.

Here to support.

Can you be more specific than "a number of the more important NPCs"? As I said, I've only seen in on Aela so far, and I've been over most of Whiterun and Riverwood to this point looking. If you can give me at least a small list, maybe we can start narrowing this down somewhat for both of us.

Resources Link for 2.43 leads to the Standalone download, Sheson. MAY want to fix that. :)

You're correct, Greg, but that was also in the original version. Nothing new there. :) Keep the ESM activated, do not activate the two that got merged - the merged file contains those records, and it will work fine. You MAY want to re-run Relinker, just to be safe, though. EDIT: In other update news, Sheson updated DynDOLOD to 2.43 in the last few minutes, for those who are in process of building. EDIT: In other, other news, the BethINI download was reported to have a trojan of some sort in it - has this been confirmed or resolved yet?

Both videos unavailable. :) I didn't. Pretty sure that merging an ESM is a big no-no.

It's somehow related to facegen files, but the fixes I've seen talked about seem... rather involved or arcane. If you figure this out, be sure to shout out. I've only seen Aela affected by this so far, which IIRC is the same NPC you saw with it. Here to support. I'd already done all the other updates and additions (though I hadn't moved the two Rustic mods to the positions you showed), but those two armor mods I left alone pending the question I had regarding the apparent removal of physics from the armors. WRT KS Dragon Overhaul 2, I should also point out that there is NOT a Thunderchild patch for it yet (not sure if we were using it or not for the original), and that it requires a new game, not an upgrade in place - odd things happen if you replace it mid-game, apparently.

KS Dragon Overhaul has a successor - KS Dragon Overhaul 2. The english is pretty broken, so it's hard to make it out totally, but it looks essentially like the original, but adds in a few new possibilities, such as stat bolstering from dragon soul absorbs. The scripting used in the original may be a bit more streamlined as well, somehow - again, its kind of hard to read. Possible upgrade/replace of the original mod? EDIT: Reading in the comments, the changes are as follows: A) Streamlines the scripting process. B) Removed the "Vanilla/Mod" option of dragon behavior - so, in essence, one less option we have to change over in the MCM. C) Added in the dragon soul absorb options, which allow the PC to grow in strength (stats) through soul absorbs - this was apparently something another mod did/used to do that he has added in. In all other respects, appears to be mostly unchanged.

A few questions with regards to the changes: A) You've updated the Black Sacrament Armor, but not Lustmord Vampire. They have the same author and changes made to their mods - why one and not the other? Also, this change apparently now requires additional work to get the physics that the previous version had (if I read correctly). Are these changes really what we want? B) In the position you've placed the Rustic Word Walls, all but two files are overwritten by Vivid Landscapes two mods later. Does this not pretty much defeat the purpose of putting this in? In essence, we've changed next to nothing in the overall appearance of the word walls by doing this. I'd wait until you finish the entire guide before trying to fix anything - most things are taken care of at or near the Finishing Line portion... although I admit that first pic is a tad odd. Not sure what's going on there.

A crash to desktop before the main menu is generally an indication of a missing master error. If this is the case, the Weather Systems merged file will have a red triangle next to it (and an indication in the top right corner of MO, for that matter). Hovering your mouse over that triangle should identify the file that is missing - turn this on. As to what portions of the finishing line you need to redo, I'd suggest the Great Equalizer, Wrye Bash Patch, Smash Patch and zPatch. The LOD portions should only be redone if the missing master has anything to do with terrain, and given that it's the weather systems that caused the original problem, that may be needed as well. The Sorting Masters thing... great if you do it, but I've never seen any adverse affects from not doing it. Since you'll likely have to redo a bunch of stuff, may as well this time around, but if you don't I wouldn't sweat it too much. As to the SkyUI problem, if you go through the list for MCM config, you'll note Lexy has you turn off most (and in my case, I turn off all) of the options for version monitoring. It's not a serious error, and nothing to worry about, but this way you don't get informed about it every time you load up the game. Which one? Either way, the answers are above. For the both of you - if you have continued troubles with the guide, I'd suggest posting in the main guide thread instead of separately - you're far more likely to get assistance there than this way.

New question (so not editing my previous post for the third time): WRT SSE_Tamriel_Terrain.ESM.... what is the purpose of this mod, and why must it be deactivated for so much of the finishing line steps?

Exactly as I told you. You could also have right-clicked the mod -> open in explorer -> renamed the file in windows, then right click in MO -> All Files -> Refresh. Would have accomplished the same... regardless, glad you have it done.

Just looking at a few mods that have updated, and two them (here and here) appear to have removed the physics component of the mod if I read it right. Is this, then, something we should NOT update? Also - New to the Your Own Thoughts Family, patches for Ordinator, Convenient Horses, Summermyst, Apocolypse, Imperious and Wildcat.

*points at previous post* Nope. Nobody at all. Except the guy who posted, literally, right before you did.