Shadriss

And another one bites the dust... Glad to hear it's all worked out now. Happy Skyrimming.

Here to support, guy. With regards to 3/4... that happens a LOT around here. It's a lot of work, and if you don't take breaks, mistakes happen. So far as iNeed is concerned, have you tried a reinstall of the mod? Just going through basic ideas here before we start hunting witches... Concur with Link... if it's not being hidden, it likely isn't in the actual merge list created by zMerge when you built the merge. I'd recommend rebuilding that merge from scratch (IE, in zMerge - delete the merge profile that you created and recreate it), and double-triple check your settings and checkmarks. Bern hits the highlights, but to reiterate and maybe add a few more tidbits: 1) ESM version, but it's change, breaks a great many patches that are used for the mod. The effort to recreate them is substantial. 2) Many users on the discord have reported being... less than impressed (I'm being kind here...) with the storyline of Vigilant. I haven't played it myself, but the things I've heard about it make me less inclined to play it myself. 3) Pulling it will mean an empty space in the museum, yes... but given that room is huge and largely empty anyhow, who'd notice? 4) Those tree things being (subjectively) true, the effort to recreate the patches far outweighs any gain. 5) Trumping all of that, Lexy doesn't really like it either. 6) The cheese stands alone (that for Uncle Sheo...). For those who have it already in their game, and wish to keep it: DO NOT update your Lexy CR patches or the guide in general until you are done with the playthrough. As I understand it, this pull will happen this Monday with the regular update. For those currently installing: If you want it, act fast and get it done before Monday. If you can't work that fast, then I'm afraid you'll be a bit out of luck and may have to do your own CR at that point. Be Aware. ;)

1) Not sure what's going on there, but it sounds like script lag. When was this happening, and what else was going on at the time? 2) Normal. Experience changes the way that leveling works so that Skill Levels are capped by Player Levels. The base for this (IIRC) is Player Level + 20, so if you were levels 1-5 when you were picking locks, it wouldn't advance any. 3) Normal. Know Your Enemy and Know Your Armor change how combat works significantly - to your specific example, Skeletons are weak to blunt weapons, and are not effected much by bladed weapons or arrows. 4) Can I get a screenshot of this? I've not ever seen that message in-game, so I'm curious as to what it actually said and when. I highly suggest reading and understanding all of the mod descriptions in the guide - there are some major game-play alterations that occur, and if you aren't expecting them it can mess with your head somewhat.

No - I was referring to MO2. MS will have it's ordered based on your load order, which would be MO2's RIGHT pane.

Go back, extract the BSAs you need to, resume. Most likely, that would be the extent of it.

If you walk towards the Western Watchtower from the original encounter site, there is a large rock on the right side of the road - S'ahara is on the watchtower side of that rock, partially hidden by the grass. Yes, she's a pain to find. It's almost like she was hiding or something. ;) Many people disagree. Though it's staying for now, I'd far rather it go away, honestly. I've heard about some of the late-story events, and I'm not thrilled with it... I'd rather have that display be empty than support the kind of story I've been hearing Vigilant turns into. Again, that's based on what users in the discord say, so YMMV. When talking about the LEFT Pane, they should match exactly. When talking about the RIGHT pane, then whatever LOOT does when you run it is correct.

Another T/S Effort completed satisfactorily. Here to support.

Lexy answered this, but for clarity: Some users feel a need to LOOT sort and look inside their game for errors long before the entire guide is finished. Without these kind of rules, they will get a Cyclic Error in LOOT, which they then come over here or on the Discord to complain about, even though we say not to do that because it's pointless. Lexy finally caved to this, and provided LOOT rules which allow these people to LOOT sort just so she wouldn't have to listen to the whining. I'm afraid so. The ones I list are pretty much the biggest offenders. Before you start the 50/50 checking though, there is one more quick-ish check that you can look... I mention this one only because it's come up on the Discord several times in recent days. Verify that all mods in the guide that contain the CLASSIC tag have had their BSA files unpacked - if they have not, then this can also cause a CTD. I think that one happens on game load, and is not tied to given locations, but it's still something to look at. Apart from that... yeah, the "turn-it-off-check-turn-off-next-check" method (AKA, 50/50 checks) is about all that's left. I'd start by turning off only the Finishing Line mods and then the merges... those are the two most likely places for something to have gone wrong. I'd try rebuilding the merge first... I know Lexy mentioned it, but it was almost as an afterthought, so I want to be sure you see this. I've just rebuilt all of my merges as part of the recent weekly update, and I'm not seeing this problem... so I can only assume that something went wrong during that particular merge. Restart it from scratch, make sure of the instructions and process, and give this another try. From my own experience in the last day or two, this merge does work as intended with no errors.

TO further answer this: There are a number of rules mentioned during install that never appear in the Finishing Line... these were added so that those few who just have to turn on the game every so often to make sure they aren't messing something up (which is pointless until it's all installed anyway, but whatevs...) can properly sort everything. As Link mentioned, those get merged later on, so won't appear in the Finishing Line because you wouldn't be able to alter them at that point anyhow. Bruma was a part of the guide until about a month or two ago. If you got back through the guide's changelog, you'll see where it was removed. The guide lists for that period should give you an idea of what mod patches you need to go looking for. That said... it was dropped for a reason... that reason being that it's an unfinished bloody mess of a mod. It's playable, but it is only a 'proof-of-concept' mod that is part of a much larger project. Your call, of course, but I, personally, wouldn't recommend it. Stick with the guide. The Guide is Life. Lexy is your god now. Trust in Lexy. Repeat until you believe it. :)

Random Thoughts: A) New game, or a old save? B) Reinstalled ENB and preset, or left as it was when you removed... whatever that other thing is? C) Without me having dived into that list of mods (Wall of Text reasons), any other mods that touch lighting in any way, shape, or form? D) Unrelated - Confused. Are there two threads with the same name, or is this an odd duplication glitch?

You may want to move this thread then - the general support is, I believe, meant to be for STEP support, which is all Skyrim. There is an area for the other Bethesda games, and putting this there might generate a better reply from someone who plays FO3... though I'm not sure I've seen anyone talking about that game in quite some time.

SO there's a few things that we always recommend checking - I realize you may have done some of these already, but since you didn't say, I won't assume. :) A) Just after the LOOT process in Finishing Line, thee is a list of places to try COC'ing into. Try this process again... the intent in this test is to make sure all the statues were renamed properly, and Lexy listed the easiest ones to check. I can't recall is Morthal has on in it's area or not, but that's the first thing to check. If this test results in CTD, then you need to go into the guide instructions for Stunning Statues and the Talos staute mod (whose name escapes me at the moment) and make sure you've followed them and that all spellings are correct. B) In Skyrim - Immersive Creatures, make sure that the Goblin spawns are turned off - they have been known to cause CTD because of the rocks they throw having bad meshes. Also verify all the other spawns in that mod are set properly while you are at it. C) If neither of those turn out to be the issue, it'll be time for more intensive searching. The next thing I'd do at that point is COC into Morthal itself and see if it CTDs or not. This may give an indication if it's the city itself, or something surrounding it. Let's go with those for now, and see what happens.

I'm confused - I've been playing Skyrim for a long time, and I've had characters well over Lv 30... what cap are you talking about?

I don't disagree... and it is something to be looked at. As I mentiond a few posts ago, there is a guide overhaul in progress (not the updates that Lexy does every week - a serious overhaul of its setup and wording), and things like this are brought up with Lexy. Some things will change, others not... and I can't really say which will happen to what. Remember that, in the end, this is HER list, and if she considers a thing CORE (even if you do only see it for a minute), then that's what it will be. I will say, in this case, that if that Logo DIDN'T spin, I'd be very worried I'd messed something up... I've had it for so long, I sometimes forget it isn't vanilla behavior... We install the first one to deliberately force you onto the original mod page - hopefully to read what the mod does, maybe even give the file an endorsement. The replacement ESPs and scripts are for compatibility reasons, and in no way takes away credit from those who did the work - it should be acknowledged and appreciated.

Your save has some of those baked into it's data - when you merged them into the Bashed Patch, they no longer appear to Skyrim. You COULD just ignore the warnings and play, but keep in mind that any references to those files original locations would be broken. It's working as intended. In essence, the game sees Bashed Patch.esp (which has all the data from the mods merged into it), but does not see the file names that are PART of the Bashed... if that makes sense? Let me try this: You run Skyrim with mods A, B, C, and D with no Bashed Patch. You play for a while. You create a Bashed Patch which then merges B and C. You now run with mods A, D, and the Bashed Patch. Skyrim can see the Bashed Patch (which contains mods B and C), but cannot see the esp files for B and C, so reports that they are missing. Hope that explains what's happening. Your best bet for stability is to start a new toon.

Despite Lexy having answered these both already, I'll add my two cents as well. I've never added tags through LOOT. Until a few months ago, I didn't even know it was a thing. If your experience shows that tags added in LOOT don't carry over, than I'd say that doing all the tags in WB just makes sense, so as not to do double the work. The guide hasn't had a big overhaul for clarity in quite some time - this is being worked on (slowly and in the background). The two instruction sets you are referring to can be used interchangeably, and will be "After installation, delete..." when the rewrite is done. There is no real difference between deleting a thing after it is installed and never having installed the file in the first place... but since many mods don't allow you to cherry pick which specific files get installed (there actually is a way, but it's never really talked about in the guide), it's simpler to just delete them after installation to keep this kind of confusion from happening.

You haven't linked MO2 to Nexus. Go into the Settings on MO2, click on the Nexus tab, and there will be a big button that will link the two. Click it and follow the directions.

Well, I think we can rule out Mesh or Statues... those issues result in instant CTD, not a delayed one. The first thing that comes to mind is scripting lag, but let's check a few other things first. You mention you've done both the Vanilla and Start in the Wild. Both of those are in the Helgen area... try a few other areas (Solitude Docks, for example) and see if the same thing results. If it doesn't, we will at least know it is something in that general area that is causing the issue. For our future reference, if you could provide system specs as well, that may give some insight as well.

A) With regards to Frostfall, you can leave it inactive with no issues. B) For 83 Willow, that would require, at a minimum, a lot of patching to make it all work with CACO, IIRC. It's certainly possible. Not sure how likely it is to be added right now though - the Trello is on hold for new additions because of how backed up it is, so she and the Testing Team are a tad bit swamped.

Which guide specifically are we talking about? With 500+ mods and zMerge mentioned, I'm guessing Lexy's LOTDSE, but it's kind of important to know that so you can be directed to talk to the appropriate people.

First, nope. I always number points for emphasis. ;) Second, you're welcome. Third, it's not there because that is a well known and documented engine limitation that is not in the scope of the guide to inform you of. That said, question answered. I always have a great day. :)

OK, take this in the spirit intended, and not as the semi-angry diatribe it could come off as. First, STEP is under no obligation to 'inform the ignorant'. The FPS issue with Havok has been a well known and documented issue, dating from the original release of the game back in 2011. There are a large number of similar things, none of which are mentioned in 'large red letters at the very start'. Most of these are easily searchable, easily corrected, and not in the scope of the guide to correct. These have nothing to do with modding your game, they have to do with running your game. Second, and following somewhat the last point, they are also under no obligation to maintain anything. There are, to my certain knowledge, a grand total of two people who still work on the STEP project on something resembling a full time basis (and one of those, I'm not certain of). In the time since 2.10 was released, if you had read around these forums (and especially in the announcements) you would note that there has been a LOT of work going on in the background to bring in a new site, a new content management system, and a completely updated STEP 3.0 for Skyrim LE. This milestone is approaching fairly soon. What you consider 'reasonable' was not possible based on those two things alone. STEP is not intended to address 'broader issues', as it is now and always has been a 'Vanilla +' type guide. As to your concern about mod count... Take a look at Lexy's Legacy of the Dragonborn: Special Edition sometime. It's well over 500 mods and 100 GB of downloaded mods cobbled together. You are in NO danger of anything there, unless directions and best practices have been ignored. I get where you are coming from, but I would advise you to be more informed about things before you start throwing things out as you just did. While I know you don't intend to be negative, it's very hard to see your statement as anything but. I again remind you that this project is maintained solely at the discretion of TechAngel and Z. The fact that this guide is still around is a testament to it's flexibility in the face of time. It is known that STEP 2.10 is not current - there are numerous threads on this forums that talk about this, with workarounds and recommendations associated. I'd recommend doing a search or taking a look around.

For the first, likely it was a weather shift to a foggy weather. Second, it's likely physics going wild... is your FPS going above 60 FPS? The havok engine wasn't designed with that in mind.

First, I think you can manage waiting longer than a day. Not everyone here checks every thread every day. Give it some time. Second, if you are having physics issues, you likely aren't wrong and do need to cap your FPS. This is also called vSync, and the setting for it is located in your Skyrim.ini or skyrimPrefs.ini. IIRC, the setting you need to change is iPresentInterval. Anyone else, feel free to correct me.

The dummy ESPs should be handled by LOOT sorting. No need to worry.