DanimalTwo

In the installer check the "Install Everything Dragon DLC" box and you are good to go. After install follow the rest of the instructions.

Yes you should exclude the "Data" folder. It is installed with the "Vididian - Weather - Lighting and Climates of Tamriel Enhancement".

The mod is already included in Neovalen's Skyrim Revisited Legendery Edition.

There does not seem to be a conflict with the DATA - Flags.

Yep, that is what I use with GTX 680 4 GB.

@Neovalon: Just curious still SLI?

If you open Wyre BASH, you find those already have the BASH tags applied. Thus there is not need to add them.

For placement follow Neovalen's lead: https://wiki.step-project.com/User:Neovalen/Skyrim_Revisited_-_Legendary_Edition#Weather_Systems

For some silly reason I found your response funny.

You do realize you can find most prior versions of the ENB binaries here:https://forum.skyrimtuner.com/viewtopic.php?f=16&t=99

Once you have TES5Edit open, select none, select your STEP Core Patch. All mod dependencies should be listed. Then expand the "+" sign in you left pane for STEP Core Patch. Click every record and expand everything below doing the same. When you click on the record, if Improved Closefaced Helmets is listed in the right pane, right click on that record in the left pane as select "Remove". Do this from every record from Improved Closefaced Helmets included in the Patch. When done right click on the the left pane the STEP Core Patch and select 'clean masters'. If you did this right TES5Edit should only save changes to the STEP Core Patch. If anything else is checked for saving, you did things wrong. Simply uncheck everything to be saved and try again. I hope that is clear.

It looks like things are working and installed correctly. I am at a loss. I do not use SKSE_Elys_AltF4.

When you downloaded a mod to your MO/downloads directory it should show when you click the "downloads tab" in the right pane. Before you install, you should right click on the downloaded mod and select "Query info" which will retrieve the mod info from the Nexus. If you do not do this or some reason the Nexus is unavailable, instead of the version number the mod will give the install date as the version number in the left pane. You can fix this be double clicking on the mod and selecting the "Nexus info" tab. Then enter the correct mod id and version number.

If you haven't already, try installing the Memory Blocks Log found here: https://www.nexusmods.com/skyrim/mods/50471/? Install like any other mod through MO. The log file will appear in your MO/overwrite directory. It will tell you if you are running out of memory.

Your mods in the left pane SHOULD be in the order given in the STEP guide (you can change the order simply by clicking and holding down your left mouse button and moving the mod to where you want). You can find out what mods are conflicting by double clicking the mod name in the left pane and then selecting the conflicts tab in the newly opened window.

That is the correct file, but your load order is not correct. You need to configure and run BOSS through MO.

It looks like you did not setup your tools correctly. They should all be run through MO. Looking at your ESPs and ESMs you have not run BOSS as they are not in the proper order. Your load order is not handled by the loadorder.txt in your Skyrim folder. Your load order should look more like this: The file is located in MO/profiles/{your profiile name here}.

Some mods will overwrite the files you see in the left pane and have some of its files overwritten by subsequent mods (seen as a lightning symbol with +/- signs next to it). This is intended in STEP, which is why you should follow the STEP load order. In the right pane the ESMs and ESPs will be sorted by BOSS, which can be completely different from your mod order in the left pane. Again this behavior is completely intended. If a mod is completely overwritten in the left pane, it will have a grey lightning symbol next to it.

Sounds like you incorrectly installed SKSE using MO. What you should have done is extract the *.exe and *.dll files and place them in your Skyrim program directory (not the Data directory). Then install the SKSE Data directory using MO just as you would any other mod. In you "MO/mods/{SKSE directory name}/" directory create a subdirectory called "SKSE", nativigate to the SKSE subdirectory and create your SKSE.ini. The SKSE.ini should read like this: In the above, DefaultHeapInitialAllocMB=768 refers to the TOTAL memory used. Thus you will be using BLOCK1=512MB and BLOCK2=256MB. If you set DefaultHeapInitialAllocMB=512, you are actually using 256MB for BLOCK1 and are probably running out of memory.

The nice thing about MO is that it keeps you actual Skyrim directory "clean". There are exceptions of coarse like when using an ENB or SKSE. That is beyond the scope of this reply. I would first of all create a "clean" Skyrim install, this should not effect your modded game using MO, but based on your description it sounds like you corrupted you actual Data folder by putting things there that you shouldn't have (you should not use NMM at all to install mods). The proper way to install FNIS is as follows: 1. Install using MO just like you would any other mod. 2. Click your data tab in the right pane of MO and expand the tools folder (it should be close to the bottom). 3. Expand the GenerateFNIS_for_Users folder. 4. Right click on GenerateFNISforUsers.exe and select run as executable. 5. Select FNIS from the list of executables and select RUN. The files created will be placed in your Overwrite folder and you have to rerun FNIS, BOSS, BASH, and any SkyProc mods anytime you make mod changes. The files FNIS created are in the overwrite/meshes folder. Ideally, your Overwrite folder should be empty, but many people including myself, keep files there. These include your BASHed patch, user created patches (though you really should create a mod folder for those), FNIS, and any SkyProc mods you may use. Generally, you can delete everything in the Overwrite directory unless you have user made patches in there as all the other files will be regenerated when you switch profiles or make modifications to your current profile. After making changes to you current profile or switching profiles you will have rerun FNIS, BOSS, Wyre BASH, and any SkyProc Patches you may have (all through MO) which will recreate all the files. NEVER run FNIS, BOSS, BASH, or SkyProc patches outside of MO.

If you followed the instructions, you moved the .backup files to the original Skyrim folder. Then the only thing left in your MO/overwrite directory are your cleaned ESMs. If this is true, then do the following. In the left pane, at the bottom "right click" on Overwrite, select "create mod", and for the file name type "Clean Vanilla ESMs". Then move the newly created mod, containing only the cleaned "ESMs" to the top of you load order in the left pane of MO.

If using Windows 7 deleted files will appear in your Recycle Bin. This maybe true of other Windows versions as well, I just have no way of verifying. Generally speaking, you should not have any files in your Overwrite folder, but actually many people including myself do. In my case I follow Neovalen's SR:LE, and the only critical file is the "SR compatibility patch.esp" which I created myself after many hours using TES5Edit. The other files/folders I delete whenever I make mod changes as they are easy to recreate. Running FNIS (Fore's New Idols in Skyrim), BASH, and SUM (SkyProc Unified Manager) generate all the other files in the Overwrite folder. For me if I make mods changes and do not delete all files in the overwrite directory except the SR compatibility patch, SUM will run into problems with the garbage left behind. If using MO correctly, the files in your overwrite folder are not critical and can easily be regenerated.

Just overwrite the new version over the old. You should lose nothing. To be on the safe side backup your profiles directory.

The version of MO you are using no longer works with the Nexus. You will have to upgrade. There are no automatic upgrades for that version. You will have to download that latest version and install. The current version is v1.1.1.

If you haven't solved it yet, please post a screensot of your BUM settings for that mod so we can easier determine where things go wrong.The problem is that BUM does not support BOSS 3.0.0. At least it didn't work for me, as BUM requires a masterlist.txt, but BOSS 3.0.0 does not use that anymore it seems. I keep getting an error there is no masterlist.txt. The Beta version instead has a built in Metadata Editor which is supposed to do what BUM does. I might be wrong, but it is what it seems like.The current supported release for SRLE is BOSS Version 2.1.1. Use it and everything will work as expected.