Guide:System Setup Guide: Difference between revisions

From Step Mods | Change The Game
 
(393 intermediate revisions by 6 users not shown)
Line 1: Line 1:
[[Category:General Modding Guides]][[Category:Official Mod-Build 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|limit=4}}
[[Category:General Modding Guides]][[Category:Official Mod-Build Guides]]{{#seo:
{{Fc|important|This guide describes the expected configuration of the 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.  
|title=Step System Setup Guide - SSG
|title_mode=replace
|keywords=pc gaming, modding environment, modding best practice, modding guide
|description=A mandatory prerequisite for following Step Game Guides, featuring best practices for establishing a hassle-free modding environment for gaming on the PC, ensuring the things that go wrong are related to mods, mod configurations, or modding applications rather than the foundation upon which it's all built
|type=website
|image_alt=Change the game
|locale=en-US
|modified_time={{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
}}{{PageTitle|logo=delta|title=System Setup Guide (SSG)|subtitle=A Mandatory Prerequisite for Following Step Game Guides|author=The Step Team|forumtid=14917}}{{TOC|limit=4}}
{{Fc|important|This guide describes the expected configuration of the Windows 10/11  PC environment in order to follow mod-build guides 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:
After completing the SSG, return to the Game Guide using the top navigation bar.
* {{Fc|salmon|This guide assumes a Windows 10 environment.}}
** Windows 7 is at End-of-Life and Windows 8 is not recommended, therefore, Windows 10 is the only OS supported by Step.
* {{Fc|salmon|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 ==
== Modding Folders ==
First, 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|salmon|Avoid installing games and modding resources within the following directory locations without first understanding ''why'' this can cause issues and ''how'' to circumvent them:}}
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.
* <code>C:\Windows\..</code>
* <code>C:\Program Files\..</code>
* <code>C:\Program Files (x86)\..</code>
* <code>C:\Users\{logged in user}\AppData\Local</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.


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.
To avoid potential Windows Security / 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...
{{alert small|text=A good rule of thumb for modding drive space requirements is ~100 GB per game.}}
* <code>{{Fc|red|C:\Program Files\}}</code>
* <code>{{Fc|red|C:\Program Files (x86)\}}</code>
* <code>{{Fc|red|C:\Users\}}</code>
* <code>{{Fc|red|C:\Windows\}}</code>


Specifically, begin by creating the following folders:
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:
# '''Games''', located at the root of any drive: e.g., <code>C:\Games</code>,
<pre>C:\Modding
# '''Modding''', inside the new ''Modding'' folder created above: e.g., <code>C:\Games\Modding</code>
C:\Modding\Tools
This keeps path depth shallow and path strings brief.
C:\Games</pre>
 
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.
=== Folder Structure ===
Extend the modding folder structure as follows, based on the game being modded:
==== Bethesda Games ====
: <code>..Games\Modding\Bethesda Tools\</code>
==== No Man's Sky ====
: <code>..Games\Modding\NoMansSky\</code>
:: <code>..\NoMansSky\Tools\</code>
<!--::: <code>..\Tools\AMUMSS</code>-->
::: <code>..\Tools\PSArcTool</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-type extensions to simplify asset identification.
{{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 43: Line 38:


== Steam Installation ==
== Steam Installation ==
Steam is a digital distribution platform by Valve Corp. used for purchasing, downloading, installing, and launching PC games.
As is mentioned throughout this guide, Step only supports Steam games at this time. 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]
# Download the program [https://store.steampowered.com/about/ from their website]
# Run the installer and install Steam to the '''Games''' folder created above: e.g., <code>C:\Games\</code>
# Install Steam under the 'Games' folder created previously (e.g., <code>C:\Games\Steam\</code>)
#* This location is outside of UAC control and keeps path depth shallow.
#* 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 <code>..\Steam\steamapps\common\</code> sub-folder.
#* 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 our Guides will reference these default paths, therefore, users will have to remember to change the paths to suit their setups. When installing Steam to an alternative path...
* avoid installing to a location controlled by UAC (see [[Guide:SystemSetupGuide#Modding_Folder|Modding Folder]])
* keep in mind the space requirements for the games that will be installed


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 64: Line 58:
## 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 ===
== Game Installation & Maintenance Via Steam ==
Since Steam installs its games in the <code>..Steam\steamapps\</code> sub-folder by default, UAC restrictions are usually not an issue, regardless of install location; however, users are encouraged not to install within a UAC location to avoid any potential issues with the modding tools and unknown security setups. Users who already have Steam installed and desire to move their game installations can [https://support.steampowered.com/kb_article.php?ref=7418-YUBN-8129 utilize Steam to do so].
The basics relating to the Step guides follow. Visit [https://help.steampowered.com/en/faqs/view/71AB-698D-57EB-178C '''Steam Support'''] for the more lengthy official documentation.
 
=== Consider Moving Steam and Installed Games ===
Since [[Guide:System_Setup_Guide#Steam_Installation|Steam is 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 move Steam games or Steam itself into a custom location].


== Game Installation ==
=== Installing a Steam Game ===
Games are installed using the Steam application, and this can be done on one of two ways:
Games are downloaded and installed under the Steam directory location <code>..\Steam\steamapps\common\</code> using the Steam application.
* Users who purchased a physical copy of the game from a retailer should already have the game installed from the Steam installation above.
{{Spoiler|shown=Steps - Game Download & Install|hidden=
* 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:\Games\Steam\</code> ).
# Click {{ui|Next}}, accept any EULA/Agreements, and install the game.}}


=== Initial Launch ===
=== Initialize the Game ===
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:
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:
# Click the '''Play''' button on the games page in Steam.
# Launch Steam, and click the {{Ui|Library}} from the top menu.
# Load the game to the game menu.
# Click on the game of choice in the left menu.
# Exit the game.
# 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.


This completes the initial game setup. Repeat the above steps to install all the desired games before moving on.
=== Restoring the Default (Vanilla) Game Folder ===
If the game has been previously installed and modded, there are likely third-party files under the Steam game directory location. Depending on the methods and tools used, some of these files could cause problems later. Additionally, Step guides always expect the most current Steam game release. Restoring the default Steam (vanilla) game installation is highly recommended and ensures there are no hangups later.


=== Game Backup{{fs|0.75em|<sup> (optional)</sup>}} ===
If an [[Guide:System_Setup_Guide#Game_Backup(optional)|archived backup]] of the vanilla game was not created, the default game content can be restored fresh from Steam. This is a two part process.
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:
==== Delete Game Files and User Data ====
{{Spoiler|shown=Steps - Part 1: Remove Installed Content|hidden=
# If mods from the Steam Workshop are installed, navigate to the Workshop and '''unsubscribe from ALL mods'''.
# Browse to the game directory:  <code>.\Steam\SteamApps\common\<gameFolder></code>
# Delete all files and subdirectories.
# Launch Steam, and click on {{Ui|Library}} from the top menu.
# In the left menu, right click on the game, and click {{Ui|Manage >}} {{Ui|Uninstall}}.
# Browse to: <code>%USERPROFILE%\My Documents\My Games\<gameName></code>, and delete all files and subdirectories.}}


* ''{{fc|instruction|Replace 'GameFolder'  with the name of the folder being archived.}}''
==== Verify Integrity of Game Files ====
* <code>..\Steam\steamapps\common\GameFolder</code>
{{Spoiler|shown=Steps - Part 2: Reacquire Game Files|hidden=
* <code>%USERPROFILE%\My Documents\My Games\GameFolder</code>
# Close any open mod managers.
* <code>%LOCALAPPDATA%\GameFolder</code> (e.g. <code>C:\Users\UserName\AppData\Local\GameFolder</code> )
# 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]].}}


To return those game folders to a vanilla state, the archives may simply be extracted to the same or analogous paths as above.
=== 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".


=== Reverting to Vanilla without a backup ===
=== Game Backup{{Fc|yellow|<sup>(optional)</sup>}} ===
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.
Some mod management applications manipulate the physical game files in the Steam game directory location: <code>..\Steam\steamapps\common\</code>. MO instead uses a virtual game directory location, preserving all of the vanilla game files. Even so, some engine-level runtime mods (e.g., post-processors, script extenders, etc.) require their EXE and DLL files to be installed in the physical game directory location. Some may wish to create a backup of the vanilla game before any changes under the game location take place. For this, Step recommends using [https://www.7-zip.org/ 7-Zip] to archive the following directories:
{{Spoiler|shown=Click here to show instructions|hidden=&nbsp;
* ''{{fc|instruction|Replace 'GameFolder' with the name of the folder being archived.}}''
# Deactivate all mods using the mod manager.
* <code>..\Steam\steamapps\common\{{Fc|orange|<gameFolder>}}</code>
# In Steam, navigate to the Workshop and unsubscribe from '''every mod'''. (If mods from the Workshop are installed)
* <code>%USERPROFILE%\My Documents\My Games\{{Fc|orange|<gameFolder>}}</code>
# Now browse to the game's directory:  <code>../Steam/SteamApps/common/GameFolder</code>
* <code>{{Fc|blue|%LOCALAPPDATA%}}\{{Fc|orange|<gameFolder>}}</code> (e.g. <code>{{Fc|blue|C:\Users\<UserName>\AppData\Local}}\{{Fc|orange|<gameFolder>}}</code> )
# 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).
# In the Steam app, right-click the game and select Properties.
# Under the ''Local Files'' tab, click '''[Verify integrity of game cache...]'''
#* 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.}}
== Tools Installation and Setup ==
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.


== Tools Installation and Setup ==
=== Miscellaneous ===
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.
There are some programs that are commonly used during modding that aren't necessarily "modding tools". These are general applications used for more than just modding and should NOT be installed under the <code>..\Modding\Tools\</code> location:
; [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.


=== Mod Organizer 2 ([https://stepmodifications.org/forum/topic/198-- Forum]) ===
# [https://www.nexusmods.com/skyrimspecialedition/mods/6194 Download] MO2 from [https://www.nexusmods.com/skyrimspecialedition/mods/6194 Nexus].
# Install MO2 by running the installer and changing the path to the ''Modding'' folder (e.g. <code>..Games\Modding\Mod Organizer\</code>)
#* See the [[Guide:Mod_Organizer#Installation_and_Setup|Mod Organizer Guide for installation guidance]].


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:
{{Alert|text=Install all of the following modding tools to the <code>..\Modding\Tools\</code> location created previously.}}
# '''A return to normal plugin/archive relationship'''
#: 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.
# '''New installation options'''
#* 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 mod-build guides around using MO2's ''instances'', which allows management of ''independent'' mod lists.
#* See the [[Guide:Mod_Organizer#Setup|Portable vs Instanced Installation]] Sidebox on the Mod Organizer Guide for more information.


{{alert|type=notice|size=mid|text=No Man Sky users should stop here and [[Guide:System_Setup_Guide#Mod_Organizer_Initialization|skip to the MO Initialization]].}}
=== 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. Vortex users can [https://stepmodifications.org/forum/topic/19414-pandora-behavior-engine/page/2/#comment-277826 easily switch to MO] without losing downloaded or installed mods by moving some files around using Windows Explorer. Then each download/mod's metadata can be synced,
# 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>


=== Modding Tools Setup ===
Install tools to the location created above (e.g., <code>..\Games\Modding\Bethesda Tools\</code>).
{{Alert|text=These tools are 'generic' and pertain to multiple Bethesda games, regardless of the game guide being followed. Simply make the adjustments indicated by the referring guide for the particular game of interest.}}


==== BethINI ([https://stepmodifications.org/forum/topic/13322-- Forum]) ====
{{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]].}}
# [https://www.nexusmods.com/skyrimspecialedition/mods/4875 Download] BethINI from Nexus.
# Extract the archive to the *Tools* folders (e.g. <code>..\Games\Modding\Bethesda Tools\BethINI\</code>)


==== DynDOLOD ([https://stepmodifications.org/forum/forum/223-shesons-dyndolod-xlodgen/ Forum]) ====
=== BethINI{{Fs|0.75em|<sup>([https://stepmodifications.org/forum/topic/13322-- Forum])}} ===
# [https://www.nexusmods.com/skyrimspecialedition/mods/32382 Download] and unpack the archive into e.g. <code>..\Games\Modding\Bethesda Tools\DynDOLOD\</code>
# Download BethINI:
# If [https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads Visual Studio 2015, 2017 and 2019] are missing, download and install them; ''both x86 and x64 files''.
#* Check the Release Date at the top of the [[Main_Page|Step guide of interest]] (Step guides are also linked in the top nav under '''Game Guides''').
#* For guides released prior to 2024: [https://www.nexusmods.com/skyrimspecialedition/mods/4875 Download the previous version of BethINI].
#* For guides released in 2024 onward: [https://www.nexusmods.com/site/mods/631 Download BethINI Pie].
# 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.
# Create the <code>..\Modding\Tools\BethINI</code> folder, and drag all files/folders into this folder.
#* When upgrading BethINI, merge the updated archive content into existing files/folders with overwrite.


The Resources file will be installed later, so ignore it for now.
=== LOOT{{Fs|0.75em|<sup>([https://stepmodifications.org/forum/topic/4995-- Forum])}} ===
# [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.


==== LOOT ([https://stepmodifications.org/forum/topic/4995-- Forum]) ====
=== xEdit{{Fs|0.75em|<sup>([https://stepmodifications.org/forum/topic/10094-- Forum])}} ===
# [https://loot.github.io/ Download] the latest version of LOOT from their [https://github.com/loot/loot/releases GitHub page] ('''LOOT.Install.exe''').
''''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).
# Install LOOT by running the installer and changing the path to the ''Tools'' folder (e.g. <code>..\Games\Modding\Bethesda Tools\LOOT\</code>)
# [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!''}}
# 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.
# Create the <code>..\Modding\Tools\xEdit</code> 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.


==== xEdit ([https://stepmodifications.org/forum/topic/10094-- Forum])====
=== 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://www.nexusmods.com/skyrimspecialedition/mods/164 Download] xEdit from Nexus Mods.
# [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.
# Extract the archive to the ''xEdit'' folder: <code>..\Games\Modding\Bethesda Tools\xEdit</code>
# Double-click the archive to open it in 7z, and drag the ''xLODGen'' folder directly into <code>..\Modding\Tools\</code>.
#: [[Guide:XEdit|xEdit Guide]]
# 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.


==== xLODGen ([https://stepmodifications.org/forum/topic/8217-- Forum]) ====
# Ensure the latest version of the required [https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads redistributable packages] are installed. Both the x86 and x64 version should be installed.
# [https://stepmodifications.org/forum/topic/13451-xlodgen-terrain-lod-beta-76-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal-enderalse/ Download] the latest xLODGen Beta from the link in the forum post.
# Extract the ''xLODGen'' folder from the archive to the ''Tools'' folder: (e.g. <code>..\Games\Modding\Bethesda Tools\xLODGen</code>)
# Open the extracted folder and create a new folder for the tool's output files.
#* Recommended folder name: '''xLODGen_Output'''
----
----
The "Modding" folder structure should now reflect:
The "Modding" folder structure should now reflect:
* <code>..Games\Modding\Mod Organizer</code>
<pre>
* <code>..Games\Modding\Bethesda Tools</code>
..\Modding\Tools
** <code>..\Bethesda Tools\BethINI</code>
..\Modding\Tools\BethINI
** <code>..\Bethesda Tools\DynDOLOD</code>
..\Modding\Tools\LOOT
** <code>..\Bethesda Tools\LOOT</code>
..\Modding\Tools\Mod Organizer
** <code>..\Bethesda Tools\xEdit</code>
..\Modding\Tools\xEdit
** <code>..\Bethesda Tools\xLODGen</code>
..\Modding\Tools\xLODGen</pre>
 
== Configuration ==
=== Mod Organizer Initialization ===
Step recommends installing all applications as standalone programs, including Mod Organizer 2. If MO was 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#Installation_and_Setup|Mod Organizer Guide]].
# Launch MO2 by running its executable (e.g. <code>..Games\Modding\Mod Organizer\ModOrganizer.exe</code>)
# Upon launch, a windows explaining "instances" will be presented. Click {{ui|Next}}.
# Next is the choice of using as a standalone or portable application. Choose {{ui|Create a global instance}}.
# The installer will detect games that are installed. Select any one of the games listed and click {{ui|Next}}.
#: If it didn't find a game, users can manually browse to the game's location.
# 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}}.
# 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}}.
# Next window is for connection to Nexus Mods. Click the {{ui|Connnect to Nexus}} button.
#* 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.
#* 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}}
# A confirmation window will display with the installation information. Click {{ui|Finish}}.
#* 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.
#* Another prompt will appear if MO is not set up to handle .NXM links, users should select {{ui|Yes}}.
# MO2 is now ready to use.
{{Showroom|row1images=
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup02.PNG|caption=Step 3}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup03.PNG|caption=Step 4}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup05.PNG|caption=Step 5}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup06.PNG|caption=Step 6}}
|row2=yes|row2images=
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup08.PNG|caption=Step 7}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup09.PNG|caption=Step 7-2}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup12.PNG|caption=Step 8}}
{{ShowroomImage|id=MO2FirstStart|img=File:MO2Setup15.PNG|caption=Step 9}}
}}


=== System Drivers ===
=== MO First-Launch Setup ===
{{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 out of scope.}}


A driver is software that allows computer programs to interact with hardware devices. Most drivers are updated relatively frequently, especially drivers for graphic devices such as video cards. Driver updates often fix bugs, expand compatibility, and provide performance improvements. As such, it is important to have up-to-date drivers for all hardware on the system, and users should ensure they do.
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].


If the system being used for mod testing is pre-built (i.e., an off-the-shelf computer under a brand name: HP, ACER, or ASUS) an application is usually included that assists users with installing vendor specific driver updates. If this is the case, use this application since many pre-built systems have drivers specifically designed for their proprietary hardware.<br>
First, launch MO by running its executable (e.g. <code>..\Modding\Tools\Mod Organizer\ModOrganizer.exe</code>). If this is the first time MO is started after installation, the "Creating a new instance" wizard will be presented. If this is NOT the first time launching MO, click on the {{Icon|moinstance}} icon, and then click {{Ui|+ Create new instance}} in the upper left of the instances windows to start the wizard.
: '''Exception:''' the latest display drivers for these systems should always be obtained from the video card company's website (AMD or Nvidia).
{{CollapsibleTable
| row = 1
| type = MOinstance
| title = Create a global instance
| text = Click {{Ui|Next}}, and select "Create a global instance", and click {{ui|Next}} again.
| images = MOSetup02.PNG}}
{{CollapsibleTable
| row = 2
| type = MOinstance
| title = Select the game
| text = MO will detect games that are installed. Select any one of the games listed and click {{ui|Next}}. {{Fc|salmon|''If the game wasn't auto-detected, manually browse to the game directory.''}}
* Select the '''''Steam''''' game edition if prompted. {{Fc|salmon|''Step guides only support Steam games. Other editions can be used but aren't supported by Step guide curators.''}}
| images = MOSetup03.PNG}}
{{CollapsibleTable
| row = 3
| type = MOinstance
| title = Name the instance
| text = Type a name, or use the default, and click {{ui|Next}}.
* Step recommends using the guide name and version number as the instance name (e.g. <code>Step SkyrimSE v#.#</code>), which makes it possible to completely partition game-specific builds. MO profiles do not allow this degree of separation. See [[Guide:Mod_Organizer/Instances_vs_Profiles|Instances vs Profiles]] for more information.
* If prompted to "Configure profile settings", tick all boxes before clicking {{ui|Next}}.
| images = MOSetup05.PNG}}
{{CollapsibleTable
| row = 4
| type = MOinstance
| title = Set the instance location
| text = Use the default path (recommended), or choose a custom path, and click {{ui|Next}}.
| images = MOSetup06.PNG}}
{{CollapsibleTable
| row = 5
| type = MOinstance
| title = Connect to Nexus (only appears on first launch)
| text =  Click the {{ui|Connect to Nexus}} button. {{Fc|salmon|''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.
| images = MOSetup08.PNG}}
{{CollapsibleTable
| row = 6
| type = MOinstance
| title = Authorize Nexus
| text = If successful, a browser window will open Nexus Mods. Log in, and click the {{ui|Authorise}} button to allow the connection.
* The browser page should present a 'success' message. Close the window, and click {{ui|Next}}
| images = MOSetup09.PNG}}
{{CollapsibleTable
| row = final
| type = MOinstance
| title = Create the instance
| text = Click {{ui|Finish}} after the confirmation message appears.
* A tutorial prompt may appear, which is recommended for those new to MO.
* Another prompt will appear if MO is not set up to handle .NXM links. Select {{ui|Yes}}.
| images = MOSetup12.PNG}}<br>
MO is now ready to use. {{Fc|salmon|''By default, the MO profile will be created under'' <code>%LOCALAPPDATA%\ModOrganizer\{{Fc|orange|<instanceName>}}\profiles\{{Fc|orange|<profileName>}}</code>.}}<br>


If the system is custom built, then there are several applications to assist with driver updates. These will usually scan the system and list hardware that are using outdated drivers for free. Downloading them usually requires the paid versions, but users can take the list and manually download them individually from the web.<br>
{{Alert|type=mo|text='''Note on MO version tracking'''
: {{fc|warning|It's not recommended to allow this program to update your display drivers. This is best done manually by downloading them directly from AMD or Nvidia.}}'''
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.}}


{{alert small‏‎|type=notice|text=Never use beta drivers for a system used for mod testing!}}
== Update Drivers ==


=== Video Card Setup ===
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.
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).


==== 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 'flash'.
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.
* [https://www.intel.com/content/www/us/en/download/18002/intel-driver-support-assistant.html '''Intel Driver Updates''']
*: Intel also provides a means to [https://www.intel.com/content/www/us/en/support/articles/000032252/software/software-applications.html update unsupported drivers].
* [https://www.amd.com/en/support '''AMD Driver Updates''']


{{Spoiler|shown=Click here to show instructions|hidden=&nbsp;
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 - "Clean Upgrade" 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|'''Example Settings'''}}]] - reference only to eliminate stutter or other glitches with AMD Adrenalin-powered systems.
== Display Configuration ==
Keep in mind that hardware and software vary wildly by end user, and there are many configuration possibilities that work for any given subset, but results will still vary.


== Overlays ==
'''Important Considerations:'''
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.
# It's recommended that driver software enhancements (e.g., anitialiasing, image sharpening, multisampling, etc.) be disabled or "off, unless application specifies". Otherwise, the relevant driver software options will be addressed later in the guide.
# TES games don't natively support HDR, so disabling monitor HDR and Windows HDR is recommended.
# The monitor's on-board configuration settings can impact the game. A warm or color-neutral standard preset is recommended.


=== Discord ===
=== Monitor Calibration ===
To disable the overlay in Discord:
Color calibration is critical to photographers and graphic artists who work across media types, but it's also equally important for gaming. Nevertheless, all monitors vary in terms of color range/accuracy and brightness/contrast quality.
{{Spoiler|shown=Click here to show instructions|hidden=<br>
# Run Discord and open the User Settings (gear icon next to username).
# In the left navigation under ''Activity Settings'', click '''Game Overlay'''.
# Toggle off '''Enable in-game overlay'''.
#* {{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.}}
# Still under ''Activity Settings'', now click '''Activity Status'''.
# 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.
#* {{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 ===
There are three places to configure color saturation, temperature, brightness, contrast, gamma, etc.:
To disable the overlay in GeForce Experience:
# The monitor's on-board configuration
{{Spoiler|shown=Click here to show instructions|hidden=<br>
# Windows ''Display Settings'' and ''Color Management''  
# Open the GeForce Experience application.
# The graphics software configuration utility
# Click the Settings icon (gear) at the top.
# Mid-way down the Setting page toggle '''IN-GAME OVERLAY''' off.
# Close the window.}}


=== Steam ===
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.
To disable the Steam overlay for Skyrim Special Edition:
{{Spoiler|shown=Click here to show instructions|hidden=<br>
# Open Steam
# 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.
{{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:
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.
# Load Steam.
# On the toolbar click '''Steam'''.
# On the dropdown menu click '''Settings'''.
# On the new window, uncheck the '''Enabled the Steam overlay while in-game''' box then click '''OK'''.}}


=== Xbox Apps & Game Bar ===
Additional calibration images can be found here: [http://www.lagom.nl/lcd-test/ http://www.lagom.nl/lcd-test/]
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!}}


{{Spoiler|shown=Click here to show instructions|hidden=<br>
== Disabling Overlays ==
# On the task bar, search ''PowerShell''.
# Right-click on ''Windows PowerShell'' from the search and select, '''Run as administrator'''.
# Copy and paste the following, then hit '''Enter''' to list the xbox packages installled:
#: <code><nowiki>dism /Online /Get-ProvisionedAppxPackages | Select-String PackageName | Select-String xbox</nowiki></code>
# If packages are found, use the following to remove them:
#: <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>
# Now rerun the code from step 3 to verify no packages are listed.
# Users should restart their PC.}}
{{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 ==
Certain programs (e.g., ENBSeries) don't work properly when other program overlays are active. Consider disabling all conflicting or unnecessary overlays commonly found on modern Windows PCs.
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.
{{CollapsibleTable
 
| row = 1
'''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".
| type = Overlays
 
| caption = Disable Overlays
There are three places to configure color saturation, temperature, brightness, contrast, gamma, etc:
| heading = 4
# The monitor's built-in configuration menu
| title = Disable the Discord Overlay
# Windows color management
| text = # Run Discord and open Settings (gear icon next to username).
# The driver configuration utility
# In the left navigation under '''''Activity Settings''''', tick {{Ui|Game Overlay}}.
 
# ''Un''tick {{Ui|Enable in-game overlay}}.
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.
#* To enable in some games but not others, leave this setting ticked, and ...
* 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.
#*# Still under '''''Activity Settings''''', click {{Ui|Activity Status}}.
* 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.
#*#* Ensure the monitor icon is toggled off (red) for each game for which the overlay should be disabled.
* 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.
# Close the window.
** '''AMD-CCC:''' |Desktop Management| > |Desktop Color| (click "Reactivate AMD color controls").
#: Also see [https://support.discordapp.com/hc/en-us/articles/217659737-Games-Overlay-101 Discord's official documentation].}}
** '''Nvidia Control Panel:''' Access from the Windows Control Panel. |Display| > |Adjust desktop color settings|
{{CollapsibleTable
| row = 2
| type = Overlays
| title = Disable the GeForce Experience Overlay
| text = # Open the GeForce Experience application.
# Click the Settings icon (gear) at the top.
# Midway down the page, ''Un''toggle '''IN-GAME OVERLAY'''.
# Close the window.}}
{{CollapsibleTable
| row = final
| type = Overlays
| title = Disable the Steam Overlay
| text = # Open Steam, and click on the ''LIBRARY'' tab at top.
# In the game list, right-click on '''''The Elder Scrolls V: Skyrim Special Edition'''''
# Select '''''Properties'''''.
# ''Un''tick {{Ui|Enable the Steam Overlay while in-game}}
# Close the window.
To disable the Steam overlay for ALL games:
# Open Steam, and click on  '''Steam''' in the toolbar.
# On the dropdown menu click '''Settings'''.
# In the pop-up, ''Un''tick {{Ui|Enabled the Steam overlay while in-game}}, and click {{Ui|OK}}.}}

Latest revision as of 02:45, September 11, 2024

Delta c.png

System Setup Guide (SSG)

A Mandatory Prerequisite for Following Step Game Guides

by: The Step Team  | Forum Topic

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

After completing the SSG, return to the Game Guide using the top navigation bar.

Modding Folders

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 / 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

It's recommended to unhide file-type extensions to simplify asset identification.

➕ [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

As is mentioned throughout this guide, Step only supports Steam games at this time. 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).

Game Installation & Maintenance Via Steam

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

Consider Moving Steam and Installed Games

Since Steam is 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 move Steam games or Steam itself into a custom location.

Installing a Steam Game

Games are downloaded and installed under the Steam directory location ..\Steam\steamapps\common\ using the Steam application.

➕ [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.

Initialize the Game

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.

Restoring the Default (Vanilla) Game Folder

If the game has been previously installed and modded, there are likely third-party files under the Steam game directory location. Depending on the methods and tools used, some of these files could cause problems later. Additionally, Step guides always expect the most current Steam game release. Restoring the default Steam (vanilla) game installation is highly recommended and ensures there are no hangups later.

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

Delete Game Files and User Data

➕ [Click to show]➖ [Click to hide] Steps - Part 1: 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

➕ [Click to show]➖ [Click to hide] Steps - Part 2: Reacquire Game Files
  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.

Disabling Steam Automatic Updates(optional)

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(optional)

Some mod management applications manipulate the physical game files in the Steam game directory location: ..\Steam\steamapps\common\. MO instead uses a virtual game directory location, preserving all of the vanilla game files. Even so, some engine-level runtime mods (e.g., post-processors, script extenders, etc.) require their EXE and DLL files to be installed in the physical game directory location. Some may wish to create a backup of the vanilla game before any changes under the game location take place. 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> )

Tools Installation and Setup

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". These are general applications used for more than just modding and should NOT be installed under the ..\Modding\Tools\ location:

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 ..\Modding\Tools\ location created previously.

Mod Organizer(Forum)

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. Vortex users can easily switch to MO without losing downloaded or installed mods by moving some files around using Windows Explorer. Then each download/mod's metadata can be synced,

  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)

  1. Download BethINI:
  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, merge the updated archive content into existing files/folders with overwrite.

LOOT(Forum)

  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)

'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)

  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

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 out of scope.

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.

First, launch MO by running its executable (e.g. ..\Modding\Tools\Mod Organizer\ModOrganizer.exe). If this is the first time MO is started after installation, the "Creating a new instance" wizard will be presented. If this is NOT the first time launching MO, click on the MOInstanceManager.png icon, and then click [+ Create new instance] in the upper left of the instances windows to start the wizard.

Create a global instance Click to show/hide
Click [Next], and select "Create a global instance", and click [Next] again.

MOSetup02.PNG
Select the game Click to show/hide

MO will detect games that are installed. Select any one of the games listed and click [Next]. If the game wasn't auto-detected, manually browse to the game directory.

  • Select the Steam game edition if prompted. Step guides only support Steam games. Other editions can be used but aren't supported by Step guide curators.

MOSetup03.PNG
Name the instance Click to show/hide

Type a name, or use the default, and click [Next].

  • Step recommends using the guide name and version number as the instance name (e.g. Step SkyrimSE v#.#), which makes it possible to completely partition game-specific builds. MO profiles do not allow this degree of separation. See Instances vs Profiles for more information.
  • If prompted to "Configure profile settings", tick all boxes before clicking [Next].

MOSetup05.PNG
Set the instance location Click to show/hide
Use the default path (recommended), or choose a custom path, and click [Next].

MOSetup06.PNG
Connect to Nexus (only appears on first launch) Click to show/hide

Click 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.

MOSetup08.PNG
Authorize Nexus Click to show/hide

If successful, a browser window will open Nexus Mods. Log in, and click the [Authorise] button to allow the connection.

  • The browser page should present a 'success' message. Close the window, and click [Next]

MOSetup09.PNG
Create the instance Click to show/hide

Click [Finish] after the confirmation message appears.

  • A tutorial prompt may appear, which is recommended for those new to MO.
  • Another prompt will appear if MO is not set up to handle .NXM links. Select [Yes].

MOSetup12.PNG


MO is now ready to use. 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.

Update Drivers

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 'flash'.

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 - "Clean Upgrade" 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.

Display Configuration

Keep in mind that hardware and software vary wildly by end user, and there are many configuration possibilities that work for any given subset, but results will still vary.

Important Considerations:

  1. It's recommended that driver software enhancements (e.g., anitialiasing, image sharpening, multisampling, etc.) be disabled or "off, unless application specifies". Otherwise, the relevant driver software options will be addressed later in the guide.
  2. TES games don't natively support HDR, so disabling monitor HDR and Windows HDR is recommended.
  3. The monitor's on-board configuration settings can impact the game. A warm or color-neutral standard preset is recommended.

Monitor Calibration

Color calibration is critical to photographers and graphic artists who work across media types, but it's also equally important for gaming. Nevertheless, all monitors vary in terms of color range/accuracy and brightness/contrast quality.

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

  1. The monitor's on-board configuration
  2. Windows Display Settings and Color Management
  3. The graphics software 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/

Disabling Overlays

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

Disable Overlays
Disable the Discord Overlay Click to show/hide
  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.
Disable the GeForce Experience Overlay Click to show/hide
  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.
Disable the Steam Overlay Click to show/hide
  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].
Retrieved from "https://stepmodifications.org/wiki/index.php?title=Guide:System_Setup_Guide&oldid=190228"