SkyrimLE:3.0.0

From Step Mods | Change The Game


Info-Logo.png

NOTE

This is the current version of the Step SkyrimLE Guide. Don't forget to endorse Step on the Nexus if you like the guide. Please report any problems or confusing instructions on the latest Feedback & Bug Reports pinned forum topic.


STEP Skyrim LE Guide[edit | edit source]

This is the official v3.0 release of the Step Skyrim LE Guide. It'll now be considered a "retired" gaming guide, meaning we will not be releasing updates to it, beyond continued routine maintenance.

There have been many changes, so check out the Changelog for all the fine details.



About STEP[edit | edit source]

A Foreword

Created by TheCompiler, STEP is a collaborative project with input from the modding community, technical volunteers, and project administrators. The goal is to provide tested and validated methods for establishing and maintaining an enhanced modded Skyrim. Thus, the Guide provides detailed, well-tested build instructions for a solid modded Skyrim that achieves an enhanced, vanilla experience. It's meant to be installed in its entirety and not piecemeal.

The STEP team collects information from the modding community through extensive mod testing, detailed reviews, feedback, and suggestions exchanged on the Step Community Forums. Posting rules apply, so be sure to read and follow them. Engage and enjoy a warm welcome and plenty of high-quality support from a large community of experienced members.

New to Modding?[edit | edit source]

We recommend that you ...

  • read through this Guide at least once before attempting installation.
  • follow all linked guides and read through them, as well.

There is a lot of information to absorb and learn in order to successfully build a modded game. We and the community, have brought together a lot of this information into guides as a free and hopefully convenient resource for all. New and experienced modders alike will find many answers within these guides and linked resources. This Guide is written in such a way that it expects users to know the basics of modding and related tools (e.g. mod managers, LOD optimizers, configuration utilities, etc.). However our support forums are always available for our users.

Nomenclature[edit | edit source]

The following nomenclature is used throughout this guide and should be understood before proceeding.

  • 'tick' means 'check': Frequently, the word 'check' or 'checked' can mean 'ensure' in addition to "check mark", so 'check' is not used where it is synonymous with 'tick' to avoid any mistakes that can (and have) happened from this conflation.
  • Baseline: An installation of a mod using the recommend file option listed within the Baseline column of the mod tables below.
  • STEP Patches: A "patch" is a plugin that allows two or more mods to work together without conflicting. The STEP Patches are such plugins, but allow all of the mods in the STEP Guide to work harmoniously together. Some users refer to this as a conflict resolution patch or "CR Patch".

Minimum System Requirements[edit | edit source]

We recommend the following hardware configuration for running a STEP Skyrim LE installation at a resolution of 1920x1080. The minimum requirements will allow most users to install and run the Baseline options, which are Skyrim LE's recommended requirements. The recommended requirements for this Guide will allow most users to install and run a modded setup beyond that of the Baseline options (higher quality options). For those wishing to use high quality options at resolutions higher than 1920x1080, be advised that a more powerful system will likely be required.

Hardware Minimum Recommended
Windows OS Windows 10 64-bit Windows 10 64-bit
CPU Intel Core i3/equivalent (dual core) Intel Core i5-4430 or equivalent
System RAM 8 GB 8 GB or higher
GPU Nvidia GTX 780 3GB / AMD R9 290 4GB Nvidia GTX 970 or equivalent or better / 4GB VRAM or higher
Drive Space ~50 GBs ~70 GBs
Monitor Resolution 1920x1080 1920x1080 or higher

Time Requirement[edit | edit source]

Users should be aware that it will usually take anywhere from several hours to a several days to complete this Guide from start to finish. Since this is a start to finish process, a recommend schedule for completing it is:

Day 1 : Steps 1 - 3
Day 2 : Step 4
  • Step 4 is installing all the mods. Depending on download speeds and previous modding knowledge, this step could span 1-3 days.
Final Day : Finish the remainder of the Guide.

The overall message here is that STEP encourages users to always follow proper computer ergonomics when modding! Remember to take breaks and happy modding!


Mod Tables Legend[edit | edit source]

Mod Name Baseline Quality Options DLC Required Notes
Mod NameWikilink.png Baseline LowQuality.png HighQuality.png
DG
Notes
Core Mod STEP:Core mods are indicated by the presence of a green vertical bar in the row at the immediate left-hand column of the table.

STEP:Extended mods include these PLUS all the remaining mods in the list.

Mod Name Shortened version (where applicable) of Nexus mod name presented as a link to Nexus for download.
Wikilink.png Link to the mod's Wiki page.
Baseline This notes the STEP Baseline version or option of the corresponding mod, and usually refers to options affecting performance/quality. General suggestions are located in the "Notes" column.
Quality Options Indicates if there are performance-friendly or performance-unfriendly versions of the mod relative to the Baseline recommendation:
 LowQuality.png       Relative to Baseline, a lower quality, less demanding version of the mod is also available.
      HighQuality.png  Relative to Baseline, a higher quality, more demanding version of the mod is also available.
 LowQuality.png HighQuality.png  Relative to Baseline, both lower and higher quality versions of the mod are available.
DLC Required Any DLCs listed here are required for the mod to function. If all DLCs listed are not present do not use this mod.
Notes Brief notes that apply to the mod or installation. In some cases, mods with many alternative options will include a suggested option. These suggestions will take the form of: "STEP recommends 'Option A'." In other cases, there may only be one appropriate alternative option that fits the STEP Mandate. These instructions will take the form of: "Use 'Option A'."


STEP 1[edit | edit source]

Game & Tool Installation

Game Installation and Modding Setup[edit | edit source]

Those who have not completed the System Setup Guide should stop and do so now. This Guide expects that all users have previously completed the instructions in related guides or are at least familiar with those steps and ramifications of not having completed them.
Users deviating from our instructions and recommendations will need to reinterpret other instructions and recommendations in this guide accordingly. Make sure to note any such deviations for later reference.

Start Out Clean![edit | edit source]

It is particularly important for new users begin with clean installations of both Steam and Skyrim in order to be successful with the setup of this Guide the first time through.
PLEASE READ EACH SECTION BELOW CAREFULLY, as no information included in this Guide is irrelevant!

Mod Organizer 2[edit | edit source]

Mod Organizer 2 is the successor to Mod Organizer, and is now the official mod manager for all STEP game guides. It supports both 32-bit and 64-bit versions of Bethesda games. The major changes it brings are ...

  1. A return to normal plugin/BSA relationship - Users will no longer be able to load BSAs without loading the corresponding plugin, as they did with MO. The plugins must be active for the BSAs to load, which is the intended behavior that the game expects.
  2. New MO2 installation options - Users will have the choice between installing MO2 in "standalone" or "portable" mode. Unless Merge Plugins is going to be utilized, it’s purely an individual preference. Merged Plugins will currently only work when MO2 is installed and used in “portable” mode. “Standalone” mode is recommended for use with this Guide. This allows us to design all of our game guides around using MO2's "instances". This means one MO2 installation is used for all supported games. Users should decide how they wish to install and use MO2 before continuing; keeping in mind the space requirements mentioned in our System Setup Guide.
Moicon.png

MO2

This guide assumes that the reader is familiar with MO, so if that is not the case, please see the Mod Organizer Guide.

Tools Installation and Setup[edit | edit source]

STEP recommends the tools for modding be installed and setup as “standalone” applications, when possible. This means a tool is installed once and used for all games. Most of the modding tools used already have this feature built in and some are meant to be used as such. Following this recommendation will also reduce redundant tool installations; thus, saving hard drive space, and it's more organized. The instructions throughout this Guide will assume the tools are installed as “standalone” applications. However, users are free to set up their tools as they see fit.

Tool Installation[edit | edit source]

Users should install the tools to the location created while following the System Setup Guide (i.e., ../Modding/Tools/). Install the following tools to that location:


Mod Name Baseline Instructions

Template:ModTable/RowTemplate:ModTable/RowTemplate:ModTable/RowTemplate:ModTable/RowTemplate:ModTable/Row


The "Modding" folder structure should now reflect:

  • ../Modding/Steam (optional; may be installed elsewhere)
  • ../Modding/Tools
    • ../Tools/BethINI Standalone
    • ../Tools/DynDOLOD
    • ../Tools/LOOT
    • ../Tools/Mod Organizer 2
    • ../Tools/xEdit
    • ../Tools/xLODGen


STEP 2[edit | edit source]

Tool Configuration

Mod Organizer 2 - Configuration[edit | edit source]

Initialization[edit | edit source]

STEP recommends using all applications as standalone programs, including Mod Organizer 2. The below instructions for MO2's first run reflect this. If MO2 is run in Portable mode, users will need to adjust the instructions as appropriate. To initialize Mod Organizer 2:

➕ [Click to show]➖ [Click to hide] Initialization Instructions


  1. Launch MO2 by running its executable (e.g. ..Modding/Tools/Mod Organizer 2/ModOrganizer.exe)
  2. Upon launch, users will have a choose between setting it up as portable or create a new instance. Choose [New - Create a new instance.]
  3. Select SkyrimLE from the drop-down and choose [OK].
    • A prompt will appear informing you about the option of changing the location of data stored. Read it and click [OK].
  4. The installer should automatically detect the Skyrim LE installation (e.g. ..Steam/steamapps/common/Skyrim). Select it.
    • If it didn't find the location, browse to to the Skyrim LE installation path.
  5. Another prompt will appear for first time installers asking to run the tutorial or not. First time MO users should run it for a quick lesson on MO. Experienced MO users can skip it.
  6. MO2 is now ready to use.

Settings[edit | edit source]

The only settings covered here are to enable MO to download mods from Nexus.

➕ [Click to show]➖ [Click to hide] Nexus Mods Connection


  1. Open the MO settings by clicking on the Configure settings and workarounds icon.
  2. Click on the Nexus tab.
  3. Click the [Connect to Nexus] button under the Nexus Connection section.
  4. This opens a browser window to Nexus Mods. If necessary, login. Then click the [Authorize] button and close the window.
  5. Upon returning to MO window, users should find their Nexus account information populated.
  6. Click [OK] to close the settings window. If MO prompts a restart, let it.

Profile Setup[edit | edit source]

Now users will take advantage of Mod Organizer's profile feature by creating/editing two profiles for use during this Guide:

➕ [Click to show]➖ [Click to hide] Profile Setup Instructions


  1. Launch MO2, choosing the Skyrim LE Instance.
  2. On the default profile, arrange the mods in the left pane in the following order:
    1. DLC: Dawnguard
    2. DLC: HearthFires
    3. DLC: Dragonborn
  3. Click the Configure Profiles button on the menu bar.
  4. Select the Default profile and click [Rename].
  5. Rename this profile to Vanilla Skyrim or something similar
  6. Ensure the Use profile-specific Game INI Files box is ticked and select [OK].
    • Users can also tick Use profile-specific Save Games, if desired.
  7. Ensure the renamed profile is still selected and click [Copy].
  8. Name the new profile STEP Skyrim LE, or anything similar.
  9. Tick the same boxes from step 6, above.
  10. Close the window by clicking [Close].
    • Users will likely see a window saying some INI files were missing and will be copied. This is normal.
    • If an error is displayed about missing "modlist.txt" files, restart MO (or do a system reboot if one hasn't been done yet).
  11. Ensure that the STEP Skyrim LE profile is the currently selected profile in the Profile drop-down menu.

Tool Setup[edit | edit source]

All tools installed in Step 1 should be added to MO2. Some tools will have been auto-detected and added already; however, ensure the settings below are set for all tools, regardless. xEdit is used for this example:

➕ [Click to show]➖ [Click to hide] Tool Setup Instructions


  1. Click the [Configure the executables...] button at the top of the main Mod Organizer window.
  2. Over the left pane of the executables config, click the [+] to add a new executable, and then [Add from file...].
  3. Navigate to the TES5Edit.exe file (e.g. ..Modding/Tools/xEdit/TES5Edit.exe).
    • This should auto-fill most of the fields.
  4. Change the title to xEdit.
  5. The following arguments can be helpful. Input them in the Arguments field separated by a single space:
    • e.g. -IKnowWhatImDoing -TES5 -AllowMasterFilesEdit
    • "-IKnowWhatImDoing": This turns off a warning presented when users make edits.
    • "-AllowMasterFilesEdit": By default xEdit will not allow master file editing. This allows users to edit these files.
  6. Click [Apply].
  7. Repeat these steps to add the remaining executables as indicated in the table below:


Tool Setup Table

Executable Title Argument(s)
TES5Edit.exe xEdit -IKnowWhatImDoing -TES5 -AllowMasterFilesEdit
SSEEditQuickAutoClean.exe xEditQuickAutoClean -TES5
DynDOLOD.exe DynDOLOD -TES5
LOOT.exe LOOT --game="Skyrim"
TexGen.exe (installed with DynDOLOD) TexGen -TES5
xLODGen.exe xLODGen -lodgen -tes5 -o:"C:\Modding\Tools\xLODGen\xLODGen_Output\"

Users can arrange their tools in any order they wish using the up and down buttons above the list. This will dictate the order they are listed in the MO "Run" dropdown menu. When complete, close the window by clicking the [OK] button.

BethINI Setup[edit | edit source]

BethINI needs to be run for the current MO2 profile to establish the INIs before beginning the mod installations. To do this:

➕ [Click to show]➖ [Click to hide] BethINI Initialization and Setup


  1. Close MO2 and run BethINI (e.g. ..Modding/Tools/BethINI/BethINI.exe).
  2. Select "Skyrim" from the game selection box.
  3. Allow BethINI to handle custom INIs, if prompted.
  4. Go to the Setup tab
    • Ensure the Game path is correct (e.g. ../Modding/Steam/steamapps/common/Skyrim).
    • Ensure the Mod Organizer path is correct (e.g. ../Modding/Tools/Mod Organizer 2).
    • For the INI Path, select Mod Organizer - STEP Skyrim LE from the drop-down menu. NOTE: This depends on the MO2 Profile Setup
      • If BethINI does not automatically find the profiles, browse to MO2's /Profile folder.
      • For 'instance' users, the profile will be stored in the user's /AppData folder (e.g. %LOCALAPPDATA%/ModOrganizer/STEP Skyrim LE/profiles/)
    • BethINI should restart whenever the INI path changes in order to associate the MO2 profile information.
  5. Return to the Setup tab.
    • The “Automatically Check for Updates”, “Auto-detect Invalid Settings”, and “Modify Custom INIs” boxes should be ticked.
    • If BethINI will be used for multiple games from a single installation, the “Always Select Game” box should be ticked.
  6. Select the Basic tab.
    • Ensure the Window Resolution matches the system resolution.
    • The recommended Antialiasing is "TAA".
    • The other recommended options to tick are:
      • Windowed Mode
      • Borderless
      • Vsync
      • Lock Frame Rate (optional) This reduces 'tearing' effects and is optional, depending on whether or not the graphics software is used to limit frame rate.
    • The [Medium] Preset is recommended as a baseline to avoid problems before initial testing when guide setup is complete (this can be changed at any time later).
    • Tick the box for Recommended Tweaks.
  7. Select the Detail tab.
    • Untick Reflect Sky (water reflections are not accurate with respect to the LOD of most custom builds)
  8. Return the the Basic tab, and click [Save and Exit].


Users now have a minimal setup for the game INIs for testing and running the game during the mod installations. Once all mods have been installed, BethINI will be run again to complete the INI setup.

Users should now relaunch Mod Organizer and ensure the STEP Skyrim LE profile is selected to continue with the Guide.

STEP 3[edit | edit source]

Cleanup and Considerations

LOOT[edit | edit source]

At any time during the mod installation process, LOOT should be used to sort plugin load order before running the game. This is necessary to ensure proper plugin priority (load order), which can have a dramatic impact on the game. Users not running the game during the mod installation step of the Guide can wait to sort after this step is complete. To sort with LOOT:

  1. Launch LOOT via Mod Organizer 2 from the executables drop-down menu at the top of the right pane.
    Template:Alert small
  2. Click the [Sort Plugins] icon at the top of the LOOT window.
  3. Several plugins will show warnings. The next section describes how to clean them up.
  4. Click [Apply] button, which has replaced the Sort button at the top.
  5. Close LOOT.
Info-Logo.png

NOTE

When running LOOT before completing the STEP Guide, additional warnings may be indicated. These will all be fixed by the end of this guide.

Up to this point, users should only have the following plugins, in the order listed:

  1. Skyrim.esm
  2. Update.esm
  3. Dawnguard.esm
  4. HearthFires.esm
  5. Dragonborn.esm

If the plugins are not in the order listed, run LOOT now.

Cleaning Vanilla Master Files[edit | edit source]

To resolve potential issues later, the vanilla plugin masters should be cleaned with xEdit.

Standard Cleaning Procedures[edit | edit source]

➕ [Click to show]➖ [Click to hide] Toggle cleaning procedures...


  1. Run xEditQuickAutoClean from the drop-down executable list in MO2.
  2. On the plugin selection window, double-click on the mod being cleaned (e.g. Update.esm).
  3. Once xEdit is finished, click [X] at upper right to close. A backup of the original plugin will automatically be saved into (e.g., ../xEdit Output/TES5Edit Backups) inside of Overwrite at the bottom of the MO mod list (left) pane.

Clean the Masters[edit | edit source]

Vanilla masters should be cleaned in the following order:

  1. Update.esm
  2. Dawnguard.esm
  3. Hearthfires.esm
  4. Dragonborn.esm
  1. Follow the standard cleaning procedures to clean Update.esm.
  2. Once Update.esm is cleaned, next clean Dawnguard.esm using the standard cleaning procedures.
  3. Next, complete the manual cleaning below for Dawnguard.esm...
➕ [Click to show]➖ [Click to hide] Toggle Dawnguard manual cleaning procedures...


  1. Run xEdit from MO.
  2. At the prompt, double-click on Dawnguard.esm.
  3. Once loaded, type in 00016BCF in the FormID field (above the mod list) and hit [Enter/Return].
  4. In the right pane, find the "XEZN - Encounter Zone" record.
  5. In the Dawnguard.esm column, right-click on the "RiftenRatwayZone [ECZN:0009FBB9]" entry and select [Remove].
    • If a prompt appears select Yes for each of these removals.
  6. In the FormID field again, type in 0001FA4C and hit [Enter/Return].
  7. On the Dawnguard.esm column, right-lick on the "Dawnguard.esm" header and select [Remove].
  8. In the FormID field again, type in 0006C3B6 and hit [Enter/Return].
  9. On the Dawnguard.esm column, right-lick on the "Dawnguard.esm" header and select [Remove].
  10. Now close xEdit.
  11. Ensure Dawnguard.esm is ticked in the pane, Backup plugins is ticked at the bottom of the prompted window and click [OK].


Once Dawnguard's manual cleaning is complete, follow the standard cleaning procedures to clean Hearthfires.esm, and then finally, Dragonborn.esm.

Moving the Cleaned Files[edit | edit source]

After the vanilla master files are cleaned, they should be moved into the "Cleaned Vanilla Masters" mod in MO, and the original files should be restored into the 'real' "Data" directory in the game folder. This makes Steam happy when "validating" files so that it remains unaware of changes. To move the new files and restore the original files, complete the following:

➕ [Click to show]➖ [Click to hide] Toggle instructions


Cleaned Masters

  1. On the MO window, click the [Open list options...] button at the top of the left pane, next to the profile selection drop-down.
  2. Choose Create empty mod, name it Cleaned Vanilla Masters, and click [OK].
  3. Move this mod up the MO mod list to just after "DLC: Dragonborn".
  4. Enable the new mod listing.
  5. In MO, hold Ctrl and double-click on the now-empty Cleaned Vanilla Masters mod to open it in Windows Explorer.
  6. Click the [Show Open Folders menu...] button above the MO mod list (left) pane, and select Open Game Folder to open the game folder in Windows Explorer (e.g. ../Modding/Steam/steamapps/common/Skyrim/, and open ../Data.
  7. Move the four cleaned master files from ../Data into ../Cleaned Vanilla Masters.

Original Masters

  1. In MO, scroll to the end of the mod list (left) pane, and hold Ctrl + double click on Overwrite to open in Explorer.
  2. Inside the "TES5Edit Backups" folder, rename the files to "MasterName.esm" (i.e. "Update.esm").
    • If there are multiple copies of any of the files, use the one with the earliest timestamp (the original).
  3. Click the [Show Open Folders menu...] button above the MO mod list (left) pane, and select Open Game Folder to open the game folder in Windows Explorer (e.g. ../Modding/Steam/steamapps/common/Skyrim/
  4. Move or copy the renamed files into the 'real' game "Data" directory (../Data), choosing to overwrite/replace, if asked.
  5. All Explorer windows can be closed now.
  6. Right click on Overwrite, select [Clear Overwrite], and click [OK].
Moicon.png

MO2

Any time Bethesda updates these master files, they will likely need to be cleaned again and replaced in MO2. Any previously cleaned versions of these same files that exist in the MO mod list must be either disabled or deleted first, because xEdit will see only the cleaned versions otherwise.

At this point, the Bethesda masters should be cleaned and the mod list order should reflect:

  1. DLC: Dawnguard
  2. DLC: HearthFires
  3. DLC: Dragonborn
  4. Cleaned Vanilla Masters

Template:Alert small

Understanding the STEP Patches[edit | edit source]

A “conflict resolution” patch, or CR Patch, is a plugin that resolves conflicts between various active plugins. They allow users to use various mods together without any major issues, while still achieving the desired outcome from the mods. Thus, the STEP Patches are one part patch and one part mod.

The STEP Patches are built specifically for the STEP mod list. They are required to run the this Guide and are dependent on specific mods within the mod list (those tagged at left with a green vertical bar). They will not resolve conflicts with any applicable mods that are not within the Guide's mod list, though.

STEP Patches[edit | edit source]

  1. STEP Skyrim LE - Conflict Resolution Patch (STEP CR Patch)
    • For those that would opt for their own custom lighting and weather mods
    • Patches all applicable mods except for Lighting & Weather mods
    • Required for all users!
  2. STEP Skyrim LE - Lighting & Weather Patch (STEP LW Patch)
    • For those that are using Guide's lighting and weather mod from the Lighting & Weather mod group.
    • Patches only the applicable Lighting & Weather mods; the CR Patch is still required!


Final Pre-Installation Notes[edit | edit source]

A Final Consideration
  • Remember that STEP:Core should be used as a base for ANY modded setup. It is a universal build and will not spoil any downstream setup or Packs, although there may well be a few minor redundancies whereby a STEP:Core mod is later installed again with some added or subtracted options.
  • Install mods in the order that they are presented in the following tables in order to achieve the desired result.
  • Read the ReadMe and other mod-related documentation that comes packaged with most mods. This includes the mod description on the Nexus. If the mod author has seen fit and taken time to create these reference materials, then they are relevant and important in the eyes of the mod author. This means that they are relevant and important to you!


STEP 2[edit | edit source]

Mod Installation


Warning-Logo.png

WARNING

Please read the following notice. Failure to heed these points may result in unnecessary delays in your install.


Info-Logo.png

NOTE

Consider the following while installing mods:

  • Mods should be installed in the order that they are listed to ensure that mods further down the list overwrite those occurring before them. This is necessary to ensure the desired in-game effect. Mods are otherwise listed in alphabetical order within each section, and any deviations from this are purposeful to achieve the desired outcome.
  • Always install plugins (ESPs/ESMs) unless otherwise noted. If there are not any notes associated with a particular mod, then all options fit the STEP mandate. The notes only provide instructions where necessary; otherwise, STEP encourages user customization.
  • Unless otherwise stated, follow LOOT's advice with regards to mod cleaning.
  • Users MUST familiarise themselves with the use of MO when installing mods. Some examples can be found in the MO guideMO guide on installing mods.


2.A. LOOT Sorting & Patches[edit | edit source]

At any time during the mod installation process LOOT should be used to sort plugin load order before stopping to benchmark and test Skyrim. This is necessary to ensure proper plugin priority order (load order), which can have a dramatic impact on the game (or at worst cause a CTD).

  1. Launch LOOT via Mod Organizer by clicking on the "Sort" button or directly from the executables drop-down menu.
  2. Examine the LOOT output carefully and look for any alerts or warnings and address each. The Plugins tab in MO (on the right side of the MO window) is where plugins can be activated/deactivated and sorted (either drag and drop or use Ctrl + Up/Down arrow keys to sort).

Template:Alert small

STEP includes patches for both STEP Core installations and STEP Core + Extended installations to save plugin slots. For users that may not want to install all of the mods included in STEP, check the page of required mods for the STEP Patches below. Users that decided they will not use the STEP Patches will need to install all relevant patches listed on that page. Take note of those plugins since they are not listed throughout the guide. Regardless, anyone can use the STEP Combined Plugin as long as DLC and SMIM are installed to save about ten plugins.

STEP Patches Requirements - For anyone that is not using the STEP Patches, it is recommended to keep this page open for reference.

2.B. Clean the Update ESM[edit | edit source]

To remove errors in the Bethesda master files, STEP recommends that they be cleaned with TES5Edit. This ensures maximum stability and compatibility within the Skyrim modding experience. At this time, Update.esm will be cleaned in the following manner (the DLC should be cleaned later according to instructions on their corresponding "mod" pages):

  1. Make a backup of Update.esm from <Skyrim>/data directory by copying it to the desktop (or somewhere else handy).
  2. Run TES5Edit through Mod Organizer.
  3. Right-click the list of plugins and choose [Select None].
  4. Double-click Update.esm.
  5. Wait for the Background Loader: finished in the right panel, and then right-click [Update.esm] and select [Apply Filter For Cleaning].
  6. Wait for the [Filtering done] Processed Records: message in the right panel, and then right-click [Update.esm] and select [Remove "Identical to Master" records]. If the Warning! prompt pops up, click [Yes, I'm absolutely sure].
  7. Wait for the [Removing "Identical to Master" records done] Processed Records: message, and then right-click [Update.esm] and select [Undelete and Disable References].
  8. Wait for the [Undeleting and Disabling References done] Processed Records: message, and then click the [X] at upper right of the program window to exit the program.
  9. At the prompt, checkmark Update.esm and Backup Plugins and click [OK].

At this point there are two possible outcomes, dependent upon how fast your disc drive is:

  • In the first case (typically slower drives such as HDDs), the Update.esm is now no longer in the data directory.
  • In the second case (typically faster drives such as SSDs), a cleaned Update.esm is now in the data directory (compare the filesize to your backup of Update.esm to verify that it has been cleaned--it should be smaller).

In the first case, you should now do the following:

  1. Restore the backed up Update.esm from step 1 to the data directory.
  2. In Mod Organizer, at the bottom of the left pane modlist is the Overwrite mod, now labeled red because files have been written to it. Double-click to open it.
  3. In Overwrite you will find two items: a TES5Edit Backups folder and Update.esm. Since you already restored your own backed up Update.esm to the data directory, right-click and delete the TES5Edit Backups folder and click Close.
  4. Right-click Overwrite and select Create Mod..., name it Cleaned Update ESM, and click OK.
  5. Drag and drop the new Cleaned Update ESM mod to the top of the left pane modlist.

In the second case, you are done! You can safely delete the backup as you shall not need it (if you wish to restore the original uncleaned Update.esm later, you can simply verify Steam cache and redownload it).

2.C.[edit | edit source]

The mods in this section are required for a properly functioning STEP installation. YES, ENBoost is needed by EVERYONE, including those that do not use ENB Presets!

No mods defined.

2.D.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.E.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.F.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.G.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.H.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.I.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.J.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.K.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.L.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.M.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.N.[edit | edit source]

No mods defined.

Benchmark32.png
Benchmark
Benchmark32.png


2.O. Launching STEP:Skyrim[edit | edit source]

Archive Management[edit | edit source]

Moicon.png

MO2

Mod Organizer allows loading archives without their dummy plugins.

  1. In the Plugins tab, deactivate HighResTexturePack01.esp, HighResTexturePack02.esp, HighResTexturePack03.esp, Unofficial High Resolution Patch.esp, STEP DLC Optimized Textures, STEP Vanilla Optimized Textures, Brawl Bugs CE.esp (Core users only), and BWS.esp as they are all dummy plugins.
  2. Go to the Archives tab.
  3. Tick Have MO manage archives.
  4. In the archive list, ensure all the mods are checked.

When ready to play for the first time after a STEP install, be certain to start a new character. In the past, we advised that you could use an existing save, but with this release, we feel it is imperative that you start a new game, as many mods included here will cause bugs on an existing save.

Template:Alert small

STEP 3[edit | edit source]

Tips & Troubleshooting Common Issues

3.A. Troubleshooting Common Problems[edit | edit source]

A heavily modded Skyrim can bring even a very powerful system to its knees. Maximum visual quality is highly dependent upon total on-card graphics-dedicated video memory (VRAM), the number of GPUs, and monitor resolution. The goal should be to maintain 30 or more FPS on average without any noticeable stuttering.

3.A.1. Failure to Launch[edit | edit source]

Skyrim still sometimes fails to launch, and the following are some of the most common causes and solutions:

  • Improper load order - Run LOOT and examine the output. Plugins out of order or plugins with missing masters will cause this. LOOT will sort everything properly, but certain patches installed with certain mods included with STEP:Extended will not apply under a STEP:Core install, so these plugins need to be un-ticked in MO or WB plugin lists.
  • Improper Bashed Patch - This can result from ticking options that are not explicitly mentioned in this guide, or it can result if the Bashed Patch was not rebuilt after a mod-list/order change.
  • Bad INI settings - If Skyrim.ini or SkyrimPrefs.ini were edited in a way that was not described in STEP 1.D. (or if a fresh, default INI was not used as a baseline), certain settings can cause this issue. The quickest solution is to revisit that section and regenerate a fresh INI with the recommended settings.

3.A.2. Crashes to Desktop (CTD)[edit | edit source]

There are unfortunately many reasons for CTDs just after launch or shortly thereafter, but if this guide was followed precisely, STEP mods should not be the cause. Following are some common causes and solutions.

  • Improper Load Order - Run LOOT and examine the output as in the previous section.
  • Missing Masters - If an active plugin is missing its dependent master, a CTD will occur immediately. To fix, either locate the missing master and add it in or deactivate the plugin missing its master.
    • MO will show a red exclamation icon next to the plugin, while Wrye Bash will show a red checkbox next to the plugin.
  • Improper Bashed Patch - See the previous section.
  • Bad INI settings - Yep, see the previous section.
  • Bad video settings or incompatible driver version - Revisit STEP 1.E. and verify settings, back them down to 'performance' options, or update to the proper video driver.
  • Windows environment issue - This is highly possible and unfortunately too difficult to prescribe any remotely ubiquitous solution other than restarting the computer and checking for conflicting processes (e.g., anti-virus/maleware). Google is a friend to all in need.

3.A.3. Semi-Invisible People, Objects or Misbehaving Walls[edit | edit source]

Following are some solutions:

  • Transparency Antialiasing - Turn off any transparency (adaptive) sampling if enabled under antialiasing settings of the graphics-driver software (see references under STEP 1.E.). Also, remember to download the latest graphic drivers.
  • Bad INI settings - If using ENB, set bFloatPointRenderTarget=1 in the SkyrimPrefs.ini.

3.A.4. Stuttering[edit | edit source]

  • Microstutter - This is an annoying 'glitchiness' when moving or panning for those using higher-end graphics cards (usually) or multiple GPUs in SLI or CrossfireX configs (purportedly). Follow the recommendations for ENBoost, noting in particular EnableVSync=true . If this does not resolve the issue:
    • Ensure that microstutter is not being confused with 'macro'-stutter, which is more severe and memory related. Remember: microstutter is very annoying, but not hindering in any way.
    • Try forcing vsync via Nvidia Inspector (Nvidia users) or RadeonPro (AMD users) ... sorry Intel users. Also (and this is very important), enable D3D-compatible triple buffering via RadeonPro. Nvidia Inspector users: D3D-compatible triple buffering is not available. Use D3Doverrider instead. This may also have a vsync function.
  • Macrostutter - This is most likely the result of using textures and meshes that exceed the limits of GPU VRAM. ENBoost should prevent this in most cases, but certain user configurations and/or hardware may not behave as expected:
    • Verify ENBoost settings and graphics settings described under STEP 1.E.!
    • Re-install the most performance-friendly versions of mods as indicated by the "Quality Options" column of the mod tables above.
    • Consult the DDSopt Guide to learn how to optimize textures accordingly.
    • Finally, Un-install Skyrim Flora Overhaul, which is easily the most VRAM-intensive mod in STEP (although there are others under STEP 2.F. and STEP 2.G. in particular).
    • Enable windowed mode via ENBoost (instructions at bottom of mod page).

3.A.5. Texture Flickering, Etc.[edit | edit source]

Refer to the Z-Fighting Guide.

3.B. In-Game Tips[edit | edit source]

  • The console can be activated by pressing the tilde ([~]) key, often located just below [Escape], while in-game.
  • ENBoost has a couple built in hotkeys that are helpful (can be adjusted in enblocal.ini section [INPUT]):
    1. Show FPS: [*] (on the numpad not shift+8)
    2. Free VRAM: [f4]
    3. Screenshot: print screen (Skyrim's screenshots do not work with ENB/ENBoost)
  • Steam screenshots are [f12], but if using a keyboard with multimedia keys it could be [shift+f12].
    1. Be aware [shift+f12] is also the ENB Series Graphics hotkey to toggle the effects on/off. ENBoost ONLY users are not affected.

3.B.1. Optimize Field of View (FOV)[edit | edit source]

Prior to 2008, the most common monitor resolutions were 16:10 aspect ratio (source). Since then, 16:9 has become the standard. The Skyrim FOV defaults to 65 and is optimized for a monitor aspect ratio of 16:10. Therefore, users with 16:9 monitors (e.g. 1920x1080) will want to increase their FOV to 70.59. Setting this in the INI does not persist, so it must be done via the console. Within Skyrim, open the console (tap the tilde [~] key) and type: fov 70.59. Those rare and unfortunate users stuck with 4:3 aspect ratio will need to reduce their FOV down to 55.93.

A helpful conversion calculator can assist in calculation of other monitor types and aspect ratios. To use:

  1. Change Resolution of single monitor to your total resolution (if using multiple monitors, use the combined resolution)
  2. Change Number of monitors? to the number of monitors being used Across and Tall (e.g., if you only have 1, set both Across and Tall to 1. If you have 3 beside each other, set Across to 3 and Tall to 1. If you have 4 monitors arranged so that it is 2 by 2, set Across to 2 and Tall to 2.
  3. Change Old Res or Ratio to 16:10.
  4. Change Old hFOV to 65.
  5. Your new optimized FOV value will be labeled New hFOV immediately below and to the right.

3.B.2. BIG Frame Drops During Cell Loading[edit | edit source]

This is a likely indicator that VRAM is too often operating at or beyond capacity (see 3.A.4).

STEP Packs[edit | edit source]

Community Add-ons

STEP Packs are generally intended to go over the STEP:Core build. Be certain to read the Pack instructions to determine what build the Pack is dependent upon.

Moicon.png

MO2

You will now experience one of the reasons why Mod Organizer is the chosen mod-management utility for STEP. Pack installation is a breeze, as it is possible to have profiles for each build dependency that a given Pack relies upon.

Consider reviewing some of the Packs that our users have been developing to augment STEP.

STEP Packs

User Contributions[edit | edit source]

How YOU Can Help

STEP can only get bigger and better with help from the user community. Even simply maintaining the current STEP is too much work for the core STEP team to ensure that the highest quality is maintained. We need people to help us identify mods that improve Skyrim while adhering to the STEP Mandate. We also need ongoing reviews and updates on mods that may be causing problems or that stray from the STEP philosophy. Finally, we need help from the community in terms of testing, benchmarking and analysis. More detail is presented in the Mod Testing Guide.

In order to suggest a mod, visit the Mod Suggestions section of the STEP Forums.

Info-Logo.png

NOTE

The STEP team will be beta testing a new mod-testing procedure and interface currently in final stages of development here on the STEP Wiki. Anyone interested in testing mods of any kind --whether included in STEP or not-- should contact the STEP administrators by email or on the forums (click on the link in upper left of header).

Call for Wiki Content Editors[edit | edit source]

The STEP Community Wiki is open to editing by all registered community members; however, we need assistance maintaining and creating new supporting content. We are particularly interested in obtaining a few people with a passion for writing and editing. Familiarity with wiki markup is preferable but not necessary. Interested parties please contact z929669 via PM on the forums (Please register on the forums and see the very bottom of the Forum Team page).

Call for STEP Mod Testers[edit | edit source]

STEP users interested in becoming testers, please contact z929669 via PM on the forums (Please register on the forums and see the very bottom of the Forum Team page). Once registered, record your system specs by clicking on the button and filling out the form. These specs will be associated with performance data by tester. Before deciding, read through the Mod Testing Guide to get a sense what mod testing involves.

Call for STEP Benchmarks[edit | edit source]

Users interested in helping out with the STEP Benchmarking Project, see our benchmarking guidelines and submit results on the forums (see link at upper left of site header bar).

Call for Forum Moderators[edit | edit source]

Regular STEP forum users interested in becoming moderators, please contact z929669 via PM on the forums (Please register on the forums and see the very bottom of the Forum Team page).


Thank you for reading and enjoy the game!


Credits[edit | edit source]

The STEP administrators would sincerely like to thank (from the bottoms of our fuzzy little hearts):

  • The authors of mods recommended in STEP
  • The authors of mods who granted permission for their mods to be placed inside the STEP Compilation
  • The core STEP Community for feedback, suggestions and input
  • The STEP testers for their good humor and rigorous analyses
  • The Nexus community
  • Bethesda Softworks for Skyrim (and TES in general)
  • Tannin for continued development and support of Mod Organizer


The core STEP team is:[edit | edit source]
  • DoubleYou - Release coordinator, Mod Organizer doctor, Wiki editor
  • EssArrBee - Release coordinator, Fallout survivor, STEP Patches maintainer
  • stoppingby4now - Main site developer, Semantic Mediawiki developer & extraordinaire, site founder
  • TechAngel85 - Release coordinator, ENB guide leader, FOMOD extraordinaire
  • TheCompiler - STEP creator, mod-list extraordinaire
  • z929669 - Wiki & forums content editor, main site administrator, hosting maintenance, site founder
  • Other active volunteer staff: Aiyen, GrantSP, GSDfan, hishutup, Kelmych, kryptopyr, oqhansoloqo, phazer11, rootsrat, torminater, WilliamImm, Xaviien
  • Farlo - Mediawiki developer & extraordinaire, Mod-list co-compiler, forums admin, site founder (out of commission since November, 2013)
  • MontyMM - Solutions developer (Semi-Automatic STEP), site founder (out of commission since December, 2013)

{{#css:STEP:StepGuide.css}}