Guide:System Setup Guide: Difference between revisions

From Step Mods | Change The Game
m (Text replacement - "|hidden=<br>" to "|hidden=")
 
(357 intermediate revisions by 6 users not shown)
Line 1: Line 1:
__NOTITLE__[[Category:Official Game Guides]]{{PageTitle|logo=delta|title=System Setup Guide|subtitle=A Mandatory Prerequisite for Step's Bethesda Game Guides|author=The Step Team|forumtid=14917}}{{TOC right|limit=4}}
[[Category:General Modding Guides]][[Category:Official Mod-Build Guides]]{{PageTitle|logo=delta|title=System Setup Guide|subtitle=A Mandatory Prerequisite for Step Mod-Build Guides|author=The Step Team|forumtid=14917}}{{TOC|limit=4}}
{{Fc|important|This guide describes the expected configuration of the PC environment in order to complete ANY Bethesda game guide on this wiki.}} This standard configuration prevents some common modding issues and facilitates support and resolution of many others.  
{{Fc|important|This guide describes the expected configuration of the Windows 10/11  PC environment in order to complete ANY Bethesda mod-build guide on this wiki.}} This standard configuration prevents some common modding issues and facilitates support and resolution of many others.  


A couple of notes before continuing:
== Modding Folders ==
* {{fc|highlight|This guide assumes a Windows 10 environment.}}
Create modding-related folders (aka, directory locations or 'paths'). Before doing so, consider the space requirements. {{Fc|important|A good rule of thumb for drive space requirements is ~100GB per game}}; however, this will vary from game to game. This space accounts for the game (e.g., Skyrim LE requires ~13GB, Fallout 4 requires ~30GB), installed mods, temporary files, modding tools, etc. Also remember that no PC drive should be filled to more than 90% of its capacity.
** Windows 7 is at End-of-Life and Windows 8 is not recommended, therefore, Windows 10 is the only OS supported by Step.
* {{fc|highlight|Step recommends solid state drives (SSD) over hard drives (HDD)}}
** SSDs are much faster than HDDs, therefore, users will have an improved experience using SSDs.


== Modding Folder ==
To avoid potential Windows Security and User Account Control (UAC) pemissions issues, {{Fc|salmon|avoid installing moddable games and modding resources under existing paths created by Windows or third-party programs}}. {{Fc|red|Install locations to avoid}} include but are not limited to...
First, users need to select and set up a directory location for modding. Due to issues with some modding programs and Windows User Account Control (UAC), Step recommends using a location outside of UAC jurisdiction. {{fc|important|Avoid installing games and modding resources within the following directory locations:}}
* <code>{{Fc|red|C:\Program Files\}}</code>
* <code>C:/Windows/</code>
* <code>{{Fc|red|C:\Program Files (x86)\}}</code>
* <code>C:/Program Files/</code>
* <code>{{Fc|red|C:\Users\}}</code>
* <code>C:/Program Files (x86)/</code>
* <code>{{Fc|red|C:\Windows\}}</code>
* <code>C:/Users/{logged in user}/AppData/</code> Note that some modding applications like [[SkyrimSE:BethINI SE|BethINI]] and [[SkyrimSE:Mod Organizer 2|Mod Organizer]] may validly create files under this location.
Specifically, begin by creating a folder called ''Modding'', at the root of any drive: e.g., <code>C:/Modding/</code>. This keeps path depth shallow and path strings brief.


Also consider the space requirements for modding, which can be significant for a single game. For a heavily modded setup, at least 50 GB of free space per game is typical. This accounts for downloaded mods, installed mods, temporary LODGen files, modding tools, etc. Additionally, allow for at least 20 GB of free space for each game (e.g., Skyrim requires 13 GB, and Fallout 4 requires upwards of 30 GB). Also remember that no PC drive should be filled to more than 90% of its capacity.
Instead, create the following folders on any drive root (e.g., <code>C:\</code>, <code>D:\</code>, <code>E:\</code>, etc.) to keep paths shallow. Installing games and modding tools onto a large, fast drive is beneficial:
{{alert small|text=A good rule of thumb for modding drive space requirements is ~100 GB per game.}}
<pre>C:\Modding
=== Folder Structure ===
C:\Modding\Tools
Extend the modding folder structure as follows:
C:\Games</pre>
: <code>..Modding/</code>
In creating these directories, the 'Owner' is the Windows user who created them and who has full permissions under these locations by default, thus avoiding any potential Windows Security issues in the future.
:: <code>../Tools/</code>
::: <code>../xEdit/</code>


=== File Extensions ===
=== File Extensions ===
It's recommended to unhide file extensions so that they are visible. This makes working with files much easier when modding.
It's recommended to unhide file extensions so they are visible to make identifying assets easier.
{{Spoiler|shown=Click here to show instructions for unhiding file extensions|hidden=<br>
{{Spoiler|shown=Steps - Show Windows File Extensions|hidden=
# Click on the Windows button.
# Click on the Windows button.
# Type in the search, ''File Explorer Options''.
# Type in the search, ''File Explorer Options''.
Line 34: Line 27:


== Steam Installation ==
== Steam Installation ==
Steam is a digital distribution platform by Valve Corp. used for purchasing, downloading, installing, and launching PC games. Download the program [https://store.steampowered.com/about/ from their website]. When installing Steam...
Steam is a digital distribution platform by Valve Corp. used for purchasing, downloading, installing, and launching PC games.
* Users should avoid installing to a location controlled by UAC (see [[Guide:SystemSetupGuide#Modding_Folder|Modding Folder]])
# Download the program [https://store.steampowered.com/about/ from their website]
** Steam installs its games in the <code>..Steam/steamapps/</code> sub-folder, thus not prompting UAC.
# Install Steam under the 'Games' folder created previously (e.g., <code>C:\Games\Steam\</code>)
* When choosing a Steam install location, keep in mind the space requirements for the games that will be installed ...
#* This location is outside of UAC control (by virtue of being owned by the user) and ensures path depth is shallow and simple.
** ... Steam can be installed to any drive, regardless of the drive used for the <code>../Modding/</code> folder created previously.  
#* Steam installs its games in the <code>..\steamapps\common\</code> sub-folder.


Steam can be installed to any drive and any location, regardless of the paths used for this Guide. However, all Step guides reference these default paths, so any deviations must be taken into account. When installing Steam to an alternative path...
* Avoid installing to existing paths created by Windows or third-party installations (see [[Guide:SystemSetupGuide#Modding_Folders|Modding Folders]]).
* Keep in mind the space requirements for the games that will be installed.
{{Spoiler|shown=Steps - Steam Installation|hidden=
Steam can be installed one of two ways:
Steam can be installed one of two ways:
{{Spoiler|shown=Show Steam installation instructions|hidden=&nbsp;
# {{fc|#ddd|Using a physical copy of the Steam-hosted game purchased from a retailer}}:
# {{fc|#ddd|Using a physical copy of the Steam-hosted game purchased from a retailer}}:
## Insert the game disk into your disk drive.
## Insert the game disk into your disk drive.
Line 51: Line 47:
## Navigate to your downloads location and launch '''SteamSetup.exe''' (see video link below).}}
## Navigate to your downloads location and launch '''SteamSetup.exe''' (see video link below).}}


=== Moving Steam and Installed Games ===
== Steam Game Installation & Maintenance ==
Since Steam installs its games in the <code>..Steam/steamapps/</code> sub-folder by default, UAC restrictions should not be an issue with any Steam install location; however, users can [https://support.steampowered.com/kb_article.php?ref=7418-YUBN-8129 utilize Steam to move the installation] locations if desired.
The basics relating to the Step guides follow. Visit [https://help.steampowered.com/en/faqs/view/71AB-698D-57EB-178C '''Steam Support'''] for official documentation.


== Game Installation ==
Games are downloaded and installed using the Steam application. Those who have installed a physical copy of the official game will have done the following.
Games are installed using the Steam application, and this can be done on one of two ways:
{{Spoiler|shown=Steps - Game Download & Install|hidden=
* Users who purchased a physical copy of the game from a retailer should already have the game installed from the Steam installation above.
* Use Steam to download and install:
{{Spoiler|shown=Show game installation instructions|hidden=&nbsp;
# Open the Steam application.
# Open the Steam application.
# Users who need to purchase a game can use the search bar to search for and purchase it from the app.
# From the top menu, click {{Ui|Library}}.
# Users who have already purchased a copy of the game, click '''Library''' at the top.
# If the game is not listed in the left menu, click {{Ui|Store}} from the top menu, and use the search bar to find and purchase the game.
# Users will now see a list of their purchased games. Games in grey are not installed. Click on the game needing to be installed.
# Grayed out listings in the left menu of the Steam library are not installed. Click on the game listing to install it, choosing the default 'Apps' location.}}
# On the game's page (right pane) click the '''Install''' button.
# Check the shortcuts desired and ensure the path is correct (e.g. <code>C:/Modding/Steam/</code> ).
# Click {{ui|Next}}, accept any EULA/Agreements, and install the game.}}


=== Initial Launch ===
=== Moving Steam and Installed Games{{Fc|yellow|<sup>(optional)</sup>}} ===
Once the game is installed, it needs to be loaded with the default launcher to register it with the system, install missing support software, and create necessary files. To do this:
Since Steam is presumably installed under a user-created folder like <code>C:\Games\Steam</code> Windows Security is not an issue; however, if Steam was previously installed into its default location, or if space for installed games is running low, it's simple (and recommended) to [https://help.steampowered.com/en/faqs/view/4BD4-4528-6B2E-8327 moved Steam games or Steam itself into a custom location].
# Click the '''Play''' button on the games page in Steam.
# Load the game to the game menu.
# Exit the game.


This completes the initial game setup. Repeat the above steps to install all the desired games before moving on.
=== Disabling Steam Automatic Updates{{Fc|yellow|<sup>(optional)</sup>}} ===
Step guides expect the latest version of supported games with all available official DLC, so disabling automatic updates is not advised; however, certain updates can break the respective guide on occasion until the guide is updated likewise. To stop Steam from automatically updating a game, right click on a game title in the Library, and select Properties > Updates > "Only update this game when I launch it".


=== Game Backup{{fs|0.75em|<sup> (optional)</sup>}} ===
=== Initialize the Game ===
Though not necessary with the use of Mod Organizer, some users may wish to create a backup of their vanilla game before modding begins. If so, now would be the time to complete this task. For this, Step recommends using [https://www.7-zip.org/ 7-Zip] to archive the following directories:
Once the game is installed, it needs to be loaded with the default launcher to register it with Windows and create necessary files. For games with DLC, it's mandatory to purchase and install all DLC prior to following the corresponding guide. Furthermore, it's mandatory to be running the latest version of said game(s), because the Step guides are only compatible with the latest game versions + all available DLC:
# Launch Steam, and click the {{Ui|Library}} from the top menu.
# Click on the game of choice in the left menu.
# Click {{Ui|Play}} button on the game page at right.
#* This will invoke one-time initialization scripts for required software.
#* For Bethesda games, video settings will be autodetected, game INIs will be created, and keys/values will be written to  the Windows registry.
# {{Fc|salmon|SkyrimSE ONLY}} (skip to #5 for other games) - This ensures all CC content are the latest versions available.
## Click {{Ui|Play}} within the launcher.
## Click {{Ui|Download}} to download the Creation Club data files.
## Click {{Ui|OK}} to reset the game files.
# Exit/quit the launcher/game.
 
=== Game Backup{{Fc|yellow|<sup>(optional)</sup>}} ===
Though not necessary with the use of Mod Organizer, some may wish to create a backup of the vanilla game before modding begins. If so, now would be the time to complete this task. For this, Step recommends using [https://www.7-zip.org/ 7-Zip] to archive the following directories:


* ''{{fc|instruction|Replace 'GameFolder'  with the name of the folder being archived.}}''
* ''{{fc|instruction|Replace 'GameFolder'  with the name of the folder being archived.}}''
* <code>../Steam/SteamApps/common/GameFolder</code>
* <code>..\Steam\steamapps\common\{{Fc|orange|<gameFolder>}}</code>
* <code>%USERPROFILE%/My Documents/My Games/GameFolder</code>
* <code>%USERPROFILE%\My Documents\My Games\{{Fc|orange|<gameFolder>}}</code>
* <code>%LOCALAPPDATA%/GameFolder</code> (e.g. <code>C:/Users/UserName/AppData/Local/GameFolder</code> )
* <code>%LOCALAPPDATA%\{{Fc|orange|<gameFolder>}}</code> (e.g. <code>C:\Users\UserName\AppData\Local\{{Fc|orange|<gameFolder>}}</code> )


To return those game folders to a vanilla state, the archives may simply be extracted to the same or analogous paths as above.
=== Reverting to Vanilla ===
During the modding experience it is handy to know how to re-establish a clean game installation. If the game was backed up as described previously, the archives may simply be extracted into the desired location (see [[Guide:System_Setup_Guide#Moving_Steam_and_Installed_Games_.28optional.29|previous instructions]]).


=== Reverting to Vanilla without a backup ===
If an archived backup was not created, the default game content can be downloaded fresh from Steam. This is a two part process:
During the modding experience it is handy to know how to re-establish a clean game installation. If an archived backup was not created (see above), there is still a much simpler way to achieve the same effect, which is essentially just deleting the game's files. This will require Steam to redownload these file.
==== Remove Installed Content ====
{{Spoiler|shown=Click here to show instructions|hidden=&nbsp;
{{Spoiler|shown=Steps - Remove Installed Content|hidden=
# Deactivate all mods using the mod manager.
# If mods from the Steam Workshop are installed, navigate to the Workshop and '''unsubscribe from ALL mods'''.
# In Steam, navigate to the Workshop and unsubscribe from '''every mod'''. (If mods from the Workshop are installed)
# Browse to the game directory:  <code>..\Steam\SteamApps\common\<gameFolder></code>
# Now browse to the game's directory:  <code>../Steam/SteamApps/common/GameFolder</code>
# Delete all files and subdirectories.
# Delete all files and subdirectories.
# Navigate to: <code>%USERPROFILE%/My Documents/My Games/GameName</code> and delete all files and subdirectories (make backups if desired before deleting).
# Launch Steam, and click on {{Ui|Library}} from the top menu.
# In the Steam app, right-click the game and select Properties.
# In the left menu, right click on the game, and click {{Ui|Manage >}} {{Ui|Uninstall}}.
# Under the ''Local Files'' tab, click '''[Verify integrity of game cache...]'''
# Browse to: <code>%USERPROFILE%\My Documents\My Games\<gameName></code>, and delete all files and subdirectories.}}
#* This will download any files that are corrupted, missing, or didn't pass a CRC check. It may take some time to complete, depending on Internet speeds.
# Launch the game from Steam to redo the system registration and recreate new game files.


The game installation should now be refreshed to a vanilla state.}}
==== Verify Integrity of Game Files ====
{{Spoiler|shown=Steps - Reacquire Game Data From Steam|hidden=
# Close any open mod managers.
# In the Steam app Library, right-click the game and select Properties.
# Under the '''''Installed Files''''' menu, click {{Ui|Verify integrity of game files...}}
#* This will reset all game data, and the game will need to be [[Guide:System_Setup_Guide#Initialize_the_Game|reinitialized]].}}


== Tools Installation and Setup ==
== 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. This will also reduce redundant tool installations while maintaining a good organization and saving hard drive space. All Step guides will assume the tools are installed as “standalone” applications; however, users are free to set up their tools as they see fit.
Step recommends the tools for modding be installed and setup as “standalone” applications whenever possible. This means a tool is installed once and used for all games.
 
=== Miscellaneous ===
There are some programs that are commonly used during modding that aren't necessarily "modding tools". Step recommends the following programs but it's ultimately up to the user. These programs may be installed in their default locations without issue:
; [https://www.7-zip.org/ 7-zip]
:: This is a popular file archiver. All mods are archived before uploading and may need to be extracted. Most mods have the custom format from 7-zip (.7z).
; [https://notepad-plus-plus.org/ Notepad++]
:: This is a popular text editor that supports many coding languages and has syntax highlighting, plugins (including Papyrus), and many more features useful for modding.
 
 
{{Alert|text=Install all of the following modding tools to the location created above (e.g., <code>..\Modding\Tools\</code>).}}
 
=== Mod Organizer{{Fs|0.75em|<sup>([https://stepmodifications.org/forum/topic/417-- Forum])</sup>}} ===
Mod Organizer 2 (MO) is the required mod manager for all Step Guides, since mod installation instructions are written specifically for MO. Other mod managers can be used, but they are NOT supported.
# Log in to [https://www.nexusmods.com/skyrimspecialedition/mods/6194 Nexus] and [https://www.nexusmods.com/skyrimspecialedition/mods/6194 Download] the MO Main File.
# Install MO into <code>..\Modding\Tools\Mod Organizer\</code>
 
 
{{alert|type=warn|size=mid|text={{Fc|highlight|'''No Man Sky:'''}} The following modding tools don't apply, so skip ahead to [[Guide:System_Setup_Guide#MO First-Launch Setup|MO First-Launch Setup]].}}


=== Mod Organizer 2 ===
=== BethINI{{Fs|0.75em|<sup>([https://stepmodifications.org/forum/topic/13322-- Forum])}} ===
Mod Organizer 2 is the successor to Mod Organizer (1), and is now the official mod manager for all Step guides. As such, we will continue to refer to Mod Organizer 2 as 'MO' or 'MO2' interchangeably. MO2 supports both 32-bit and 64-bit versions of Bethesda games and has basic support for a few games from other publishers. The major changes MO2 brings from the old version are:
# [https://www.nexusmods.com/skyrimspecialedition/mods/4875 Download] the BethINI Main File from Nexus.
# '''A return to normal plugin/archive relationship'''
# Double-click the archive to open it in 7z, and double-click into the top folder to expose all of the BethINI files/folders to be installed.
#: Users will no longer be able to load archives without loading their corresponding plugin, as MO1 allowed. On MO2, the plugins must be active for the archives to load, which is the intended behavior expected.
# Create the <code>..\Modding\Tools\BethINI</code> folder, and drag all files/folders into this folder.
# '''New installation options'''
#* When upgrading BethINI, remove all existing files/folders, and replace them with those from the latest archive.
#* MO2 may be installed as [[Guide:Mod_Organizer#Setup|"instanced" or "portable"]]. Certain third-party (mostly deprecated) applications like ''Merge Plugins'' can require special configuration with instanced installations of MO, but Step recommends it's successor, [https://z-edit.github.io/#/docs?t=Overview%2FMerge_Plugins_Comparison zMerge], which works fine with the instanced install method. Also see [https://www.youtube.com/watch?v=oQ1mdOGosdc Gamerpoet's zEdit tutorial] for all assets and instruction.
#* {{Fc|important|Step recommends “instanced” installation}}, meaning a single installation of MO2 is used for all supported games. Not only is this option cleaner and better organized, but it also allows us to design all of our game guides around using MO2's ''instances'', which allows management of ''independent'' mod lists.  
#* See the [[Guide:Mod_Organizer|Mod Organizer Guide]] for more information.


=== Tool List ===
=== LOOT{{Fs|0.75em|<sup>([https://stepmodifications.org/forum/topic/4995-- Forum])}} ===
The links below may lead to several different gamespaces on Nexus Mods or other websites. This is expected. Tools downloaded from various gamespaces or various sources will still work for all [[Property:Game|supported games]].
# [https://loot.github.io/ Download] the 7z archive of the latest 64-bit version of LOOT (e.g., <code>loot_#.#.#-win64.7z</code>).
# Double-click the archive to open it in 7z, and double-click into the top folder to expose all of the LOOT files/folders to be installed.
# Create the <code>..\Modding\Tools\LOOT</code> folder, and drag all files/folders into this folder.
#* When upgrading LOOT, remove all existing files/folders, and replace them with those from the latest archive.


Users should install the tools to the location created above (i.e., <code>../Modding/Tools/</code>). Install the following tools to that location:
=== xEdit{{Fs|0.75em|<sup>([https://stepmodifications.org/forum/topic/10094-- Forum])}} ===
{{ModTable|ModTableRow=
''''xEdit'''' is the generic name that applies to all applicable game variants (e.g., SSEEdit, TES5Edit, FO4Edit, etc.). For example, SSEEdit is the ''same application'' as FO4Edit, and the only difference is the name of the EXE files in the downloads. The application's game-specific behavior is triggered by the file name but can be overridden by command-line argument. In keeping with all modding tools being installed as standalone applications, Step will use the command-line argument via MO to invoke the applicable game mode rather than installing each variant (more on that later in the Guide).
{{#ask:[[Game::SkyrimLE]][[Version::3.0.0]][[ModGroup::01-Tools]]
# [https://www.nexusmods.com/skyrimspecialedition/mods/164 Download] SSEEdit (i.e., xEdit) from Nexus. {{Fc|salmon|'''SSEEdit' is 'xEdit', and applies to all Bethesda games!''}}
|?ModName
# Double-click the archive to open it in 7z, and double-click into the top folder to expose all of the xEdit files/folders to be installed.
|?Version
# Create the <code>..\Modding\Tools\xEdit</code> folder, and drag all files/folders into this folder.
|mainlabel=-
#* When upgrading xEdit, remove all existing files/folders, and replace them with those from the latest archive.
|named args=yes
|link=none
|format=plainlist
|template=ModTable/Row
|sort=OrderID
}}
}}


=== xLODGen{{Fs|0.75em|<sup>([https://stepmodifications.org/forum/topic/13451-xlodgen-terrain-lod-beta-85-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal-enderalse Forum])}} ===
# [https://stepmodifications.org/forum/topic/13451-xlodgen-terrain-lod-beta-85-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal-enderalse/ Read the OP carefully] before downloading and using xLODGen.
# Double-click the archive to open it in 7z, and drag the ''xLODGen'' folder directly into <code>..\Modding\Tools\</code>.
# Create a folder inside the xLODGen folder for the application output: <code>..\Modding\Tools\xLODGen\xLODGen_Output</code>
#* When upgrading xLODGen, remove all existing files/folders ''except'' <code>xLODGen_Output</code>, and replace them with those from the latest archive.


----
The "Modding" folder structure should now reflect:
The "Modding" folder structure should now reflect:
* <code>../Modding</code>
<pre>
** <code>../Tools</code>
..\Modding\Tools
*** <code>../BethINI</code>
..\Modding\Tools\BethINI
*** <code>../DynDOLOD</code>
..\Modding\Tools\LOOT
*** <code>../LOOT</code>
..\Modding\Tools\Mod Organizer
*** <code>../Mod Organizer</code>
..\Modding\Tools\xEdit
*** <code>../xEdit</code>
..\Modding\Tools\xLODGen</pre>
*** <code>../xLODGen</code>
* <code>../Steam</code> (optional; may be installed elsewhere)


== Configuration ==
=== MO First-Launch Setup ===
=== Mod Organizer Initialization ===
{{Alert|type=warn|text=For many instructions to make sense, this guide expects mods to be downloaded from Nexus using the "Mod Manager Download" button when it's available. This requires a Nexus user account to be associated with MO to leverage the API. Step doesn't support issues related to either 1) manual mod metadata maintenance or 2) obtaining mods from Nexus anonymously. Both add layers of complexity and potential issues that are beyond the scope of this guide.}}
Step recommends installing all applications as standalone programs, including Mod Organizer 2. If MO wass installed as a Portable application, the instructions below will need to be reinterpreted accordingly. For further information about this process, see the [[Guide:Mod_Organizer|Mod Organizer Guide]].
 
# Launch MO2 by running its executable (e.g. <code>..Modding/Tools/Mod Organizer/ModOrganizer.exe</code>)
As mentioned previously, Step recommends installing all applications as standalone programs. For MO, this behavior is configured at first launch of the program and creating a "Global Instance". For more detailed information about the MO configuration at first launch, see the [https://stepmodifications.org/wiki/Guide:Mod_Organizer#First-Launch_Setup Mod Organizer Guide].
# Upon launch, user will be presented with a windows explaining "instances". Click {{ui|Next}}.
# Launch MO by running its executable (e.g. <code>..\Modding\Tools\Mod Organizer\ModOrganizer.exe</code>)
# Next is the choice of using as a standalone or portable application. Choose {{ui|Create a global instance}}.
# Upon first launch, a window explaining "instances" will be presented. Select "Create a global instance", and tick {{ui|Next}}.
# The installer will detect games that are installed. Select any one of the games listed and click {{ui|Next}}.
# MO will detect games that are installed. Select any one of the games listed and tick {{ui|Next}}. {{Fc|salmon|''If the game wasn't auto-detected, manually browse to the game directory.''}}
#: If it didn't find a game, users can manually browse to the game's location.
# Type a name, or use the default, and tick {{ui|Next}}. {{Fc|salmon|''It is useful to include the guide name and version in the instance name.''}}
# Leave the default name or create a custom one. Step recommends using the default name or appending a custom name to the end. Click {{ui|Next}}.
# Choose an installation path, and tick {{ui|Next}}.
# Now user have the option of changing the location of data stored. Step recommends the default location, unless space restraints prevent this. Click {{ui|Next}}.
# Tick the {{ui|Connect to Nexus}} button. {{Fc|salmon|''This is necessary to leverage the Nexus API for mod data integrations between Nexus and MO!''}}
# Next window is for connection to Nexus Mods. Click the {{ui|Connnect to Nexus}} button.
#* If this fails, wait a moment and try again.
#* If this fails, wait a moment and try again.
#* When successful, a browser window will open to Nexus Mods. Log in, if required. Click the {{ui|Authorise}} button to allow the connection.
#* When successful, a browser window will open Nexus Mods. Log in, and tick the {{ui|Authorise}} button to allow the connection.
#* The browser page will reload and display a success message. The window/tab can be closed and the user should return to the installation. Click {{ui|Next}}
#* The browser page should present a 'success' message. Close the window, and tick {{ui|Next}}
# A confirmation window will display with the installation information. Click {{ui|Finish}}.
# Tick {{ui|Finish}} after the confirmation message appears.
#* A 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.
#* A tutorial prompt may appear. First time MO users should run it for a quick lesson on MO.
#* Another prompt will appear if MO is not set up to handle .NXM links, users should select {{ui|Yes}}.
#* Another prompt will appear if MO is not set up to handle .NXM links. Select {{ui|Yes}}.
# MO2 is now ready to use.
# MO is now ready to use. {{Fc|salmon|'''''NOTE:''' By default, the MO profile will be created under'' <code>%LOCALAPPDATA%\ModOrganizer\{{Fc|orange|<instanceName>}}\profiles\{{Fc|orange|<profileName>}}</code>.}}
{{Showroom|row1images=
{{GallerySimple|id=MOFirstStart|img=File:MOSetup02.PNG|caption=Step 2}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup02.PNG|caption=Step 3}}
{{GallerySimple|id=MOFirstStart|img=File:MOSetup03.PNG|caption=Step 3}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup03.PNG|caption=Step 4}}
{{GallerySimple|id=MOFirstStart|img=File:MOSetup05.PNG|caption=Step 4}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup05.PNG|caption=Step 5}}
{{GallerySimple|id=MOFirstStart|img=File:MOSetup06.PNG|caption=Step 5}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup06.PNG|caption=Step 6}}
{{clear}}
|row2=yes|row2images=
{{GallerySimple|id=MOFirstStart|img=File:MOSetup08.PNG|caption=Step 6}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup08.PNG|caption=Step 7}}
{{GallerySimple|id=MOFirstStart|img=File:MOSetup09.PNG|caption=Step 6-2}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup09.PNG|caption=Step 7-2}}
{{GallerySimple|id=MOFirstStart|img=File:MOSetup12.PNG|caption=Step 7}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup12.PNG|caption=Step 8}}
{{GallerySimple|id=MOFirstStart|img=File:MOSetup15.PNG|caption=Step 8}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup15.PNG|caption=Step 9}}
 
}}
{{Alert|type=mo|text='''Note on MO version tracking'''
To maximize efficiency of Nexus mod version tracking, Step now recommends that files not under "Main Files" be installed as separate mods to allow independent version tracking apart from the Main Files and global mod version. This will flag outdated versions of mods that have been updated. Because some mod authors don't understand or how this works (or just don't care), certain mods will perpetually be flagged as being outdated. To fix this, modify the '''''meta.ini''''' file MO creates in every mod such that the ''version'' and ''newestVersion'' values match the actual version of interest. When the mod is updated, this will trigger the flag again.}}
 
== Display & Overlays ==


=== Video Card Setup ===
=== System Drivers ===
Often under-appreciated, display and driver settings have a huge potential impact on the graphic quality of games and anything else displayed on the monitor. Unfortunately, Step can only provide recommendations, which may not be optimal for all systems, due to the wild variation of GFX cards and drivers...not to mention the added variation of PC components beyond just the display adapter (e.g., drive type, CPU, monitor, RAM ... can all impact GFX rendering to more/less degree).
Most drivers are updated fairly frequently, especially if hardware is relatively new. Driver updates often fix bugs, expand functionality, increase compatibility, and provide performance improvements. As such, it is important to keep drivers up to date, particularly chipset drivers.


==== Update Display Drivers ====
Pre-built PCs often bundle driver-update applications that can be used to download and install official driver updates specific to the PC. Drivers for custom-built PCs will be on the component manufacturer's websites. BIOS and firmware updates are often available as well but can be trickier and more risky to implement.
If there is any reason to believe the latest drivers installed aren't installed correctly, then complete all of the following instructions. Otherwise, complete steps 1 and 6 only.


{{Spoiler|shown=Click here to show instructions|hidden=&nbsp;
To help users of [https://www.intel.com/content/www/us/en/support/articles/000032252/software/software-applications.html compatible Intel-based motherboards] keep their drivers up-to-date, Intel provides it's [https://www.intel.com/content/www/us/en/download/18002/intel-driver-support-assistant.html Intel® Driver & Support Assistant(DAR)].  Once it has been downloaded and installed, it can: (1) easily identify drivers installed by Intel and third-parties, (2) scan for Intel driver and software updates as well as system and device information and (3) provide integrated support and links to other support information.  Subsequent visits to the DAR webpage will show if any drivers need updating.  All of which can make it easier to keep your motherboard's drivers current.
 
Users of AMD Radeon™ Series Graphics cards and Ryzen™ Chipsets can download and install [https://www.amd.com/en/support amd-software-adrenalin-edition] software to auto-Detect and install driver updates.  This software is for use with systems running Windows® 11 / Windows® 10 64-bit version 1809 and later.
 
=== Display Drivers ===
Most graphics software applications (i.e., GeForce Experience) provide links or automated updates for their software and drivers. If updated display drivers are available:
# Download and install the latest stable [https://www.amd.com/en/support AMD drivers] / [https://www.geforce.com/drivers Nvidia drivers].
# Reboot normally
 
Display drivers can often be upgraded without issue, particularly if done so using the video card's software; however, a bad installation or corruption is possible. In such situations, it is necessary to perform a "clean-upgrade" as described below:
{{Spoiler|shown=Steps - Update Display Drivers|hidden=
# Download the latest stable [https://www.amd.com/en/support AMD drivers] / [https://www.geforce.com/drivers Nvidia drivers].
# Download the latest stable [https://www.amd.com/en/support AMD drivers] / [https://www.geforce.com/drivers Nvidia drivers].
# Download [https://www.wagnardsoft.com/ DDU] and install it ([https://www.wagnardsoft.com/forums/viewforum.php?f=5 DDU forums]).
# Download [https://www.wagnardsoft.com/ DDU] and install it ([https://www.wagnardsoft.com/forums/viewforum.php?f=5 DDU forums]).
# Restart the system and boot into safe mode by repeatedly pressing F8 once the boot check initializes and before the OS begins loading (no need to uninstall the current drivers, but it will not hurt at all).
# Restart Windows, and boot into [https://support.microsoft.com/en-us/windows/start-your-pc-in-safe-mode-in-windows-10-92c27cff-db89-8644-1ce4-b3e5e56fe234 safe mode].
#* If using UEFI, go to to your power options and while holding down the Shift key, press restart. This will open the advanced menu where you can select to boot into safe mode.
# Launch DDU, and select the appropriate driver from the dropdown.
# Launch DDU, and select the appropriate driver from the drop-down combobox.
# Note the recommendations in DDU, and initialize the cleanup.
# Note the recommendations in DDU and initialize the cleanup.
# Reboot normally, and install the latest drivers downloaded from step 1.
# Reboot normally and install the latest drivers downloaded from step 1.}}
# Reboot normally again.}}


[[Guide:AMD_Radeon_Graphics|{{Fs|1.2em|'''AMD Adrenalin Settings'''}}]] - reference only to eliminate stutter or other glitches with AMD Adrenalin-powered systems.
Also see [[SkyrimSE:SSE Display Tweaks|SSE Display Tweaks]] for additional information. Thought this article is in reference to SSE, much of it applies to all games.


== Overlays ==
=== Overlays ===
Certain programs, especially ENBSeries, don't work properly when other program overlays are active. Therefore, users should consider disabling all overlays other programs are providing (MSI Afterburner, RivaTuner, GeForce Experience, etc.). Below are instructions for disabling the most common overlays. Disable all that are applicable to the system.
Certain programs (e.g., ENBSeries) don't work properly when other program overlays are active. Consider disabling all unnecessary overlays commonly found on modern Windows PCs.
 
{{Spoiler|shown=Steps - Disable Discord Overlay|hidden=
=== Discord ===
# Run Discord and open Settings (gear icon next to username).
To disable the overlay in Discord:
# In the left navigation under '''''Activity Settings''''', tick {{Ui|Game Overlay}}.
{{Spoiler|shown=Click here to show instructions|hidden=<br>
# ''Un''tick {{Ui|Enable in-game overlay}}.
# Run Discord and open the User Settings (gear icon next to username).
#* To enable in some games but not others, leave this setting ticked, and ...
# In the left navigation under ''Gaming Settings'', click '''Overlay'''.
#*# Still under '''''Activity Settings''''', click {{Ui|Activity Status}}.
# Toggle off '''Enable in-game overlay'''.
#*#* Ensure the monitor icon is toggled off (red) for each game for which the overlay should be disabled.
#* {{fc|instruction|Some users may wish to have Discord overlay active in some games but not others. These users can leave this setting toggled on and see the next steps.}}
# Close the window.
# Still under ''App Settings'', now click '''Game Activity'''.
#: Also see [https://support.discordapp.com/hc/en-us/articles/217659737-Games-Overlay-101 Discord's official documentation].}}
# Users will see a list of installed games with each listing having a monitor icon. Ensure this icon is toggled off (red) for each game the overlay should be disabled for.
{{Spoiler|shown=Steps - Disable GeForce Experience Overlay|hidden=
#* {{fc|warning|Skyrim LE users should turn off the overlay. It's label "at your own risk" by Discord.}}
# Close the window.}}
{{Alert small‏‎|type=notice|text=Users can find more information about Discord's overlay at [https://support.discordapp.com/hc/en-us/articles/217659737-Games-Overlay-101 Discord's official documentation].}}
 
=== GeForce Experience ===
To disable the overlay in GeForce Experience:
{{Spoiler|shown=Click here to show instructions|hidden=<br>
# Open the GeForce Experience application.
# Open the GeForce Experience application.
# Click the Settings icon (gear) at the top.
# Click the Settings icon (gear) at the top.
# Mid-way down the Setting page toggle '''IN-GAME OVERLAY''' off.
# Midway down the page, ''Un''toggle '''IN-GAME OVERLAY'''.
# Close the window.}}
# Close the window.}}
 
{{Spoiler|shown=Steps - Disable Steam Overlay|hidden=
=== Steam ===
# Open Steam, and click on the ''LIBRARY'' tab at top.
To disable the Steam overlay for Skyrim Special Edition:
# In the game list, right-click on '''''The Elder Scrolls V: Skyrim Special Edition'''''
{{Spoiler|shown=Click here to show instructions|hidden=<br>
# Select '''''Properties'''''.
# Open Steam
# ''Un''tick {{Ui|Enable the Steam Overlay while in-game}}
# Click ''LIBRARY'' at the top
# In your game list, right-click on ''The Elder Scrolls V: Skyrim Special Edition''
# Select '''Properties'''.
# Uncheck the “'''Enable the Steam Overlay while in-game'''” box
# Close the window.
# Close the window.
{{AlertSmall‏‎|type=notice|text=This process is the same for all games. Simply replicate the instructions for the game in question.}}


Alternatively users who would like to disable the Steam overlay for all games:
To disable the Steam overlay for ALL games:
# Load Steam.
# Open Steam, and click on  '''Steam''' in the toolbar.
# On the toolbar click '''Steam'''.
# On the dropdown menu click '''Settings'''.
# On the dropdown menu click '''Settings'''.
# On the new window, uncheck the '''Enabled the Steam overlay while in-game''' box then click '''OK'''.}}
# In the pop-up, ''Un''tick {{Ui|Enabled the Steam overlay while in-game}}, and click {{Ui|OK}}.}}
 
<!--=== Xbox Apps & Game Bar ===
=== Xbox Apps & Game Bar ===
The Xbox Game Bar is an app on Windows 10 that is part of the Xbox services. It's an overlay to display various features and widgets, which allow users to chat, record gameplay, control music, and more. Sounds nice but this takes up valuable system resources, has been reported to cause issues with some games, and there are better programs that do the same thing (not covered here). It's recommended to remove the Xbox services from the computer altogether. To do this:
The Xbox Game Bar is an app on Windows 10 that is part of the Xbox services. It's an overlay to display various features and widgets, which allow users to chat, record gameplay, control music, and more. Sounds nice but this takes up valuable system resources, has been reported to cause issues with some games, and there are better programs that do the same thing (not covered here). It's recommended to remove the Xbox services from the computer altogether. To do this:
{{Alert small|type=warning|text=Be advised this will remove the ability to use Game Pass!}}
{{Fc|red|Be advised this will remove the ability to use Game Pass!}}<br>
 
{{Spoiler|shown=Steps to Disable Xbox & Game Bar Overlays|hidden=
{{Spoiler|shown=Click here to show instructions|hidden=<br>
: {{Fc|salmon|text=Be advised this will remove the ability to use Game Pass.}}
# On the task bar, search ''PowerShell''.
: Follow the steps below. Alternatively, see [https://www.windowscentral.com/how-disable-and-remove-game-bar-windows-10-creators-update this article].
# Right-click on ''Windows PowerShell'' from the search and select, '''Run as administrator'''.
# Right-click the ''Windows PowerShell'' application shortcut, and select {{Ui|Run as administrator}}.
# Copy and paste the following, then hit '''Enter''' to list the xbox packages installled:
# Copy and paste the following, then hit '''Enter''':
#: <code><nowiki>dism /Online /Get-ProvisionedAppxPackages | Select-String PackageName | Select-String xbox</nowiki></code>
#: <code><nowiki>dism /Online /Get-ProvisionedAppxPackages | Select-String PackageName | Select-String xbox</nowiki></code>
# If packages are found, use the following to remove them:
#: If packages are found, use the following to remove them ALL (or modify "xbox" to match the desired package):
#: <div style="line-height:1.2em;"><code><nowiki>Get-ProvisionedAppxPackage -Online | `</nowiki><br><nowiki>Where-Object { $_.PackageName -match "xbox" } | `</nowiki><br><nowiki>ForEach-Object { Remove-ProvisionedAppxPackage -Online -PackageName $_.PackageName }</nowiki></code></div>
#: <code>{{Fs|0.8em|<nowiki>Get-ProvisionedAppxPackage -Online | Where-Object { $_.PackageName -match "xbox" } | ForEach-Object { Remove-ProvisionedAppxPackage -Online -PackageName $_.PackageName }</nowiki>}}</code>
# Now rerun the code from step 3 to verify no packages are listed.
# Return to step 2 to verify no packages are listed.
# Users should restart their PC.}}
# Restart Windows.}}-->
{{Alert small‏‎|type=notice|text=Users who wish to turn off services selectively should see [https://www.windowscentral.com/how-disable-and-remove-game-bar-windows-10-creators-update this article].}}


== Display Calibration ==
=== Display Calibration ===
Color calibration is critical to photographers and graphic artists who work across media types, but it's also equally important for gamers due to there being a lot of screenshot sharing and qualitative discussion about in-game visuals. However, with that said, all monitors will be slightly different in their accuracy of displaying colors.
Color calibration is critical to photographers and graphic artists who work across media types, but it's also equally important for gamers due to there being a lot of screenshot sharing and qualitative discussion about in-game visuals. However, with that said, all monitors will be slightly different in their accuracy of displaying colors.


'''The gist:''' Calibrate the monitor's display settings based on the video driver configuration utility with all other configuration baselines set to something akin to "mid level".
There are three places to configure color saturation, temperature, brightness, contrast, gamma, etc.:
# The monitor's built-in configuration menu
# Windows Color Management
# The video driver's configuration utility


There are three places to configure color saturation, temperature, brightness, contrast, gamma, etc:
The value of one setting can affect the appearance of other settings, and depending on the quality of the monitor, #1 above could be very good or just 'okay'. The #2 and #3 options should be standard though, since they are made to work across various monitors. The fact of the matter is, each monitor's calibration process is going to be slightly different. So much so that Step can not reliably provide one set of instructions for everyone. As such, we recommend following [https://www.rtings.com/monitor/learn/how-to-calibrate-your-monitor-settings RTINGS's guide for monitor calibration]. It's well written by professionals and easy to understand.
# The monitor's built-in configuration menu
 
# Windows color management
Additionally, RTINGS has a large [https://www.rtings.com/monitor/index list of monitors] they have professionally reviewed and calibrated. Many of these listings have ICC profiles available for downloaded and use, which provides their professional calibration for free. If using one of these ICC profiles, be sure the model matches the model of the monitor in use! Be aware there can be small differences even between monitors of the same models. Therefore, if an ICC profile is available it may not have the exact same results as RTINGS's review, but should be relatively close.
# The driver configuration utility


The value of one setting can affect the appearance of other settings, and depending on the quality of the monitor, #1 above could be very good or just 'OK'. The #2 and #3 objects should be standard though, since they are made to work across various monitors.
Additional calibration images can be found here: [http://www.lagom.nl/lcd-test/ http://www.lagom.nl/lcd-test/]
* Ensure that #1 above is set to "the middle ground" with respect to all settings. Having extreme settings in the monitor configuration could potentially constrain the other configurations. For some, setting all #1 values to mid levels will be best, but for others the 'auto-config' will be best (auto-config may not set all #1 values to mid settings). Depending on the monitor, there may be other auto-config options based on various presets. Whatever seems most "middle of the road" is probably best for option #1 above.
* Optionally, also run option #2 (Control Panel > Display > Calibrate Color) and set to 'vanilla' mid-levels with respect to all attributes. If this was never run previously, then it should already be at mid-levels.
* Finally, calibrate using option #3 (see below) using [https://www.photofriday.com/info/calibrate this reference image] and in a room with no direct lighting that could affect what the monitor displays (not-too-bright, diffuse-lighted room). The main calibration should be done using option #3 once a baseline 'canvas' has been established for options #1 and #2.
** '''AMD-CCC:''' |Desktop Management| > |Desktop Color| (click "Reactivate AMD color controls").
** '''Nvidia Control Panel:''' Access from the Windows Control Panel. |Display| > |Adjust desktop color settings|

Latest revision as of 01:51, March 27, 2024

Delta c.png

System Setup Guide

A Mandatory Prerequisite for Step Mod-Build Guides

by: The Step Team  | Forum Topic

This guide describes the expected configuration of the Windows 10/11 PC environment in order to complete ANY Bethesda mod-build guide on this wiki. This standard configuration prevents some common modding issues and facilitates support and resolution of many others.

Modding Folders[edit | edit source]

Create modding-related folders (aka, directory locations or 'paths'). Before doing so, consider the space requirements. A good rule of thumb for drive space requirements is ~100GB per game; however, this will vary from game to game. This space accounts for the game (e.g., Skyrim LE requires ~13GB, Fallout 4 requires ~30GB), installed mods, temporary files, modding tools, etc. Also remember that no PC drive should be filled to more than 90% of its capacity.

To avoid potential Windows Security and User Account Control (UAC) pemissions issues, avoid installing moddable games and modding resources under existing paths created by Windows or third-party programs. Install locations to avoid include but are not limited to...

  • C:\Program Files\
  • C:\Program Files (x86)\
  • C:\Users\
  • C:\Windows\

Instead, create the following folders on any drive root (e.g., C:\, D:\, E:\, etc.) to keep paths shallow. Installing games and modding tools onto a large, fast drive is beneficial:

C:\Modding
C:\Modding\Tools
C:\Games

In creating these directories, the 'Owner' is the Windows user who created them and who has full permissions under these locations by default, thus avoiding any potential Windows Security issues in the future.

File Extensions[edit | edit source]

It's recommended to unhide file extensions so they are visible to make identifying assets easier.

➕ [Click to show]➖ [Click to hide] Steps - Show Windows File Extensions
  1. Click on the Windows button.
  2. Type in the search, File Explorer Options.
  3. Click on the File Explorer Options listing.
  4. Click the View tab on the window that opens.
  5. In the Advanced settings pane, remove the checkbox next to Hide extensions for known file types.

Steam Installation[edit | edit source]

Steam is a digital distribution platform by Valve Corp. used for purchasing, downloading, installing, and launching PC games.

  1. Download the program from their website
  2. Install Steam under the 'Games' folder created previously (e.g., C:\Games\Steam\)
    • This location is outside of UAC control (by virtue of being owned by the user) and ensures path depth is shallow and simple.
    • Steam installs its games in the ..\steamapps\common\ sub-folder.

Steam can be installed to any drive and any location, regardless of the paths used for this Guide. However, all Step guides reference these default paths, so any deviations must be taken into account. When installing Steam to an alternative path...

  • Avoid installing to existing paths created by Windows or third-party installations (see Modding Folders).
  • Keep in mind the space requirements for the games that will be installed.
➕ [Click to show]➖ [Click to hide] Steps - Steam Installation

Steam can be installed one of two ways:

  1. Using a physical copy of the Steam-hosted game purchased from a retailer:
    1. Insert the game disk into your disk drive.
    2. If the installer doesn't run automatically, open the disk from Explorer and run Setup.exe.
    3. Follow the on-screen instructions to install Steam (see video link below)
  2. Download Steam from their website and install it:
    1. Navigate to the Steam website
    2. Download the Steam installer
    3. Navigate to your downloads location and launch SteamSetup.exe (see video link below).

Steam Game Installation & Maintenance[edit | edit source]

The basics relating to the Step guides follow. Visit Steam Support for official documentation.

Games are downloaded and installed using the Steam application. Those who have installed a physical copy of the official game will have done the following.

➕ [Click to show]➖ [Click to hide] Steps - Game Download & Install
  1. Open the Steam application.
  2. From the top menu, click [Library].
  3. If the game is not listed in the left menu, click [Store] from the top menu, and use the search bar to find and purchase the game.
  4. Grayed out listings in the left menu of the Steam library are not installed. Click on the game listing to install it, choosing the default 'Apps' location.

Moving Steam and Installed Games(optional)[edit | edit source]

Since Steam is presumably installed under a user-created folder like C:\Games\Steam Windows Security is not an issue; however, if Steam was previously installed into its default location, or if space for installed games is running low, it's simple (and recommended) to moved Steam games or Steam itself into a custom location.

Disabling Steam Automatic Updates(optional)[edit | edit source]

Step guides expect the latest version of supported games with all available official DLC, so disabling automatic updates is not advised; however, certain updates can break the respective guide on occasion until the guide is updated likewise. To stop Steam from automatically updating a game, right click on a game title in the Library, and select Properties > Updates > "Only update this game when I launch it".

Initialize the Game[edit | edit source]

Once the game is installed, it needs to be loaded with the default launcher to register it with Windows and create necessary files. For games with DLC, it's mandatory to purchase and install all DLC prior to following the corresponding guide. Furthermore, it's mandatory to be running the latest version of said game(s), because the Step guides are only compatible with the latest game versions + all available DLC:

  1. Launch Steam, and click the [Library] from the top menu.
  2. Click on the game of choice in the left menu.
  3. Click [Play] button on the game page at right.
    • This will invoke one-time initialization scripts for required software.
    • For Bethesda games, video settings will be autodetected, game INIs will be created, and keys/values will be written to the Windows registry.
  4. SkyrimSE ONLY (skip to #5 for other games) - This ensures all CC content are the latest versions available.
    1. Click [Play] within the launcher.
    2. Click [Download] to download the Creation Club data files.
    3. Click [OK] to reset the game files.
  5. Exit/quit the launcher/game.

Game Backup(optional)[edit | edit source]

Though not necessary with the use of Mod Organizer, some may wish to create a backup of the vanilla game before modding begins. If so, now would be the time to complete this task. For this, Step recommends using 7-Zip to archive the following directories:

  • Replace 'GameFolder' with the name of the folder being archived.
  • ..\Steam\steamapps\common\<gameFolder>
  • %USERPROFILE%\My Documents\My Games\<gameFolder>
  • %LOCALAPPDATA%\<gameFolder> (e.g. C:\Users\UserName\AppData\Local\<gameFolder> )

Reverting to Vanilla[edit | edit source]

During the modding experience it is handy to know how to re-establish a clean game installation. If the game was backed up as described previously, the archives may simply be extracted into the desired location (see previous instructions).

If an archived backup was not created, the default game content can be downloaded fresh from Steam. This is a two part process:

Remove Installed Content[edit | edit source]

➕ [Click to show]➖ [Click to hide] Steps - Remove Installed Content
  1. If mods from the Steam Workshop are installed, navigate to the Workshop and unsubscribe from ALL mods.
  2. Browse to the game directory: ..\Steam\SteamApps\common\<gameFolder>
  3. Delete all files and subdirectories.
  4. Launch Steam, and click on [Library] from the top menu.
  5. In the left menu, right click on the game, and click [Manage >] [Uninstall].
  6. Browse to: %USERPROFILE%\My Documents\My Games\<gameName>, and delete all files and subdirectories.

Verify Integrity of Game Files[edit | edit source]

➕ [Click to show]➖ [Click to hide] Steps - Reacquire Game Data From Steam
  1. Close any open mod managers.
  2. In the Steam app Library, right-click the game and select Properties.
  3. Under the Installed Files menu, click [Verify integrity of game files...]
    • This will reset all game data, and the game will need to be reinitialized.

Tools Installation and Setup[edit | edit source]

Step recommends the tools for modding be installed and setup as “standalone” applications whenever possible. This means a tool is installed once and used for all games.

Miscellaneous[edit | edit source]

There are some programs that are commonly used during modding that aren't necessarily "modding tools". Step recommends the following programs but it's ultimately up to the user. These programs may be installed in their default locations without issue:

7-zip
This is a popular file archiver. All mods are archived before uploading and may need to be extracted. Most mods have the custom format from 7-zip (.7z).
Notepad++
This is a popular text editor that supports many coding languages and has syntax highlighting, plugins (including Papyrus), and many more features useful for modding.


Info-Logo.png

NOTE

Install all of the following modding tools to the location created above (e.g., ..\Modding\Tools\).

Mod Organizer(Forum)[edit | edit source]

Mod Organizer 2 (MO) is the required mod manager for all Step Guides, since mod installation instructions are written specifically for MO. Other mod managers can be used, but they are NOT supported.

  1. Log in to Nexus and Download the MO Main File.
  2. Install MO into ..\Modding\Tools\Mod Organizer\


Warning-Logo.png

WARNING

No Man Sky: The following modding tools don't apply, so skip ahead to MO First-Launch Setup.

BethINI(Forum)[edit | edit source]

  1. Download the BethINI Main File from Nexus.
  2. Double-click the archive to open it in 7z, and double-click into the top folder to expose all of the BethINI files/folders to be installed.
  3. Create the ..\Modding\Tools\BethINI folder, and drag all files/folders into this folder.
    • When upgrading BethINI, remove all existing files/folders, and replace them with those from the latest archive.

LOOT(Forum)[edit | edit source]

  1. Download the 7z archive of the latest 64-bit version of LOOT (e.g., loot_#.#.#-win64.7z).
  2. Double-click the archive to open it in 7z, and double-click into the top folder to expose all of the LOOT files/folders to be installed.
  3. Create the ..\Modding\Tools\LOOT folder, and drag all files/folders into this folder.
    • When upgrading LOOT, remove all existing files/folders, and replace them with those from the latest archive.

xEdit(Forum)[edit | edit source]

'xEdit' is the generic name that applies to all applicable game variants (e.g., SSEEdit, TES5Edit, FO4Edit, etc.). For example, SSEEdit is the same application as FO4Edit, and the only difference is the name of the EXE files in the downloads. The application's game-specific behavior is triggered by the file name but can be overridden by command-line argument. In keeping with all modding tools being installed as standalone applications, Step will use the command-line argument via MO to invoke the applicable game mode rather than installing each variant (more on that later in the Guide).

  1. Download SSEEdit (i.e., xEdit) from Nexus. 'SSEEdit' is 'xEdit', and applies to all Bethesda games!
  2. Double-click the archive to open it in 7z, and double-click into the top folder to expose all of the xEdit files/folders to be installed.
  3. Create the ..\Modding\Tools\xEdit folder, and drag all files/folders into this folder.
    • When upgrading xEdit, remove all existing files/folders, and replace them with those from the latest archive.

xLODGen(Forum)[edit | edit source]

  1. Read the OP carefully before downloading and using xLODGen.
  2. Double-click the archive to open it in 7z, and drag the xLODGen folder directly into ..\Modding\Tools\.
  3. Create a folder inside the xLODGen folder for the application output: ..\Modding\Tools\xLODGen\xLODGen_Output
    • When upgrading xLODGen, remove all existing files/folders except xLODGen_Output, and replace them with those from the latest archive.

The "Modding" folder structure should now reflect:

..\Modding\Tools
..\Modding\Tools\BethINI
..\Modding\Tools\LOOT
..\Modding\Tools\Mod Organizer
..\Modding\Tools\xEdit
..\Modding\Tools\xLODGen

MO First-Launch Setup[edit | edit source]

Warning-Logo.png

WARNING

For many instructions to make sense, this guide expects mods to be downloaded from Nexus using the "Mod Manager Download" button when it's available. This requires a Nexus user account to be associated with MO to leverage the API. Step doesn't support issues related to either 1) manual mod metadata maintenance or 2) obtaining mods from Nexus anonymously. Both add layers of complexity and potential issues that are beyond the scope of this guide.

As mentioned previously, Step recommends installing all applications as standalone programs. For MO, this behavior is configured at first launch of the program and creating a "Global Instance". For more detailed information about the MO configuration at first launch, see the Mod Organizer Guide.

  1. Launch MO by running its executable (e.g. ..\Modding\Tools\Mod Organizer\ModOrganizer.exe)
  2. Upon first launch, a window explaining "instances" will be presented. Select "Create a global instance", and tick [Next].
  3. MO will detect games that are installed. Select any one of the games listed and tick [Next]. If the game wasn't auto-detected, manually browse to the game directory.
  4. Type a name, or use the default, and tick [Next]. It is useful to include the guide name and version in the instance name.
  5. Choose an installation path, and tick [Next].
  6. Tick the [Connect to Nexus] button. This is necessary to leverage the Nexus API for mod data integrations between Nexus and MO!
    • If this fails, wait a moment and try again.
    • When successful, a browser window will open Nexus Mods. Log in, and tick the [Authorise] button to allow the connection.
    • The browser page should present a 'success' message. Close the window, and tick [Next]
  7. Tick [Finish] after the confirmation message appears.
    • A tutorial prompt may appear. First time MO users should run it for a quick lesson on MO.
    • Another prompt will appear if MO is not set up to handle .NXM links. Select [Yes].
  8. MO is now ready to use. NOTE: By default, the MO profile will be created under %LOCALAPPDATA%\ModOrganizer\<instanceName>\profiles\<profileName>.
Moicon.png

MO2

Note on MO version tracking

To maximize efficiency of Nexus mod version tracking, Step now recommends that files not under "Main Files" be installed as separate mods to allow independent version tracking apart from the Main Files and global mod version. This will flag outdated versions of mods that have been updated. Because some mod authors don't understand or how this works (or just don't care), certain mods will perpetually be flagged as being outdated. To fix this, modify the meta.ini file MO creates in every mod such that the version and newestVersion values match the actual version of interest. When the mod is updated, this will trigger the flag again.

Display & Overlays[edit | edit source]

System Drivers[edit | edit source]

Most drivers are updated fairly frequently, especially if hardware is relatively new. Driver updates often fix bugs, expand functionality, increase compatibility, and provide performance improvements. As such, it is important to keep drivers up to date, particularly chipset drivers.

Pre-built PCs often bundle driver-update applications that can be used to download and install official driver updates specific to the PC. Drivers for custom-built PCs will be on the component manufacturer's websites. BIOS and firmware updates are often available as well but can be trickier and more risky to implement.

To help users of compatible Intel-based motherboards keep their drivers up-to-date, Intel provides it's Intel® Driver & Support Assistant(DAR). Once it has been downloaded and installed, it can: (1) easily identify drivers installed by Intel and third-parties, (2) scan for Intel driver and software updates as well as system and device information and (3) provide integrated support and links to other support information. Subsequent visits to the DAR webpage will show if any drivers need updating. All of which can make it easier to keep your motherboard's drivers current.

Users of AMD Radeon™ Series Graphics cards and Ryzen™ Chipsets can download and install amd-software-adrenalin-edition software to auto-Detect and install driver updates. This software is for use with systems running Windows® 11 / Windows® 10 64-bit version 1809 and later.

Display Drivers[edit | edit source]

Most graphics software applications (i.e., GeForce Experience) provide links or automated updates for their software and drivers. If updated display drivers are available:

  1. Download and install the latest stable AMD drivers / Nvidia drivers.
  2. Reboot normally

Display drivers can often be upgraded without issue, particularly if done so using the video card's software; however, a bad installation or corruption is possible. In such situations, it is necessary to perform a "clean-upgrade" as described below:

➕ [Click to show]➖ [Click to hide] Steps - Update Display Drivers
  1. Download the latest stable AMD drivers / Nvidia drivers.
  2. Download DDU and install it (DDU forums).
  3. Restart Windows, and boot into safe mode.
  4. Launch DDU, and select the appropriate driver from the dropdown.
  5. Note the recommendations in DDU, and initialize the cleanup.
  6. Reboot normally, and install the latest drivers downloaded from step 1.
  7. Reboot normally again.

Also see SSE Display Tweaks for additional information. Thought this article is in reference to SSE, much of it applies to all games.

Overlays[edit | edit source]

Certain programs (e.g., ENBSeries) don't work properly when other program overlays are active. Consider disabling all unnecessary overlays commonly found on modern Windows PCs.

➕ [Click to show]➖ [Click to hide] Steps - Disable Discord Overlay
  1. Run Discord and open Settings (gear icon next to username).
  2. In the left navigation under Activity Settings, tick [Game Overlay].
  3. Untick [Enable in-game overlay].
    • To enable in some games but not others, leave this setting ticked, and ...
      1. Still under Activity Settings, click [Activity Status].
        • Ensure the monitor icon is toggled off (red) for each game for which the overlay should be disabled.
  4. Close the window.
    Also see Discord's official documentation.
➕ [Click to show]➖ [Click to hide] Steps - Disable GeForce Experience Overlay
  1. Open the GeForce Experience application.
  2. Click the Settings icon (gear) at the top.
  3. Midway down the page, Untoggle IN-GAME OVERLAY.
  4. Close the window.
➕ [Click to show]➖ [Click to hide] Steps - Disable Steam Overlay
  1. Open Steam, and click on the LIBRARY tab at top.
  2. In the game list, right-click on The Elder Scrolls V: Skyrim Special Edition
  3. Select Properties.
  4. Untick [Enable the Steam Overlay while in-game]
  5. Close the window.

To disable the Steam overlay for ALL games:

  1. Open Steam, and click on Steam in the toolbar.
  2. On the dropdown menu click Settings.
  3. In the pop-up, Untick [Enabled the Steam overlay while in-game], and click [OK].

Display Calibration[edit | edit source]

Color calibration is critical to photographers and graphic artists who work across media types, but it's also equally important for gamers due to there being a lot of screenshot sharing and qualitative discussion about in-game visuals. However, with that said, all monitors will be slightly different in their accuracy of displaying colors.

There are three places to configure color saturation, temperature, brightness, contrast, gamma, etc.:

  1. The monitor's built-in configuration menu
  2. Windows Color Management
  3. The video driver's configuration utility

The value of one setting can affect the appearance of other settings, and depending on the quality of the monitor, #1 above could be very good or just 'okay'. The #2 and #3 options should be standard though, since they are made to work across various monitors. The fact of the matter is, each monitor's calibration process is going to be slightly different. So much so that Step can not reliably provide one set of instructions for everyone. As such, we recommend following RTINGS's guide for monitor calibration. It's well written by professionals and easy to understand.

Additionally, RTINGS has a large list of monitors they have professionally reviewed and calibrated. Many of these listings have ICC profiles available for downloaded and use, which provides their professional calibration for free. If using one of these ICC profiles, be sure the model matches the model of the monitor in use! Be aware there can be small differences even between monitors of the same models. Therefore, if an ICC profile is available it may not have the exact same results as RTINGS's review, but should be relatively close.

Additional calibration images can be found here: http://www.lagom.nl/lcd-test/