Nebulous112

Yes. Move the .esp to optional. In the left pane, right click the mod, choose "Information...", then I think the tab is named "Plugins".

It is, but MO cannot handle .exe files, and I can't remember off the top of my head, but I don't think it can handle .dll files either. Hence the instructions to extract them manually. The instructions are correct. Edit: Thinking about it now, maybe I'm off base with MO not being able to handle the files. Maybe the issue is more the fact that MO would put files in the Skyrim\Data directory instead of the main Skyrim directory. Either way, it won't work installing it with MO. You have to do it manually.

I really have no idea when it comes to merging plugins, but Mator is fairly active in his forum here at STEP. If you have any unresolved questions, maybe pop by there. https://forum.step-project.com/forum/99-mators-utilities-support/

Update BOYD. v3.0 is the Legendary Edition Patch one.

I was thinking Legacy was so huge it would be a pack itself adding just it and some of its supported mods. Anyway, if you do end up adding Legacy, it would be awesome if you could throw any conflict resolution tips or anything you think might be useful info in the Legacy thread. If you happen to remember, and find the time, of course. ;-) My dream is STEP Extended + Legacy. Man, I might even switch over to the dark side (aka your guide...what else can you call something written by a Sith) if you got Legacy working...if I could handle it without Win 7. Stupid Windows 8 / 10 VRAM cap. I'd probably try regardless, lol. I have been following that mod for a long time, and it would be simply amazing to get it to play nice with STEP or SR:LE mods. Fair enough, I do see your point. If the extra resources of a simple check are too much for your system, what are you doing installing this or the main SR:LE guide anyway? Lol. I guess I just don't like waste, and my installs tend to be fairly solid anyway (I'm not hardly as adventurous as most folks in this thread...adding mods until your eyes bleed, lol). ;-)

No, that is incorrect. STEP mentions merging for some specific mods, but not others. I think it's mostly just to give you an idea of when merging is appropriate. Basically, if it is a hotfix or an addon, (this includes most optional files) it should be merged. If it is another full release of a mod (if it includes all the files from the old version), then you should replace. If it is a totally different mod on the same Nexus page, for example the STEP Compilation vs. STEP Optimized Vanilla Textures, then rename it to make a brand new mod listing in MO. Regarding your crashing...have you tried Memory Blocks Log to see if your SKSE is set up correctly? That would be my first step if I were you. https://www.nexusmods.com/skyrim/mods/50471/? Edit: Well, that was a lie. Not my first step. First step is to check if there are any flags listed for the plug-ins in the right pane. Pay particular attention to any with a yield sign. That means the mod is missing a "master" it is dependant on.

Is skse.ini in a folder named SKSE? Here is a screenshot I use to show STEP users how to create the .ini. Values are probably different for this guide though.

There is no need to log when not testing. If I don't crash or ILS, why would I test? Also, to test with MBL, why not just go to the Windhelm Docks and pick a fight? I think that's about the most intensive Block use a person will ever see in the game. If it doesn't crash there, I doubt it will ever crash due to Block 1 filling up. Playing the whole game with it on doesn't make any sense, IMO.

I definitely will. I'll report back once I've actually used it in game for a while and let you folks know what I think. It definitely seems worth it for the areas you mentioned, Greg, that have no markers at all in vanilla. However, I do not like the idea of marking skeleton / treasure locations... I'll let you folks know what I think after I play with it for a while. :-)

It's always a good idea to turn the logging off in the .ini for Memory Blocks Log (when not being used to test, of course). Why waste resources when not necessary? :-)

Glad to hear it! :-)

Those files need to be checked (ticked). MO will not automatically tick them for you.

Thanks, the STEP team has already been made aware, and the guide should be updated shortly. Not selecting anything is fine. The new "thinner meshes" option installs SP's alternate meshes which are installed by STEP users later in The Ruffled Feather anyway, and the patches necessary for STEP are included in the STEP Compilation. Since you asked, for future reference all topics for mods currently or formerly in STEP can be found in the Mod Anthology forum. Alternatively, the bug reports thread in the Releases forum would also be appropriate. Thanks again for the heads-up! :-)

No Stretching (by langley) Pictures from Nexus page: I found this looking through SR:LE. It seems like a decent fix, and might be a good fit for STEP.

I'm definitely going to try this mod out. It seems like a great addition to the game. Has this ever been seriously considered for STEP, with or without the MCM menu change?

I'm assuming you use MO. Do you see any flags that look like yield signs next to any of your plugins in the right pane?

I don't think so...the last update to WAF was in March of last year, before this thread was started.

FISS does that. Too bad only a few mods make use of it...

I really like the look of these compared to vanilla from the screenshots. I'll be adding them to my game.

I just wanted to chime in and say thanks to Shurah for the nice update:

Good to note that FNIS.esp was only included with v6 and above of FNIS. Before that, no .esp was needed.

Hi Pandore, your English is fine. Better than my French, for sure! What is your enblocal.ini settings? One thing that comes to mind just try installing lower quality textures for mods when available. If you added a bunch of mods after STEP, this may have just been too much for your computer to handle. Individually, all the higher texture mod options may not decrease performance very much, but when you add them all together it can make quite a difference.

It might be worth it to install Memory Blocks Log and see what the log says. The log produced should confirm whether the memory settings in skse.ini need tweaking or not.

I usually change that key to something more out of the way in enblocal.ini. I also change the Free VRam key as F4 is used by the SkyUI hot keys.

For screen archers, I believe. Edit: Bah, I thought I was responding to the latest comment, I didnt't realize there was another page (and Greg had already answered, and Rebel had already replied!).