Jump to content
  • 0

STEP Extended - MO Screenshot Examples


I have uploaded an album on Imgur that shows an example of a Extended install in MO. I have also included a screenshot illustrating the instructions for SKSE.


For ease of reference, I have removed any mods I installed on top of STEP for these screenshots.


Always remember to closely follow the STEP instructions. Due to the nature of LOOT, your plugin list in the right pane may not look 100% like mine. This is just an example of one setup.


Also note that the text version of the STEP guide (i.e. the wiki) will always be more up-to-date than the linked videos. The videos are there to give you a general idea of how it is done, but for the specifics, always follow the text of the STEP wiki!


Lastly, when you download these mods in MO, you will have some items in the "Version" field in red, and possibly slightly different names for the mods in the left pane. This is just how I set it up (telling certain mods to ignore updates, etc.), along with creating the categories in MO to fit the STEP categories. No need to worry about these things for a standard STEP install, as they don't affect the game, and only help with organizing MO.



[spoiler=First screenshot description]

This is what a STEP Extended Skyrim mod install should look like upon completion in Mod Organizer.


Note that the individual plugin load order on the right pane may vary slightly. This is inherent in LOOT. If LOOT doesn't sense that a plugin needs to moved in the load order, it doesn't move it. This can result in different (but similar) load orders having the same desired effect.


In the first screenshot, you will notice a mod not in STEP, Memory Blocks Log. This is a good tool to determine if the SKSE memory patch is working right. If not using it to test, leave it unticked.


The Hi-Res texture packs and the Unofficial High res patch are dummy plugins, and should be unticked in the right pane.


The "Weapons & Armor_TrueWeaponsLvlLists.esp " is one of the four mods merged into the bashed patch, and after creating the bashed patch it is automatically left unticked.






[spoiler=Second screenshot description]

"GQJ_DG_vampireamuletfix.esp" is another of the four mods merged into the bashed patch.






[spoiler=Third screenshot description]

"Complete Crafting_TrueWeaponsLvlLists.esp" is yet another of the four mods merged into the bashed patch.


"FarmhouseChimneysCRF.esp" will not be in your plugin list if you follow STEP. The Farmhouse Chimneys CRF patch has not been updated for USLEEP, and requires using Mator's update script to make it work. I have disabled and highlighted it to let you know to ignore it, as this plugin will not be in a standard STEP install.





[spoiler=Fourth screenshot description]

"Traps Make Noise.esp"  is the last of the four mods merged into the bashed patch.






[spoiler=Fifth screenshot description]

"AOS_Reduced_Reverb_Addon.esp" probably won't be in your plugin list, either. It is the optional reduced reverb patch from Audio Overhaul Skyrim. I have left it disabled and highlighted to let you know to ignore it if it doesn't apply to you, as it will usually not be in a standard STEP install.






[spoiler=Sixth screenshot description]

Here you can see the Archives tab in the right pane. Everything should be ticked in the Archives tab. Most files will be automatically ticked, but some files you will need to manually tick.


Note the order of the HighResTexturePacks. They must be ordered as shown, and will be if they are ordered correctly in the left pane (shown in the first screenshot).






[spoiler=Seventh screenshot description]

In the right pane, you need to manually tick the STEP Optimized Vanilla Textures S1 and S2 BSAs. The order of S1 and S2 doesn't matter.


This screenshot and the previous ones cover all of the mods in the left pane. Note the Output files generated by the different patchers - the Bashed Patch from Wrye Bash, the FNIS Output from Fore's New Idles in Skyrim, the DSR Output from Dual Sheath Redux, and the two DynDOLOD Output files (which I named LOD Textures and DynDOLOD Output).






[spoiler=Eighth screenshot description]

In the right pane, note that BWS.bsa needs to be manually ticked.


Follow the STEP instructions, and install and run the patchers in the sequence shown on the wiki and in the left pane of the screenshot. As each patcher is run, it should be the last thing in the load order. If re-running patchers, untick in the left pane any that come later on in the STEP instructions until you get to them.


Before making the Bashed Patch, make sure every plugin in the right pane is ticked. Make sure the LOOT Metadata rules were properly inputted into LOOT, and LOOT was ran. Then make the Bashed Patch. Per the STEP instructions, re-tick "WM Trap Fixes.esp" after creating the bashed patch.


Continue with the STEP instructions for FNIS and DSR. For DynDOLOD, follow the STEP procedures exactly, making sure to untick Birds and Flocks from the left pane. It is fine to leave the dummy plugins (HighResTexturePacks and Unofficial High Resolution Patch) unticked, as DynDOLOD accounts for the High Res Texture Packs already.


After you follow the STEP recommended procedure (running the two DynDOLOD scripts and create the fake mods, etc.) make sure you remember to re-tick Birds and Flocks in the left pane. Run LOOT one last time, and you should be done!


STEP works very well, as long as you follow the detailed instructions in the wiki carefully.


Remember to always follow the text of the guide for exact details. It is much more up to date than the videos could possibly be. You obviously can't make a new video each time an edit is made to the STEP guide. :-P







[spoiler=SKSE screenshot description]

Here is one last screenshot to help show the last step in installing SKSE (adding the .ini file).


Follow the STEP instructions. After moving the one .exe and two .dll files directly into the Skyrim folder (not the Data folder), install the SKSE scripts into MO, creating the "SKSE" mod you see highlighted in this screenshot.


Right click as shown, and choose "Open in Explorer". Create a new folder called "SKSE". In the SKSE folder, right click and create a new text document, and name it "skse.ini". Make sure Windows is showing you the file extensions, otherwise you might end up with "skse.ini.txt", which won't work.


Alternatively, download the pre-made SKSE file linked to on the STEP page. Either way, it needs to be named "skse.ini" and put in a folder named "SKSE", and it needs the values shown in the screenshot.


Use the mod Memory Blocks Log by Sheson to confirm your SKSE is setup correctly. If so, the log from that mod should read "512, 256". This corresponds to the 768, 256 settings in the skse.ini. The first number in the log will always be 256 less than the number in the skse.ini.





Here is a link to the full album on Imgur: https://imgur.com/a/dw4zN

Edited by Nebulous112
Updated to concur with current STEP instructions
  • Upvote 2

Share this post

Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

I found a couple minor errors, due to me normally not running a standard STEP Extended install (I usually add some mods on top). I re-uploaded some images to fix.


If anyone does notice any errors, please let me know and I will fix the description or upload a new screenshot.

Edited by Nebulous112

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By sheson
      DynDOLOD DLL for Skyrim, Skyrim Special Edition, Skyrim Anniversary Edition and Skyrim VR
      So far all versions of DynDOLOD use the SKSE plugin PapyrusUtil for the optional dynamic LOD in the game. Starting with version 2.45 there is now the alternative DynDOLOD DLL available.
      The current DLL version is 2.45. It works with dynamic LOD generated by DynDOLOD Standalone 2.45 and newer.
      Read the ..DynDOLOD\Docs\DynDOLOD_DLL.html included in DynDOLOD Standalone for an explanation about DynDOLOD DLL, installation instructions (overwrite papyrus scripts of DynDOLOD Resources) and how it works.
      If there are problems with it, check DynDOLOD_DLL.html and the DynDOLOD FAQ first before posting.
      If a DynDOLOD.DLL version is required for a game version that is not listed below, request it in this thread. First, search this thread if it has been requested already, though. The future will tell how long it takes to release updates.
      Typically a new DynDOLOD.DLL is required for each new game version, but not each new SKSE version. For example a DynDOLOD.DLL compiled with SKSE64 2.0.9 also works with SKSE64 2.0.10 for the same game version.
      Nexus Downloads for DynDOLOD 2.45 and higher
      DynDOLOD DLL for Skyrim
      DynDOLOD DLL SE for Skyrim Special Edition
      DynDOLOD DLL VR for Skyrim VR
      Mega Mirrors:
      DynDOLOD.DLL + Scripts for Skyrim 1.9.32 (overwrite the papyrus scripts included in DynDOLOD Resources)
      DynDOLOD Scripts for Skyrim Special Edition and Skyrim VR (overwrite the papyrus scripts included in DynDOLOD Resources SE)
      DynDOLOD.DLL for Skyrim Special Edition 1.5.39
      DynDOLOD.DLL for Skyrim Special Edition 1.5.50
      DynDOLOD.DLL for Skyrim Special Edition 1.5.53
      DynDOLOD.DLL for Skyrim Special Edition 1.5.62
      DynDOLOD.DLL for Skyrim Special Edition 1.5.73
      DynDOLOD.DLL for Skyrim Special Edition 1.5.80
      DynDOLOD.DLL for Skyrim Special Edition 1.5.97
      DynDOLOD.DLL for Skyrim Special Edition 1.6.318
      DynDOLOD.DLL for Skyrim Special Edition 1.6.323
      DynDOLOD.DLL for Skyrim VR 1.4.15
    • By irisquexo
      Hi guys I'm new here so hopefully this is the right place to post this.
      When I try launching Skyrim SE through Mod Organizer 2 I get the error "REL/Relocation.h(567): failed to open file"
      Before this error I was getting the error "REL/Relocation.h(548): failed to open file" but I uninstalled and reinstalled the engine fixes and SKSE libraries. After doing that and relaunching I get the error I mentioned above. Do you guys know what I could have done wrong? I'm really new to messing with mods so it's probably something I did wrong... I've made sure all plugins are enabled and all mods are installed with their masters except for the ones below because I can't find the appropriate mod that goes with it so maybe that could also be the issue. I'm pretty sure I have "Blues Skyrim" but the creator renamed it so that's why MO2 is detecting it as missing. Idk if that's the case with the other ones though.
      Missing masters:

      Master                                                                               Required By
      Blues Skyrim.esp                                                              Eli_Breezehome [PATCH - DOS (Director's Cut) SE VER1.4] (STD).esp
      Skyrim Better Roads - All In One - Merged.esp                Settlements Expanded SE - Skyrim Better Roads Patch.esp, Skyrim Better Roads - All In - One - Merged - PATCHED.esp
      Soljund's Sinkhole.esp                                                      Settlements Expanded SE - Soljunds Sinkhole Patch.esp
      Tes Arena - Skyrim Frontier Fortress.esp                         Settlements Expanded SE - Legendary Cities Patch - AIO.esp
      Whistling Mine.esp                                                           Settlements Expanded SE - Whistling Mine Patch.esp
      also another problem is when I run LOOT it gives me the error 
      Loot failed to run
      Cyclic interaction detected: ELE_SSE.esp --[Master]-> SoS_ELE_Patch.esp --[Group]-> Luminosity Lighting Overhaul.esp --[Master]-> SoS_Luminocity_Patch.esp --[Group]-> ELE_SSE.esp
      If anyone knows what I could do to fix this, that would be amazing. Thank you

    • By JackGee
      Hi there peoples,

      First time posting, so if this isn't allowed please just let me know. Looking for a bit of support, as been scratching my head for ages now and getting nowhere.

      I have used MO2 + xEdit in the past and never had any issues with it. However, decided to mod Fallout NV again. When trying to run FNVEdit through MO2, it doesn't seem to complete the action as LOOT tells me after cleaning that it still needs cleaned. I have made sure the installation directory for MO2 isn't in the Fallout folder. It's all on my C drive (SSD). Tried running as admin ect. Clearing read only. Just can't seem to get it working.

      Any advice or help is appreciated.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.