Guide:System Setup Guide

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. Please install them to the system's default location:

7-zip

This is a popular file archiver. All mods are archived before uploading and some 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 many features such as syntax highlighting, plugins (including Papyrus), tabs, and many more useful for modding.

WARNING

Step NoManSky Guide: The following modding tools don't apply, please skip ahead to Update Drivers.

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\

BethINI^(Forum)

1. Download BethINI:
   • Check the Release Date at the top of the Step guide of interest (Step guides are also linked in the top nav under Game Guides).
   • For guides released prior to 2024: Download the previous version of BethINI.
   • For guides released in 2024 onward: Download BethINI Pie.
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

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 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.
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.
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].
Set the instance location Click to show/hide
Use the default path (recommended), or choose a custom path, and click [Next].
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.
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]
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].

MO is now ready to use. By default, the MO profile will be created under %LOCALAPPDATA%\ModOrganizer\<instanceName>\profiles\<profileName>.

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

• Intel Driver Updates

  Intel also provides a means to update unsupported drivers.

• AMD Driver Updates

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
Run Discord and open Settings (gear icon next to username). In the left navigation under Activity Settings, tick [Game Overlay]. Untick [Enable in-game overlay]. To enable in some games but not others, leave this setting ticked, and ... 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. Close the window. Also see Discord's official documentation.
Disable the GeForce Experience Overlay Click to show/hide
Open the GeForce Experience application. Click the Settings icon (gear) at the top. Midway down the page, Untoggle IN-GAME OVERLAY. Close the window.
Disable the Steam Overlay Click to show/hide
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. Untick [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, Untick [Enabled the Steam overlay while in-game], and click [OK].