Difference between revisions of "STEP:3.0.0"

From STEP Modding Wiki
Redirect page
m (Automated changelog ref)
m (Redirected page to STEP:0.1.0b)
Line 1: Line 1:
{{GuideTitleSE|releasedate=December 25, 2019}}<br>
+
#REDIRECT [[STEP:0.1.0b]]
{{VersionHeader}}<br>
+
<!-- {{#ifeq: {{#show: STEP:Main | ?DonationToggle#}} | True | {{DonationButton|Guide}} }} -->
+
<div class="nonumtoc">{{TOC right}}</div>
+
 
+
==STEP SE Core Guide==
+
Per our previous release, the "STEP Guide" [[STEP:versioning|versioning scheme]] facilitates our move towards a major change in the way we not only create guides but also with respect to our entire website and methodology. In totality, we've been calling this "STEP 3.0". This Guide version is "0.1.0" (since this a new guide specific to Special Edition, it's versioning starts fresh). It's a prequel or "Beta" to the Guide we will release with STEP 3.0. While we don't consider this release quite to the standards of a full-blown 'major' release, it still represents the entirety of the Guide as it will be released.
+
 
+
{{fc|#ddd|'''There has been so many changes that we highly recommend users reviewing the [{{canonicalurl:Changelog/{{PAGENAME}}}} Changelog], for all the fine details.'''}}
+
 
+
<blockquote style="color:#ddd;">- Visit the [http://forum.step-project.com/ forums] and provide feedback related to STEP. 
+
<br >
+
 
+
- Also follow STEP on [http://www.facebook.com/pages/STEP-Skyrim-Total-Enhancement-Project/175289219235392?sk=info Facebook].
+
<br >
+
 
+
- To support hosting and maintenance of the STEP Community Project, [https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=N5TLCEMXY7KQU contributions are welcome].</blockquote>
+
<br>
+
<br>
+
 
+
= About STEP =
+
<div style="color:#ccc; text-align:center; font-size:1.4em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">A Foreword</div>
+
Created by [http://wiki.step-project.com/User:TheCompiler 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 modding template. New modders can follow STEP explicitly to achieve an enhanced, vanilla experience, or more experienced modders may use it as general guide from which to build a foundation.
+
 
+
The STEP team collects information from the modding community through extensive mod testing, detailed reviews, feedback, and suggestions exchanged on the [http://forum.step-project.com/ STEP Community Forums]. Posting [http://wiki.step-project.com/Guide:STEP_Community_Citizenship 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.
+
<br/>
+
 
+
===New to Modding?===
+
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 visitors.
+
 
+
==Nomenclature==
+
The following nomenclature is used throughout this guide and should be understood before proceeding.
+
 
+
*{{fc|#e6b69e|Baseline}}: An installation of a mod using the recommend file option listed within the '''''Baseline''''' column of the mod tables below.
+
*{{fc|#e6b69e|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 ==
+
We recommend the following hardware configuration for running a ''STEP SE Core'' installation at a resolution of 1920x1080. The minimum requirements will allow most users to install and run the Baseline options, which are Skyrim SE'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.
+
<br/><br/>
+
 
+
{| class="sitetable" style="width:60%; float:left;"
+
! Hardware
+
! Minimum
+
! Recommended
+
|-
+
! style="color:#ccc; text-align:left;"| Windows OS
+
| style="text-align:left;"| Windows 7 64-bit or later
+
| style="text-align:left;"| Windows 7 64-bit or later
+
|-
+
! style="color:#ccc; text-align:left;"| CPU
+
| style="text-align:left;"| Intel Core i5-2400 or equivalent
+
| style="text-align:left;"| Intel Core i5-4430 or equivalent
+
|-
+
! style="color:#ccc; text-align:left;"| System RAM
+
| style="text-align:left;"| 8 GB
+
| style="text-align:left;"| 8 GB or higher
+
|-
+
! style="color:#ccc; text-align:left;"| GPU
+
| style="text-align:left;"| Nvidia GTX 780 3GB / AMD R9 290 4GB
+
| style="text-align:left;"| Nvidia GTX 970 or equivalent or better
+
|-
+
! style="color:#ccc; text-align:left;"| Monitor Resolution
+
| style="text-align:left;"| 1920x1080
+
| style="text-align:left;"| 1920x1080 or higher
+
|}
+
{{clear|left}}
+
 
+
== Time Requirement ==
+
Users should be aware that it will usually take several hours to complete a STEP Guide from start to finish. STEP encourages users to always follow proper [https://uhs.princeton.edu/health-resources/ergonomics-computer-use computer ergonomics] when modding. Remember to take breaks and happy modding!
+
<br/>
+
<br/>
+
 
+
= STEP 1 =
+
<div style="color:#ccc; text-align:center; font-size:1.6em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Game & Tool Installation</div>
+
== Game Installation and Modding Setup ==
+
 
+
{{Notice|text={{fc|#ddd|'''Start Out Clean!'''}}
+
 
+
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.<br>
+
{{fc|#ddd|'''PLEASE READ EACH SECTION BELOW CAREFULLY'''}}, as no information included in this Guide is irrelevant!}}
+
<br/>
+
Before continuing with this Guide, users who have not completed the [[Guide:SystemSetupGuide|System Setup Guide]] should stop and do so now. Before continuing, users should already have the game installed and folder structure set up for modding. Our game guides are written with the expectation of the linked setup process already being completed. Users deviating from our recommendations will need to adjust the instructions in our guides accordingly.
+
 
+
== Mod Organizer 2 ==
+
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 ...
+
# '''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.
+
# '''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. STEP recommends “standalone” mode 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 [[Guide:SystemSetupGuide|System Setup Guide]].
+
 
+
<br/>
+
{{Notice|text=For more information about MO2 installation options, please see the [[Guide:Mod_Organizer| Mod Organizer Guide]].}}
+
 
+
== Tools Installation and Setup ==
+
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 ===
+
Users should install the tools to the location created while following the [[Guide:SystemSetupGuide|System Setup Guide]] (i.e., ..\''Modding''\''Tools''\). Install the following tools to that location:
+
 
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-A]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
 
+
The ''Modding'' folder structure should now reflect:
+
 
+
* ..\Modding\Steam (optional; may be installed elsewhere)
+
* ..\Modding\Tools
+
** ..\Tools\BethINI Standalone
+
** ..\Tools\DynDOLOD SE
+
** ..\Tools\LOOT
+
** ..\Tools\Mod Organizer 2
+
** ..\Tools\Wrye Bash
+
** ..\Tools\xEdit
+
** ..\Tools\xLODGen
+
<br/>
+
 
+
= STEP 2 =
+
<div style="color:#ccc; text-align:center; font-size:1.6em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Tool Configuration</div>
+
== Mod Organizer 2 - Configuration ==
+
=== Initialization ===
+
STEP recommends using all applications, including Mod Organizer 2, as standalone programs. The below instructions for MO2's first run reflect this. If MO2 is ran in Portable mode, users will need to adjust the instructions as appropriate. To initialize Mod Organizer 2:
+
 
+
{{Spoiler|shown=Initialization Instructions|hidden=<br/>
+
# Launch MO2 by running its executable (i.e. ..Modding\Tools\Mod Organizer 2\ModOrganizer.exe)
+
# Upon launch, users will have a choose between setting it up as portable or create a new Instance. Choose to create a new Instance.
+
# Select '''SkyrimSE''' and choose '''OK'''.
+
#* A prompt will appear informing you about the option of changing the location of data stored. Read it and click past it.
+
# The installer should automatically detect the Skyrim SE installation (ie. ..Steam\steamapps\common\Skyrim Special Edition). Select it.
+
#* If it didn't find the location, browse to to the Skyrim SE installation path.
+
# 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.
+
# The last prompt will ask if MO can handle .NXM links from the browser. Allow it to do so.
+
# MO2 is now set up and ready to use.}}
+
 
+
=== Profile Setup ===
+
Now users will take advantage of Mod Organizer's profile feature by creating/editing two profiles for use during this Guide:
+
 
+
{{Spoiler|shown=Profile Setup Instructions|hidden=<br/>
+
# Launch MO2, choosing the '''Skyrim SE''' Instance.
+
# On the ''default'' profile, arrange the mods in the left pane in the following order:
+
## DLC: Dawnguard
+
## DLC: HearthFires
+
## DLC: Dragonborn
+
# Click the Configure Profiles button on the menu bar.
+
# Select the “'''Default'''” profile and click “'''Rename'''”.
+
# Rename this profile to ''Vanilla Skyrim'' or something similar
+
# Ensure the '''Use profile-specific Game INI Files''' box is checked and select '''OK'''.
+
#* Users can also check the '''Use profile-specific Save Games''', if they wish.
+
# Ensure the renamed profile is still selected and click '''Copy'''.
+
# Name the new profile  "''STEP SE Core v0.1.0''",  or anything similar.
+
# Check the same boxes from step 6, above.
+
# Close the window by clicking '''Close'''.
+
# Ensure that the ''STEP SE Core'' profile is the currently selected profile in the '''Profile''' drop-down menu.}}
+
 
+
=== Tool Setup ===
+
The final step of setting up Mod Organizer 2 is to add all the tools to it, which were install in the previous step. Some tools will have been auto-detected and added for the user, however, ensure the settings below are set for all tools, even the auto-detected ones. Use the instructions below to add the tools to MO2. xEdit is used for the example:
+
 
+
{{Spoiler|shown=Tool Setup Instructions|hidden=<br/>
+
# Click the '''Executables''' button at the top of the main Mod Organizer window.
+
# In the '''Title''' field type ''SSEEdit'' or ''xEdit''.
+
# In the '''Binary''' field either type the path to the ''SSEEdit.exe'' file or browse for it by selecting the '''...''' button (i.e. ..Modding\Tools\xEdit\SSEEdit.exe)
+
# {{fc|#ddd|(optional)}} The following arguments can be helpful. Input them in the '''Argument''' field separated by a single space:
+
#* ''-IKnowWhatImDoing'' : This turns off a warning present using users make edits.
+
#* ''-AllowMasterFilesEdit'' : By default xEdit will not allow master file editing. This allows users to these files.
+
#* ''-o:"Path\to output\folder"'' : This is the output path xEdit will use when it saves certain files. (i.e. ..Modding\Tools\xEdit\xEdit_Output)
+
# Check the '''Use Application’s Icon for shortcuts''' box.
+
# Click the '''Apply''' button.
+
# Repeat steps 2 through 6 for adding the executables from the table below; filling in the appropriate data. The titles we use are suggestions:}}
+
<br/>
+
'''Tool Setup Table'''
+
{| class="sitetable" style="width:50%; float:left;"
+
! Executable
+
! Title
+
! Argument(s)
+
|-
+
! style="color:#ccc; text-align:left;"| DynDOLOD64.exe
+
| style="text-align:left;"| DynDOLOD SE
+
| style="text-align:left;"| ''-SSE''
+
|-
+
! style="color:#ccc; text-align:left;"| LOOT.exe
+
| style="text-align:left;"| LOOT
+
| style="text-align:left;"| ''--game="Skyrim Special Edition"''
+
|-
+
! style="color:#ccc; text-align:left;"| SSEEditQuickAutoClean.exe
+
| style="text-align:left;"| xEdit Quick Auto Clean
+
| style="text-align:left;"| &nbsp;
+
|-
+
! style="color:#ccc; text-align:left;"| TexGen64.exe (installed with DynDOLOD)
+
| style="text-align:left;"| TexGen SE
+
| style="text-align:left;"| ''-SSE''
+
|-
+
! style="color:#ccc; text-align:left;"| WryeBash.exe
+
| style="text-align:left;"| Wrye Bash
+
| style="text-align:left;"| ''-o “path to Skyrim Special Edition folder”''<br>(i.e, ''-o "D:\Steam\steamapps\common\Skyrim Special Edition"'' )
+
|-
+
! style="color:#ccc; text-align:left;"| xLODGen64.exe
+
| style="text-align:left;"| xLODGen
+
| style="text-align:left;"| ''-lodgen -sse''
+
|}
+
{{clear|left}}
+
 
+
Users can arrange their tools in any order they wish using the up and down buttons above the list. When complete, close the window by clicking the '''Cancel''' button.
+
 
+
== BethINI Setup ==
+
BethINI needs to be set up to run for the current profile in MO2 and ran to establish solid INIs before beginning the mod installations. To do this:
+
 
+
{{Spoiler|shown=BethINI Initialization|hidden=<br/>
+
# Close MO2 and run BethINI.
+
# Select ''Skyrim Special Edition'' from the game selection box.
+
# Allow BethINI to handle custom INIs, if prompted.
+
# Go to the '''Setup''' tab
+
#* Ensure the Game Path is correct (i.e., ..\Modding\Steam\steamapps\common\Skyrim Special Edition).
+
#* Ensure the Mod Organizer path is correct (i.e., ..\Modding\Tools\Mod Organizer 2).
+
#* If the MO path is correct, the '''INI Path''' menu will find the user’s profiles in MO2. Select the profile created earlier in the Guide (''STEP SE Core v0.1.0'').
+
#** 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 (i.e. C:\Users\UserName\AppData\Local\ModOrganizer\SkyrimSE\profiles)}}
+
 
+
 
+
At this time BethINI should restart to grab the correct INIs. Once it is restarted:
+
 
+
{{Spoiler|shown=BethINI Initial Setup|hidden=<br/>
+
# Return to the '''Setup''' tab.
+
#* BethINI will be used for multiple games from a single installation, thus users should check the “'''Always Select Game'''” box.
+
#* To prevent changes to the INIs, check the “'''Make INIs Read-Only'''” box.
+
# Select the '''Basic''' tab.
+
#* Ensure the '''Window Resolution''' matches the system resolution.
+
#* Click the '''Medium''' profile button (this can be changed at the end of the Guide).
+
#* Check the box for “'''Recommended Tweaks'''”.
+
# Now 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 ran again to complete the INI setup.
+
<br/>
+
<br/>
+
 
+
= STEP 3 =
+
<div style="color:#ccc; text-align:center; font-size:1.6em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Cleanup and Considerations</div>
+
== LOOT ==
+
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. To sort with LOOT:
+
# Launch LOOT via Mod Organizer 2 from the executables drop-down menu.<br/>{{Notice Small|text= If LOOT fails to start, try adding the following argument to it: ''--single-process''}}
+
# Click the “'''Sort'''” button at the top of the LOOT window.
+
# Examine the resulting order carefully and look for any alerts or warnings and address each (clean any mods it says has ITMs or UDRs)
+
# Click the “'''Apply'''” button, which has replaced the Sort button at the top.
+
# Close LOOT.
+
 
+
LOOT must be run any time a mod is installed that adds one or more plugins to the load order.
+
 
+
 
+
Up to this point, users should only have the following plugins, in the order listed:
+
# Skyrim.esm
+
# Update.esm
+
# Dawnguard.esm
+
# HearthFires.esm
+
# Dragonborn.esm
+
 
+
If the plugins are not in the order listed, run LOOT now.
+
 
+
== Cleaning Vanilla Master Files ==
+
To remove errors in the Bethesda master files, it is recommended they be cleaned with xEdit before modding begins. This ensures maximum stability and compatibility within the modding experience.
+
=== Standard Cleaning Procedures ===
+
 
+
{{Spoiler|shown=Toggle cleaning procedures|hidden=<br/>
+
# Run xEdit64 Quick Auto Clean from the drop-down executable list in MO2.
+
# On the plugin selection window, double-click on the mod being cleaned (i.e., Update.esm, Dawnguard.esm, etc).
+
# xEdit will now automatically clean the "Identical to master" and "deleted" records from the selected mod.
+
# Once xEdit is done cleaning, click the '''X''' in upper right of the program window to close the program.
+
<!--# At the prompt, check the box next to the mod that was cleaned and the Backup Plugins box. Click '''OK''' to close the tool.-->
+
 
+
After the vanilla master files are cleaned, users should create separate mods for them in MO2 and restore the original files. This prevents users from having to re-clean the file after verifying their files in Steam. To do this, complete the following:
+
# Right-click in the modlist. Hover over '''All Mods''' and select '''Create empty mod''', name it “''MasterName.esm - Cleaned''” (i.e., Update.esm - Cleaned), and click '''OK'''.
+
# On the new mod listing that appears, right-click and select '''Open in explorer'''. Leave this folder opened.
+
# In a new window, open the Skyrim Special Edition Data directory (i.e., ''..\Modding\Steam\steamapps\common\Skyrim Special Edition\Data'')
+
# Drag and drop the cleaned master file from Data to the "''MasterName.esm - Cleaned''" folder from step 2.
+
# Open the TES5Edit Backups folder found in Overwrite in MO2 (bottom of modlist) and rename the file to “''MasterName.esm''”.
+
# Drag and drop the renamed file from the TES5Edit Backups folder to the '''''Data''''' directory and choose to overwrite it, if asked.
+
# Close the explorer windows.
+
# Drag and drop the new ''MasterName.esm - Cleaned'' mod listing in MO2 directly below its vanilla master mod listing.}}
+
 
+
==== Update.esm, Hearthfires.esm, Dragonborn.esm ====
+
Follow the standard cleaning procedures to clean these master files, one at a time. Place the “''MasterName.esm - Cleaned''” mod listing for each below its vanilla master listing. ''Update.esm'' will not be listed in MO2 and ''Update.esm - Cleaned'' is placed at the top of the modlist.
+
 
+
==== Dawnguard.esm ====
+
Follow the standard cleaning procedures to clean ''Dawnguard.esm''.
+
 
+
Once the automatic cleaning is complete, Dawnguard also has some manual cleaning required. To do this,
+
 
+
{{Spoiler|shown=Toggle Dawnguard manual cleaning procedures|hidden=<br/>
+
# Run xEdit from MO.
+
# At the prompt, double-click on Dawnguard.esm.
+
# Once loaded, type in ''00016BCF'' in the FormID field (above the mod list) and hit '''Enter/Return'''.
+
# In the right pane, find the '''XEZN - Encounter Zone record'''.
+
# 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.
+
# In the FormID field again, type in ''0001FA4C'' and hit '''Enter/Return'''.
+
# On the Dawnguard.esm column, right-lick on the '''Dawnguard.esm''' header and select '''Remove'''.
+
# In the FormID field again, type in ''0006C3B6'' and hit '''Enter/Return'''.
+
# On the Dawnguard.esm column, right-lick on the '''Dawnguard.esm''' header and select '''Remove'''.
+
# Now close xEdit, ensuring Dawnguard.esm is checked on the prompt.}}
+
 
+
After the manual cleaning is complete, create the mod listing as directed above and place the “''Dawnguard.esm - Cleaned''” mod listing directly below ''Dawnguard.esm''.
+
 
+
 
+
{{Notice|text= Any time Bethesda updates these master files, users should complete this cleaning process again. This ensures users have any fixes Bethesda may have included within their updates.}}
+
 
+
 
+
At this point, the Bethesda masters should be cleaned and the mod list order should reflect:
+
# Updated - Cleaned .esm
+
# DLC: Dawnguard.esm
+
# Dawnguard - Cleaned.esm
+
# DLC: HearthFires.esm
+
# HearthFires - Cleaned.esm
+
# DLC: Dragonborn.esm
+
# Dragonborn - Cleaned.esm
+
 
+
== Understanding the STEP Patches ==
+
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. The STEP Patches are CR patches and more.
+
 
+
The STEP Patches are CR Patches built specifically for the mod list within this Guide. They are required to run the Guide without issues; providing conflict resolution between various mods. Additionally, the patches provide both mod integration and custom edits surrounding the use of specific mods. This means the patches are one part CR patch and one part mod.
+
 
+
Users should decide now, before installing any mods, whether or not they will be using the STEP Patches or creating their own. This decision will be referenced during mod installations below. Users who decide to install the STEP Patches will do so after the mod installations.
+
 
+
<br/>
+
{{Notice|text=Users installing only the Core mod list or only installing mods on top of this Core mod list, are '''recommended to use the STEP Patches'''! These patches will solve all conflicts for users installing only the Core mod list. For users adding a few additional mods on top of STEP Core, the Patches can be used as a foundation to build upon. This ensures a stable game.}}
+
<br/>
+
 
+
{{fc|#ddd|'''''We do not offer support for unpatched mod installations!'''''}}
+
 
+
[[STEP Patches Requirements]] - We recommend keeping the forum topic from the link open for referencing the list of required mods. This is helpful for users deciding whether or not to install a mod that may be required by the Patches.
+
 
+
Finally, we offer the following options in regards to Patches:
+
* '''STEP SE Core - Conflict Resolution Patch'''
+
** patches the entire STEP SE Core mod list besides the ''Lighting & Weather'' mod group.
+
* '''STEP SE Core - Lighting & Weather Patch'''
+
** patches the mods listed within the ''Lighting & Weather'' mod group with the rest of the STEP SE Core mod list.
+
** this is provided as a separate patch for users wanting to customize their own lighting and weather setup.
+
<br/>
+
 
+
= STEP 4 =
+
<div style="color:#ccc; text-align:center; font-size:1.6em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">STEP SE Core Modlist</div>
+
At this point users should have their systems fully set up and ready to install mods from the modlist below. Users who are unaware of how to complete mod installations using Mod Organizer 2 should return to that Guide and refresh their knowledge. When installing mods from the list below, keep the following in mind:
+
* Mods should be installed ''in the order that they are listed'' to ensure other mods further down the list overwrite those occurring before them. This is necessary to ensure the desired in-game effect.
+
* Mods are listed in alphabetical order within each section and any deviations from this ''are purposeful'' to achieve the desired outcome.
+
* Always install plugins (ESLs/ESMs/ESPs) unless otherwise noted.
+
* If there are no notes associated with a particular mod, then all options fit the our mandate and it's the user's decision which option to install. Mod notes only provide instructions where necessary; otherwise, STEP encourages user customization.
+
* Unless otherwise stated, follow LOOT's advice in regards to mod cleaning and sorting.
+
<br/>
+
{{Notice|text=STEP does not recommend extracting BSAs for this Guide. Each BSA has been manually checked by the staff to ensure the proper overwrites are maintained, without the need for extraction.}}
+
<br/>
+
 
+
== Mod Table Reference ==
+
Below is the legend and reference for the mod tables used in this Guide. Users should refer back to it when confused about a mod listing.
+
{| class="steptable" |
+
! class="first" |
+
! '''Mod Name'''
+
! '''Baseline'''
+
! '''Quality Options'''
+
! '''DLC Required'''
+
! '''Notes'''
+
|-
+
! class="core" |
+
| style="width: 20%" | [[Main Page|Mod Name]]<sup>[[File:Wikilink.png|20px]]</sup>
+
| style="width: 10%; text-align:center;" | Baseline
+
| style="width:72px; padding:4px 6px 0px;" | <span style="float:left;">[[File:LowQuality.png|32px]]</span> <span style="float:right;">[[File:HighQuality.png|32px]]</span>
+
| class="dlc" style="width: 8%; text-align:center;" | {{Indicator|32|18|#739472|#4F5C4F|#A8C9A7|Dawnguard}}
+
| Notes
+
|}
+
<br/>
+
 
+
=== Legend ===
+
{| valign="left" style="width: 70%; background-color: transparent; margin-left: 50px;"
+
! style="width: 0.5%; background-color:#6B7E40; border-bottom: 1px solid #666C71; border-top: 1px solid #666C71; padding: 0;" |
+
| style="width: 9%; border-bottom: 1px solid #666C71; border-top: 1px solid #666C71;" | '''STEP Patch'''
+
| style="border-bottom: 1px solid #666C71; border-top: 1px solid #666C71;" | Mods included in the STEP Patches are indicated by the presence of a green vertical bar in the row at the immediate left-hand column of the table before the mod name.
+
|-
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" | '''Mod Name'''
+
| style="border-bottom: 1px solid #666C71;" | Shortened version (where applicable) of Nexus mod name presented as a link to Nexus for download.
+
|-
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" | [[File:Wikilink.png]]
+
| style="border-bottom: 1px solid #666C71;" | Link to the mod's wiki page, which includes various information about the mod.
+
|-
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" | '''Baseline'''
+
| style="border-bottom: 1px solid #666C71;" | This notes the STEP Baseline version or option of the corresponding mod that should be installed, and usually refers to options affecting performance/quality.<br>General suggestions are located in the "''Notes''" column; see below.
+
|-
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" | '''Quality Options'''
+
| style="border-bottom: 1px solid #666C71;" | Indicates if there are lower or higher quality options for the mod ''relative to the Baseline recommendation'':
+
|-
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" | &nbsp;[[File:LowQuality.png|18px]] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'''''Relative to Baseline''''', a lower quality, less demanding version of the mod is also available.
+
|-
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[File:HighQuality.png|18px]] &nbsp;'''''Relative to Baseline''''', a higher quality, more demanding version of the mod is also available.
+
|-
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" | &nbsp;[[File:LowQuality.png|18px]] [[File:HighQuality.png|18px]] &nbsp;'''''Relative to Baseline''''', both lower and higher quality versions of the mod are available.
+
|-
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" | '''DLC Required'''
+
| style="border-bottom: 1px solid #666C71;" | Any DLCs listed here are ''required'' for the mod to function.  Do not install the mod, unless all DLCs listed are present.<br>{{fc|#ddd|During mod installation instructions, STEP assumes a Legendary version of the game is being used (all DLC are installed).}}
+
|-
+
| style="border-bottom: 1px solid #666C71;" |
+
| style="border-bottom: 1px solid #666C71;" | '''Notes'''
+
| style="border-bottom: 1px solid #666C71;" | Brief notes that apply to the mod or installation.<br>In some cases, mods with several options will include a suggested option. These ''suggestions'' will take the form of: {{fc|#ddd|"STEP recommends <nowiki>'</nowiki>''Option A''<nowiki>'</nowiki>."}}<br>In other cases, there may only be one appropriate option, which fits the STEP Mandate. These ''instructions'' will take the form of: {{fc|#ddd|"Use <nowiki>'</nowiki>''Option A''<nowiki>'</nowiki>."}}<br>Users will also see links displayed as: {{fc|#ddd|Detailed instructions available}}. Users should follow these links to find detailed instructions for installing the mod.
+
|}
+
 
+
== {{#show:Category:ModSection_SE-B|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-B|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-B]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-C|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-C|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-C]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-D|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-D|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-D]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-E|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-E|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-E]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-F|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-F|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-F]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
|limit=110
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-G|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-G|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-G]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-H|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-H|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-H]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-I|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-I|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-I]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-J|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-J|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-J]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-K|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-K|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-K]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-L|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-L|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-L]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-M|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-M|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-M]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-N|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-N|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-N]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-O|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-O|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-O]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-P|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-P|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-P]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-Q|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-Q|?SectionDescription}} }}
+
 
+
{{Notice Small|text={{fc|#ddd|'''''This section is optional!'''''}}<br/><br/>We wish to be clear that the mods included within this section are completely optional. They are still within the [[STEP:Mandate|Mandate]], however, we've made this section optional for users who wish to customize their own lighting and weather for their games. As such, we've included an additional patch solely for this mod group.}}
+
 
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-Q]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
 
+
== {{#show:Category:ModSection_SE-R|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-R|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-R]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
 
+
Once FNIS SE is installed, the animation files need to be generated for the skeleton changes.
+
# Sort the load order with LOOT.
+
# Run ''FNIS SE'' via Mod Organizer 2.
+
# In the ''Available Patches'' at the bottom of the window, check the box adjacent to '''"SKELETON Arm Fix"'''.
+
# Click the {{ui|Update FNIS Behavior}} button and wait for a message to appear in the window stating "''X animations for Y mods successfully included''".
+
# Click {{ui|Exit}}.
+
 
+
After closing FNIS SE, there will be files in ''Overwrite'' (essentially a fake mod located at the bottom of the left pane if sorted by priority ascending):
+
# Right-click '''Overwrite''' and select '''Create Mod'''
+
# Name it ''FNIS SE Output'' and click '''OK'''.
+
#* This will create a new mod listing in the left pane for the FNIS SE generated files.
+
# Check the new mod entry to enable it.
+
 
+
== {{#show:Category:ModSection_SE-S|?SectionLabel}} ==
+
:{{fc|#E6B69E|{{#show:Category:ModSection_SE-S|?SectionDescription}} }}
+
{{ModTable|ModTableRow=
+
{{#ask:[[Version::{{PAGENAME}}]][[Section::SE-S]]
+
|mainlabel=-
+
|format=template
+
|template=ModTable/Row
+
|named args=yes
+
|link=none
+
|?ModName
+
|?Section
+
|sort=OrderID
+
}}
+
}}
+
<br/>
+
<br/>
+
 
+
= STEP 5 =
+
<div style="color:#ccc; text-align:center; font-size:1.6em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Patches and LODs</div>
+
 
+
== Sorting with LOOT ==
+
Users should now run LOOT and accept the default mod order it provides.
+
 
+
The new Patches are designed to work with a default LOOT sorting of the mods. This means there are no more meta rules to set with the STEP Guides. This reduces user tasks (preventing one less area for user error) and streamlines the Guide's installation. Users should:
+
* sort their load order using LOOT any time they install, uninstall or update a mod.
+
* update LOOT any time it says their is an update available.
+
 
+
== Creating a Bashed Patch ==
+
A Bashed Patch is a patch created by running Wrye Bash (WB). This process imports several record types from a load order, to ensure those records are carried forward.
+
 
+
{{Notice|text={{fc|#ddd|'''This Guide no longer uses a Bashed Patch!'''}}
+
 
+
All necessary edits, which the Bashed Patch covered in previous versions of the STEP Guide are now contained with the STEP Patches.}}
+
 
+
 
+
Though this Guide doesn't require a Bashed Patch, users may eventually install mods that require one. Users should only require a Bashed Patch if they include additional mods that add or alter leveled lists. Even then, one may not always be required. STEP provides the instructions below to create a Bashed Patch. If users need to create one, they are highly encouraged to review the results in xEdit! Investing has shown many of the leveled lists forwards to be completely unnecessary as they were just copies of the winning mod's records.
+
 
+
=== Building a Bashed Patch ===
+
Keep in mind these procedures are only for using a Bashed Patch to manage leveled lists.
+
 
+
{{Spoiler|shown=Steps to build Bashed Patch for STEP|hidden=<br/>
+
# Users who did not run LOOT, do it now!
+
# Ensure the '''Overwrite''' mod is empty in MO2.
+
# Run '''Wrye Bash''' from the MO2 executable list.
+
#* If it doesn't detect the game, select Skyrim SE.
+
# Once loaded, scroll to the mod of the mod list and right-click on '''Bashed Patch, 0.esp'''
+
# Select '''Rebuild Patch'''.
+
# '''''Untick''''' all boxes besides '''Leveled Lists'''.
+
# Click the '''Build Patch''' button.
+
# Activate the patch when asked and close Wrye Bash.
+
# Right-click on the ''Overwrite'' mod in MO2 and select '''Create new mod'''.
+
# Name the new patch something unique for the current MO2 profile (i.e. ''STEP SE Core - Bashed Patch'')}}
+
 
+
== DynDOLOD ==
+
Users will now create LODs using Dynamic Distant Objects LOD (DynDOLOD). DynDOLOD is one part mod and one part tool. Users should already have the tool installed from the beginning of the Guide. Now it's time to install the mod portion:
+
 
+
{{Spoiler|shown=Install DynDOLOD Resources SE|hidden=<br/>
+
# Visit the Skyrim SE DynDOLOD [https://forum.step-project.com/topic/13894-dyndolod-beta-for-skyrim-special-edition-and-skyrim-vr-274/ forum topic].
+
# Download the '''DynDOLOD Resources SE vX.XX''' file.
+
# Install the file using MO2 by selecting the following options:
+
#* Solidtude Exterior
+
#* Whiterun Exterior
+
#* 3D Plume
+
#* High Hrogthar Window Glow
+
#* Desync Birds of Prey}}
+
 
+
 
+
Before moving on, users need to create two empty mods to use for the files DynDOLOD outputs:
+
 
+
{{Spoiler|shown=Create empty mods|hidden=<br/>
+
# Right-click on the mod list in MO2 and hover over '''All Mods'''.
+
# Select, '''Create empty mod'''.
+
# Name it ''STEP SE Core - TexGen Output'' or anything similar.
+
# Place this new mod directly after '''DynDOLOD Resources SE'''.
+
# Repeat these steps to create another new mod call ''STEP SE Core - DynDOLOD Output'', or anything similar.
+
# Place this other new mod directly after the new mod from step 3 (i.e.,  STEP SE Core - TexGen Output)..}}
+
 
+
 
+
The last few mods in the mod list should now reflect:
+
# ..
+
# STEP SE Core - CR Patch
+
# STEP SE Core - LW Patch (optional)
+
# DynDOLOD SE Resources
+
# STEP SE Core - TexGen Output
+
# STEP SE Core - DynDOLOD Output
+
 
+
=== Run TexGen ===
+
TexGen, shipped with DynDOLOD, is a program that will create custom LOD textures for objects based on the full-size texture installed. This means distance object textures will better match their fully rendered counterparts. To create custom LODs:
+
 
+
{{Spoiler|shown=Instructions for TexGen|hidden=<br/>
+
# Run TexGen from the MO2 executable drop-down list.
+
# Keep the default Output location and and choose one of the follow two options:
+
## '''Option 1:''' Keep the default settings. This is for the average system.
+
## '''Option 2:''' Users who have the a bit more performance room, change the ''LOD Texture Size'' to '''512'''. This will result in higher resolution LOD textures.
+
# Once the option has been chosen click '''Start'''.
+
# Once the completed message has appeared, click '''Save & Exit'''.
+
# Navigate to the ''DynDOLOD'' folder location (i.e., ..\Modding\Tools\DynDOLOD).
+
# Copy or cut the files from the ''TexGen_Output'' folder.
+
# In MO2, hold down the '''Ctrl''' key and double-click on the ''TexGen Output'' mod created above. This opens the mod's folder in an Explorer window.
+
# Paste the files into the mod's folder and close the window.
+
# In MO2, ensure the ''TexGen Output'' mod is active (checked).}}
+
 
+
=== Run DynDOLOD ===
+
DynDOLOD will now be run to generate the remainder of the LODs for the game. Users have the options of generating higher quality 3D Trees or generating the standard tree LOD. Following one of the two sets of instructions below, depending on the option desired.
+
 
+
==== Standard Tree LOD ====
+
{{Spoiler|shown=Instructions for Standard Trees|hidden=<br/>
+
# Run DynDOLOD from the MO2 executable drop-down list.
+
# Click the '''Advanced''' button once the main tool window is displayed.
+
# Select all worldspaces.
+
# Ensure the '''Candles''', '''FXGlow''', and '''Windows''' boxes are checked.
+
# Keep the default Output location and settings and click '''Medium'''.
+
# Users with systems able to handle '''High''' settings, may do so.
+
# Once the completed message has appeared, click '''Save & Exit'''.
+
# Navigate to the ''DynDOLOD'' folder location (i.e., ..\Modding\Tools\DynDOLOD).
+
# Copy or cut the files from the ''DynDOLOD_Output'' folder.
+
# In MO2, hold down the '''Ctrl''' key and double-click on the ''DynDOLOD Output'' mod created above.
+
# Paste the files into the mod's folder and close the window.
+
# In MO2, ensure the ''DynDOLOD Output'' mod is active (checked).
+
# Sort with LOOT.
+
# Ensure DynDOLOD.esp is the last plugin in the load order.}}
+
 
+
==== 3D Tree LOD ====
+
There are two options for 3D Trees. Full or Hybrid.
+
# Full 3D Trees will generate the entire tree (branches and trunks) in 3D.
+
# Hybrid 3D Trees is more performance friendly. It will generate 3D branches with 2D trunks.<br/>
+
 
+
{{Spoiler|shown=Instructions for 3D Trees|hidden=<br/>
+
# Open the root ''DynDOLOD'' folder (i.e., ..\Modding\Tools\DynDOLOD\).
+
# Open the ''DynDOLOD_SSE.ini'' file (i.e., ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini)
+
# Set ''TreeLOD=0''
+
#* If generating Hybrid 3D Trees, skip to the next step now.
+
#* If generating Full 3D Trees, also set ''TreeFullFallBack=0''.
+
# Run '''DynDOLOD''' from the MO2 executable drop-down list.
+
# Select all worldspaces.
+
# Ensure the '''Candles''', '''FXGlow''', '''Generate static LOD''', '''Window'''s, and '''High''' boxes are checked.
+
# Keep the default Output location and settings, click '''High''' preset button, and run it.
+
#* The '''High''' preset is require for 3D Trees!
+
# Get a cup of coffee. This takes ~40 minutes on SSDs.
+
# Once the completed message has appeared, click '''Save & Exit'''.
+
# Navigate to the ''DynDOLOD'' folder location (i.e., ..\Modding\Tools\DynDOLOD).
+
# Copy or cut the files from the ''DynDOLOD_Output'' folder.
+
# In MO2, hold down the Ctrl key and double-click on the ''DynDOLOD Output'' mod created above.
+
# Paste the files into the mod's folder and close the window.
+
# In MO2, ensure the DynDOLOD Output mod is active (checked).
+
# Sort with LOOT.
+
# Ensure DynDOLOD.esp is the last plugin in the load order.}}
+
 
+
{{Notice Small|text=One issue that can arise when generating LOD with DynDOLOD is having a "bad run", though it doesn't happen often. However, when it does happen CTDs are usually the result. If this happens, for example while fast traveling, try disabling the generated output and recreate the conditions in-game. If the CTDs are resolved, trash all of the files from the bad run and complete the process again.}}
+
 
+
=== When do users need to rebuild LODs? ===
+
Users should rebuild their LODs any time they update their mod lists with mods that adds, removes, or relocates exterior objects such as buildings, roads, trees, etc. Users should also rebuild any time an update to DynDOLOD SE Beta is released.
+
 
+
<br/>
+
 
+
= STEP 6 =
+
<div style="color:#ccc; text-align:center; font-size:1.6em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Mod Configuration & Wrap-up</div>
+
Users should now be ready to load the game for the final steps, configuring mods in the Mod Configuration Menu (MCM). The MCM is a feature of SkyUI that allows mod authors to provide custom settings for their mods, which users can set within the game. Well provide recommendations for users below for all the mods installed within this Guide.
+
 
+
{{Notice Small|text=When launching the game for the first time after a STEP Guide is installed, the load could take significantly longer than normal. This will only be a one-time load wait as all the installed mods are being initialized. Subsequent load times should be shorter.<br/><br/>
+
 
+
When ready to play the game after a new STEP Guide install, it is recommended to start a new character.}}
+
 
+
== Mod Configuration Menu Settings ==
+
=== Farmhouse Chimneys SE ===
+
Vanilla villages should all be checked on the first page. The following screenshot displays the recommended settings for the Mod Support page:
+
 
+
{{GallerySimple|id=FarmhouseChimneysMCM|width=250|img=https://i.postimg.cc/63x47Hs2/Farmhouse-Chimneys-SE.png|caption=Mod Support}}
+
{{clear}}
+
 
+
=== Remaining Mod Configurations ===
+
The remaining mod configurations are recommended to be left at their defaults for the most enhanced, vanilla experience. However, users may adjust the settings for these mods to their liking.
+
 
+
== Optional BethINI Customization ==
+
Users are now ready to play their enhanced Skyrim SE, however, please consider reading the remainder of the Guide before taking an arrow to the knee.
+
 
+
The final consideration is customizing BethINI once the game is confirmed to be stable. Users who have no issues with performance, however, aren't knowledgeable with the settings can simply choose a higher preset. Other users can feel to customize the settings to their personal preferences. Caution is advised against using the custom INI input feature. This feature will allow users to make custom INI edits, however, doing so without the knowledge of exactly what the customizations are doing can cause instability.
+
 
+
The following are provided as examples of the settings used for taking the screenshot's on Nexus (1920x1080 using a GTX 1060 6GB card). The recommended settings are called out and/or shown in the screenshots below. All settings can be customized per user preference. Simply click on a section heading to expand it.
+
 
+
{| style="border: 1px solid #000; width:90%; float:left;"
+
|-
+
| style="border-right: 1px solid #000; width:25%; text-align:left;"| {{Spoiler|shown=<h3>Basic</h3>|hidden=&nbsp;{{fc|#ddd|'''STEP Recommends:'''}}
+
* Antialiasing: TAA
+
* Windowed Mode
+
* Borderless
+
* Vsync
+
* Lock Frame Rate
+
* FPS: 60
+
* Recommended Tweaks
+
* BethINI Presets
+
** Users should select a preset. High was chosen for the screenshots.}}
+
{{GallerySimple|id=BethINICustom|width=250|img=https://i.postimg.cc/sX881jCJ/Beth-INIBasic.png|caption=Basic Tab}}
+
{{clear}}
+
| style="border-right: 1px solid #000; vertical-align: text-top; width:25%; text-align:left;"| {{Spoiler|shown=<h3>General</h3>|hidden=&nbsp;{{fc|#ddd|'''STEP Recommends:'''}}
+
Users should match the screenshot.}}
+
{{GallerySimple|id=BethINICustom|width=250|img=https://i.postimg.cc/DfJHHX1p/Beth-INIGeneral.png|caption=General Tab}}
+
{{clear}}
+
| style="border-right: 1px solid #000; vertical-align: text-top; width:25%; text-align:left;"| {{Spoiler|shown=<h3>Gameplay</h3>|hidden=&nbsp;{{fc|#ddd|'''STEP Recommends:'''}}
+
* Over-Encumbered Reminder: 300 (5 mins) or 3600 (1 hour)
+
Optionally, users can check ''NPC Use Ammo'' or a more realistic experience. This will cause NPCs to only use the ammo available in their inventories.}}
+
{{GallerySimple|id=BethINICustom|width=250|img=https://i.postimg.cc/y6MtH8P1/Beth-INIGameplay.png|caption=Gameplay Tab}}
+
{{clear}}
+
| style="width:25%; vertical-align: text-top; text-align:left;"| {{Spoiler|shown=<h3>Interface</h3>|hidden=&nbsp;{{fc|#ddd|'''STEP Recommends:'''}}
+
* Fix Map Menu Navigation
+
* Remove Map Menu Blur}}
+
{{GallerySimple|id=BethINICustom|width=250|img=https://i.postimg.cc/wBpjF5ns/Beth-INIInterface.png|caption=Interface Tab}}
+
{{clear}}
+
|-
+
| style="border-right: 1px solid #000; border-top: 1px solid #000; width:25%; text-align:left;"| {{Spoiler|shown=<h3>Detail</h3>|hidden=&nbsp;{{fc|#ddd|'''STEP Recommends:'''}}
+
* Water: Select all but Sky
+
** Reflecting the sky can cause LOD seams on the water to be more visible.
+
* Particles: 4500 (this just over doubles vanilla)
+
* Depth of Field
+
* Uncheck ''Lens Flare'' (optional)
+
* Uncheck ''Anamorphic Lens Flare'' (optional, this is the flare seen on candles)
+
This use of ''Sparkles'' is optional as they are a preference feature. However, if using [[Landscapes - Cathedral Concept]], then this mod includes custom edits to the Sparkles and Improved Snow Shader.}}
+
{{GallerySimple|id=BethINICustom|width=250|img=https://i.postimg.cc/MKssGZ0f/Beth-INIDetail.png|caption=Detail Tab}}
+
{{clear}}
+
| style="border-right: 1px solid #000; border-top: 1px solid #000; vertical-align: text-top; width:25%; text-align:left;"| {{Spoiler|shown=<h3>View Distance</h3>|hidden=&nbsp;{{fc|#ddd|'''STEP Recommends:'''}}
+
* Grass Fade: 18000 (max)
+
* Light Fade: 50000 (max)
+
* Flickering Light: 8192
+
The remainder of the Fade values are user preference. They are set fairly high for Tech's system, which allows for longer distance viewing of NPCs for archery and strategy planning. uGridsToLoad should never been changed from vanilla's default of '''5'''. The preset here should match the preset selected on the ''Basic'' tab.}}
+
{{GallerySimple|id=BethINICustom|width=250|img=https://i.postimg.cc/Gmrf4gV6/Beth-INIView-Distance.png|caption=View Distance Tab}}
+
{{clear}}
+
| style="border-right: 1px solid #000; border-top: 1px solid #000; vertical-align: text-top; width:25%; text-align:left;"| {{Spoiler|shown=<h3>Visuals</h3>|hidden=&nbsp;If using [[Landscapes - Cathedral Concept]], these setting should not need to be adjusted. If not, set the values here according to the installation instructions of the grass mod in use.}}
+
{{GallerySimple|id=BethINICustom|width=250|img=https://i.postimg.cc/BQ2yQfYx/Beth-INIVisuals.png|caption=Visuals Tab}}
+
{{clear}}
+
| style="border-top: 1px solid #000; vertical-align: text-top; width:25%; text-align:left;"|{{Spoiler|shown=<h3>Custom</h3>|hidden=&nbsp;Making the following custom adjustment to speed up the book opening animation by twice the speed of vanilla:}}
+
{{GallerySimple|id=BethINICustom|width=250|img=https://i.postimg.cc/2yZtZszN/Beth-INICustom.png|caption=Custom Tab}}
+
{{clear}}
+
|}
+
{{clear|left}}
+
 
+
== ENBSeries with STEP SE Core ==
+
The Core Guide doesn't include an ENB preset for reason that should be obvious, however, we know it can be difficult to find a preset that works with Cathedral Weathers. To make this a bit easier, we've included a small list of ENB presets below which were made to work with Cathedral Weathers, without breaking the horizon. We've included a variety of "looks", but users should search on Nexus to find the preset that works best for their preferences.
+
 
+
* [https://www.nexusmods.com/skyrimspecialedition/mods/25296 A Cathedralist's ENB]
+
* [https://www.nexusmods.com/skyrimspecialedition/mods/29350 Blubbos ENB ReShade]
+
* [https://www.nexusmods.com/skyrimspecialedition/mods/31007 CELESTIAL CATHEDRAL ENB]
+
* [https://www.nexusmods.com/skyrimspecialedition/mods/30716 iiENB]
+
* [https://www.nexusmods.com/skyrimspecialedition/mods/30971 Ljoss]
+
* [https://www.nexusmods.com/skyrimspecialedition/mods/27481 Lucid ENB]
+
* [https://www.nexusmods.com/skyrimspecialedition/mods/23086 PRENB]
+
* [https://www.nexusmods.com/skyrimspecialedition/mods/28245 Ragnar's Vivid ENB for Cathedral Weathers 2]
+
* [https://www.nexusmods.com/skyrimspecialedition/mods/30506 Serio's ENB]
+
<br/>
+
<br/>
+
 
+
= COMMUNITY CONTRIBUTIONS =
+
<div style="color:#ccc; text-align:center; font-size:1.6em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Help build STEP</div>
+
STEP can only get bigger and better with help from the community. It is very time consuming for the STEP team to ensure that the Guide is consistently maintained at the highest quality possible. We need people to help us identify mods that improve the vanilla game while adhering to our [[STEP:Mandate|Mandate]]. We also need ongoing bug reports, reviews, and updates on mods that may cause problems or that stray from the Mandate.
+
 
+
In order to suggest a mod for inclusion, visit the [https://forum.step-project.com/forum/107-skyrim-se-mods/ Mods section of the Forums].
+
 
+
== Call for Mod Testers ==
+
Community members interested in becoming Mod Testers, please [https://forum.step-project.com/user/326-techangel85/ contact TechAngel85 via PM] on the forums. Once registered, Mod Testers will be given access to Staff forums that houses useful information. For more information about our mod testing process, read through the [https://wiki.step-project.com/Guide:Mod_Testing Mod Testing Guide] to get a sense of what's involved.
+
 
+
== Call for Forum Moderators ==
+
Regular community members interested in becoming moderators, please [https://forum.step-project.com/user/326-techangel85/ contact TechAngel85 via PM] on the forums. Forum Moderators will be determined based upon level and quality of activity within our community.
+
 
+
== STEP Builds ==
+
STEP Builds are user-created guides that use one of the STEP Core mod lists as a foundation to their own mod list within their guide. If a STEP Build adheres to our guidelines, it can be considered as a candidate for being hosted on the STEP 3.0 website. An example of a STEP Build will be provided with the release of STEP 3.0 in the form of ''Tech's Skyrim Special Edition Guide''. Be certain to read the STEP Builds documentation when it becomes available.
+
 
+
{{MO Note|This one of the reasons why Mod Organizer is the chosen mod-management utility for STEP. MO2 makes building mod lists for STEP Builds a breeze.}}
+
 
+
 
+
<center>{{fs|2.0em|{{fc|#ddd|Thank you for reading and enjoy the game!}} }}</center>
+
<br />
+
 
+
= Credits =
+
<div style="color:#ccc; text-align:center; font-size:1.6em; font-weight:500; border-style:solid; border-bottom-width:3px; border-color:rgb(200,100,20); padding-bottom:10px; overflow:hidden;">Thank you all!</div>
+
 
+
The STEP administrators would sincerely like to thank (from the bottoms of our fuzzy little hearts):
+
 
+
* The authors of mods recommended within our Guides
+
* The authors of mods who granted permission for their mods to be incorporated into the STEP Patches
+
* The core Community for feedback, suggestions and input
+
* The Beta and Mod Testers for their good humor and rigorous analyses
+
* The Nexus community
+
* Bethesda Softworks for their games
+
* Tannin for the gift that is Mod Organizer
+
* All the developers that kept MO alive to create MO2
+
 
+
== STEP Staff ==
+
=== Administrators ===
+
* {{fc|#FFA500|TechAngel85}}
+
** Lead Release Coordinator, Patch Coordinator, Lead Forum Administrator, Mod Author
+
* {{fc|#FFA500|z929669}}
+
** Project Founder, Lead Site Developer, Lead Site Administrator
+
 
+
=== SM Forum Moderators ===
+
Currently active STEP Forum Moderators:
+
* {{fc|#c5d|DoubleYou}}
+
* {{fc|#c5d|GrantSP}}
+
* {{fc|#c5d|Greg}}
+
* {{fc|#c5d|Kelmych}}
+
 
+
=== Honorary Staff ===
+
Founder, Administrators, and Staff no longer active with the project:
+
* Aiyen
+
* EssArrBee
+
* Farlo
+
* hishutup
+
* MontyMM
+
* Nebulous112
+
* oqhansoloqo
+
* phazer11
+
* rootsrat
+
* stoppingby4now
+
* TheCompiler
+
* torminater
+
* WilliamImm
+
 
+
<!--{{DonorCredits}}-->
+
__NOTITLE__
+
[[Category:Step Guide]]
+
{{#css:STEP:StepGuide.css}}
+

Revision as of 16:53, January 15, 2020