DoubleYou

I normally just manually enter the correct number in the corresponding meta file.

Could you take a picture of the file in explorer (PrntScr)?

You're confusing load order with installation order. BOSS will place the ESPs where they belong.

Chat isn't a great idea for something like STEP, since it's always better to have threads that can come up in google search, rather than a lot of information that gets lost in a chatbox. :|This. Sent from Florida using my Enslaved Black Alligator.

If using ENBoost and not the ENB part of it, set bFloatPointRenderTarget=0

Seems like an abandoned project to me.

I almost have grown to like those messages... Sent from my totally awesome laptop using Windows Speech Disconfobulation Majiggy.

If your modding needs/desires are simplistic, than yes. If your modding needs/desires are like STEP, than no. I suggest a compromise, in-the-middle solution: unpack BSAs when they hinder a convenient modding installation. That will optimize speed and lessen issues.

We should probably remove Nitpick from Extended, since we're using Mod Organizer. Might give it an honorable mention for Wrye Bash users in 1.C Utilities.

Exact same idea, except I put them back into the related mods folder. You would probably have to do that in explorer if you're working with multiple logs.

To fix clipping of cloaks, use 360 Walk and Run Plus (by yukl).

For this and any other SKSE plugin log files, I recommend you move the associated logs back to the associated mod's folder and not delete them. This way you won't have to continually be emptying Overwrite of all these logs. When you move the log files to their mod files, it will write the log directly to the file and not generate one in Overwrite.

Are you sure it isn't your browser?

Thing is with most of these patches - any TES5Edit ninja can do them. I remember when AOS first came out, and I was making these patches myself. As soon as I finished making the patches, michaelrw had already done them and uploaded them, and I'm like, "If only I had waited!" The only advantage to making the patch yourself is that you can know exactly what you did. I always try to check the patches out at least, as some people got rather funny notions when it comes to patches.

Your enblocal MEMORY settings look a mess to me, although I ain't necessarily an enb guru. Since when are you reserving 512 mb? I've heard its best to keep this low to something like 64 or 128, as this is how much memory it won't use because you have reserved it. And 10240 for Video Memory? Maybe I don't understand that setting altogether, but that sounds rather high.

I'd load up your load order in TES5Edit and take a look at the mods modifying Braith and see which one might be causing this.

Perhaps you want to turn your uGridsToLoad back to 5?

I should have seen that coming.

Possibly. Depends which way the wind is blowing. Seriously though, weather affects like your entire environment, and a bunch of erroneous records under weather definitely is not going to have a positive effect.

AOS_CoT 3.1 compatibility patch.esp is bad. That is the old patch that doesn't work, and indeed is full of bad records by now. You must use the one on the AOS patches page.

You will have to TES5Edit the changes out if you use the STEP Patches, as using the patch without a master present will cause CTD.

I always make a mod specifically for TES5Edit backups and put the backups in there.

Each option is in a separate folder. Right-click, Set Data directory on the option until you get data directory. Do this for each option, merging each time.

The easiest way is to install it multiple times and merging for each option.

This does look useful!