User:Darth mathias/SRLE Extended Legacy of The Dragonborn Prerequisites
FORUMS: If you want to check SRLE Extended: Legacy of The Dragonborn forums click Here HISTORY: You can check on revisions of this Prerequisite page by clicking Here MAIN GUIDE: Click here to go to the main guide -> SRLE LOTD
Official Bethesda Content
The Steam Overlay is known to cause issues while playing Skyrim it is advised to disable it; to do this perform the following:
- Load Steam.
- In the Tool bar at the top of the left hand side Click Steam.
- In the Dropdown menu Click Settings.
- Then in the popup box find where it says In-Game.
- Uncheck Enabled the Steam overlay while in-game then click OK.
Alternatively if you would just like to disable this for Skyrim you may:
- Load Steam.
- Click LIBRARY.
- On your Games list look for The Elder Scrolls V: Skyrim and Right Click.
- In the Dropdown menu Click Properties.
- Then in the popup box Uncheck Enable the Steam Overlay while in-game.
Before we can actually start doing any modding, We'll set Skyrim up first and set a starting base.
Start by opening Steam: then perform the following steps in order:
Start The Elder Scrolls V: Skyrim through the Steam context menu to open the default Skyrim launcher.
- Click "Options".
- Click the [Ultra] push-button.
- Set "Aspect Ratio" and "Resolution" through the drop down box. Set these to the monitors optimal resolution.
- Set "Antialiasing Level" to Off through the drop down box. This is in preparation for the ENB Install.
- Set "Anisotropic Filtering" to Off through the drop down box. This is in preparation for the ENB Install.
- Click the [OK] button to close and save.
We've just set Skyrim up to a base to work on. We'll tweak this when we run the BethINI tool later in the guide.
Configure The Creation Kit
The Creation Kit is a valuable tool for Skyrim as it allows users to create and/or edit mods. It can be used to fix and change things not possible with the other 3rd party tools. Similar to Skyrim, the Creation Kit does not have default ini files until it is started for the first time and requires some basic setup to work properly for the purpose of this guide.
- Download the Creation Kit via Steam
- Start the Creation Kit through the Steam context menu.
- Once the Creation Kit is loaded, exit the program.
- Navigate to the Skyrim folder (where CreationKit.exe is located) and open SkyrimEditor.ini.
- At the bottom of the [General] section, add the line "bAllowMultipleMasterLoads=1".
- Locate the line starting with "SArchiveList=" and after Update.bsa add ", Dawnguard.bsa, Hearthfires.bsa, Dragonborn.bsa".
- Locate the line starting with "SResourceArchiveList2=" and after Update.bsa add ", Dawnguard.bsa, Hearthfires.bsa, Dragonborn.bsa".
- Save and close the file.
These settings will remain set for each subsequent run. These settings have accomplished the following:
* Setup the ini files for multiple master loads and to properly load DLC content.
Extract Dialogue Views and Script Source
With the latest Creation Kit version, Skyrim dialogue views and script sources are no longer extracted in the games data folder by default. To fix this, perform the following:
* Open Scripts.rar found in the Skyrim/Data folder and extract all files in place. (IE to the Skyrim/Data folder)
Papyrus Compiler Fix For 64-bit Systems
The following fix is only required for user with a 64-bit operating system. The PapyrusCompiler.exe used by the Creation Kit is compiled as an "AnyCPU" executable which means that it can be run in both 64-bit and 32 bit modes depending on the users OS. However, Mod Organizer is exclusively written in 32-bit and cannot hook into 64-bit applications. Due to this, compiling Papyrus scripts in the Creation Kit will fail. Fortunately, there is a workaround to force the compiler to always run in 32-bit mode.
Download this tool and place it in the Skyrim/Papyrus Compiler folder. Run the executable and click [Start].
[Skyrim Script Extender]
Install only these files to the main Skyrim folder at this time:
SKSE is absolutely essential. It extends the scripting capacity of the game to allow mods to do things that would not normally be doable in the base Skyrim Engine. Many Mods depend upon it.
[SKSE Plugin Preloader]
Download the archive manually. Install only the following files to the main Skyrim folder:
This is a little extender to help the Crash Fixes mod work.
NOTE: Download whichever file matches your system. I use the 64 bit exe file. The function of this tool is to open archives manually. It handles most modern compression schemes and is free to use. This is optional as there's other file archiving options around and if you already have one you prefer, feel free to use it.
[Champollion PEX to papyrus Decompiler]
Download the archive manually and extract the folder contained within to the Skyrim directory. The function of this tool is to decompile pex scripts to source code. This is a prerequisite for Merge Plugins Standalone.
This tool helps optimize and re-mip textures. This will ultimately save you disk space and help load times. The program is portable and can be installed anywhere. You can check the basic how tos for the program here: http://wiki.step-project.com/Guide:DDSopt/Skyrim
LOOT does a few things. As the name suggests it helps optimize your load order so things are loaded in correct order. However it also tells you which mods need cleaning, and suggests Bash Tags. More on cleaning and Bash Tags later.
Download the archive manually. Extract the whole contents of the archive to a folder. Name the folder 'Merge Plugins' or similar. I suggest putting it somewhere easy to find. This tool allows us to merge mod plugins into a single file. This is needed as Skyrim has a hard limit of 255 total mod plugins. Try and load more and the ones after 255 will get ignored. This may crash your game. Using this we can bring plugins down to a manageable level.
Download the installer file and run it. When running the installer, I usually install it in my Skyrim directory and place a shortcut on the desktop. Others have a discrete folder for all their modding tools.
In the installer, check "Handle NXM Links". This allows direct downloading of mods using the "Download With Manager" button on Nexus mod pages. The function of this tool is to manage mods and is the mod manager of choice for this guide. The reasons for this are listed below:
* Profiles allow multiple configurations set up per character and/or playthrough. * Mod Downloads via NXM allows downloading of mods directly using the "Download With Manager" button on the Nexus site. * Mod Version Tracking uses the power of the Nexus site to track major mod updates. However, this is not a replacement for the track file option on the actual Nexus site for optional downloads! * BAIN Installer Compatibility allows the use of BAIN packages. * NMM Installer Compatibility allows the use of Nexus Mod Manager installers. * Manual Installation Option allows modification and selection of the data folder in an archive manually, allowing fixes of path problems at install time. * Virtual File System allows a clean base Skyrim installation without the mess of moving files. Additionally extends this file system to other tools such as LOOT, TES5Edit, and Wrye Bash.
This is the tool we'll actually be using to download, install and manage the mods. Don't worry if it looks daunting, we'll set you right shortly.
|Notice: If you wish to use Mod Organizer 2, you can, but it takes slightly different setup procedures. These will be added shortly.|
The function of this tool is to remove Identical To Master(ITM) records, Undelete Deleted Records(UDR), and clean dirty edits as specified by the guide the ESMs and ESPs that Skyrim will be loading.
The function of this tool is to manage mods and create Bashed Patches. Bashed Patches merge the leveled lists from the installed mods and has some limited functionality to merge mods and tweak game values. For the purposes of this guide, only the Bashed Patch functionality will be used. Download the file manually and install to the 'Mopy' directory is in the Skyrim directory.
Mod Notes: this little tool to allow us to merge mods with scripts - it takes the merge maps that are produced when you merge something, grabs all the scripts and LODGen files from you active mod list (BSAs included) and replaces the old plugin name and formIDs with the new plugin name and formIDs.
[MXPF - Mator's xEdit Patching Framework]
Mod notes: This mod add a framework to xEdit that other scripts can use.
Special installation: Download MANUALLY and install into Edit scripts folder in TES5Edit.
[Khajiit Ears Show - With UNIVERSAL Mod Support]
Mod notes: This mod is an xEdit Script that will allow Khajiits to show their ears while wearing helmets.
Special installation: Download MANUALLY and install into Edit scripts folder in TES5Edit.
Mod Notes: This is small scripts to remove land edits from a mod.
Special installation: Extract to TES5Edit\Edit Scripts. Then go to TES5Edit\Edit Scripts\lib from there copy mteFunctions.pas to the main Edit Scripts folder
[The Great Equalizer - Patching Script]
Mod notes: This mod is an xEdit Script that will help balance all weapons and armour (even modded ones) in the game.
Special installation: Download MANUALLY and install into Edit scripts folder in TES5Edit.
[No More Dragon LODs]
Mod notes: Skyrim, like most games, only renders the immediate area in high quality. If you're exploring, you may notice that the grass doesn't cover everything that you can see, or that there's an area in a valley below the mountain top you're sitting on where the ground looks blocky and just generally bad. That happens because the edge of the draw distance (uGridsToLoad) has been reached and objects past that use a lower quality texture and/or model to keep performance nice.
Dragons, for some reason, have LOD textures and models. At a very far distance these may look fine or even indistinguishable from their high quality ones, but if you're fighting a dragon at the right distance, you're going to notice him popping back and forth from bad quality to good quality.
This mod is an xEdit script that fixes that.
Special installation: Download MANUALLY and install into Edit scripts folder in TES5Edit.
Configure Mod Organizer
- Start Mod Organizer.
- If this is the first run, Mod Organizer will prompt to select which game to manage, select Skyrim.
- Mod Organizer will then prompt to show a tutorial. It is highly recommended to click [Yes] if not familiar with the tool.
- Click the [Configure Profiles] button at the top of the window. The icon looks like an id card.
- Verify "Automatic Archive Invalidation" and "Local Savegames" are unchecked.
- Click [Create] and type "Vanilla Skyrim" in the text box.
- Verify that "Default Game Settings" is unchecked then click [OK]. The "Vanilla Skyrim" profile will appear in the list.
- Select the "Default" profile and click [Remove]. Select [Yes] when prompted.
- Close the dialogue by clicking [Close].
- Verify that "Vanilla Skyrim" is the currently selected profile in the "Profile" drop-down above the left-pane of the Mod Organizer window.
- Click the [Settings] button at the top of the main Mod Organizer window. The icon looks like a screwdriver and wrench.
- In the "Settings" dialogue, click the [General] tab and in the "Style" drop down select "Dark.qss".
- In the "Settings" dialogue, click the [Nexus] tab.
- Check "Automatically Log-In to Nexus" and input a valid nexus username and password.
- In the Steam tab input a valid Steam login and password.
- In the "Settings" dialogue, click the [Plugins] tab.
- Select "Basic Diagnosis Plugin" in the left pane.
- In the right pane, double click on the value to the right of "check_modorder" and select "false".
- Select "BSA Extractor" in the left pane.
- In the right pane, double click the value to the right of "enabled" and select "true".
- In the "Settings" dialogue, click the [Workarounds] tab.
- Verify that NMM Version is at least 0.63.0, if it is not then update it to this value.
- Close the window by clicking [OK].
- Click the [Executables] button at the top of the main Mod Organizer window. The icon looks like a pair of cogs.
- In the "Title" text box type "TES5Edit". (Or whatever you renamed FO4Edit.exe to as part of the Tools installation)
- In the "Binary" text box type <TES5Edit Path>\TES5Edit.exe or select it using windows explorer by pressing the [...] button.
- Do not select any of the optional check boxes.
- Click the [Add] button. TES5Edit should appear in the list.
- Repeat this process for both Merge Plugins and Wrye Bash replacing the appropriate fields then close the dialogue by clicking [OK].
Next we'll fix the default left pane order, which is scrambled from how it should look. Drag and drop the files in the left pane until they look like this:
* Dawnguard * HearthFires * Dragonborn * HRDLC1 * HRDLC2 * HRDLC3
We'll now run LOOT to organize the right pane so it depicts the correct order also. Perform the following steps:
- Select LOOT from the drop down list of executables.
- Click the [Run] button
- Towards the top right hand corner is an icon that looks like 3 horizontal lines. Mousing over it shows it's for 'Sort Plugins'. Click it.
- LOOT will now download any updates to it's masterlist file and compare the files it sees to this masterlist file.
- The calculated load order is then displayed. Click 'Apply' to accept this order. If no changes are necessary there may not be an 'Apply' option as no changes are needed.
- Close Loot using the Red X.
This process has loaded LOOT via Mod Organizer. This enables LOOT to act upon any and all of the .ESM and .ESP files in Mod Organizer's virtual file system. It compares what files it sees to the Master-List of all .ESM and .ESP files and suggests tweaks as required. Some files need to load before others or after others for their effects to be fully noticeable. LOOT helps this to happen. If you look at the Right pane of Mod Organizer now, you should notice that the files are in the same order that you just sorted them into on the Left pane, with Skyrim.esm and Update.esm above them. This is the correct formation.
You should also notice that the three files for the HighResTexturePack01,02 and 03 are in italics with what looks like a small brush icon beside them. This icon suggests they are currently empty files. Untick them in the Right pane now.
This process has enabled the Dawnguard, Hearthfires, and Dragonborn DLCs for use in the game. The High Resolution DLC are not currently enabled. A powerful feature of Mod Organizer is that it can load and manage BSA files without their corresponding ESP files by use of the "Archives" tab in the right pane. To enable the HRDLC without their corresponding ESPs active, perform the following:
* Open the "Archives" tab in the right pane of Mod Organizer. * Verify the box adjacent to "Have MO manage archives" is checked. * Verify the boxes adjacent to HighResTexturePack01.bsa, HighResTexturePack02.bsa, and HighResTexturePack03.bsa are checked.
Create The SRLE Extended LOTD Profile
We've made a Vanilla Skyrim profile. This means you can play vanilla unmodded Skyrim via Mod Organizer at a single mouse click. Now we'll make the profile with which we'll mod Skyrim. This is how we proceed:
* Click the [Configure Profiles] icon at the top of the main Mod Organizer window. The icon looks like an id card. * Select "Vanilla Skyrim" then click [Copy]. * Type "SRLE Extended LOTD" in the text box and hit [OK].
A couple of points to be made here: Firstly, when you make a new profile, Mod Organizer makes new copies of Skyrim.ini and SkyrimPrefs.ini. If and when you make ini files changes, you will be making them to THESE files. Secondly, we installed the base three files of Skyrim Script Extender (SKSE) earlier, but didn't install the script files. We will do this now to show how to install a mod via Mod Organizer. Ensure you have your newly made profile active and then perform the following steps:
* Click the small screwdriver and wrench icon adjacent to the "Profile" drop-down and select "Install Mod...". * Navigate to the downloaded SKSE archive and click [Open]. * Replace the default text, if any, in the "Name" text box with "Skyrim Script Extender". This is the name that will be displayed in the left pane post-installation. * In the file tree, navigate to the "Data" folder inside the archive, right-click and select "Set Data Directory". Only the Scripts folder should be visible and checked. * Click [OK].
The mod will now be displayed with an empty check box in the mod window. This mod is now installed but not yet enabled for use by the game. Also, note that Mod Organizer does not have a version number or category set for this mod. To resolve this, perform the following:
* Right-click the mod and select "Information...". (Alternatively, double click the mod name.) * In the "Categories" tab, check the box next to "Patches" to add that category to this mod. * In the "Nexus Info" tab, set the version number to the installed SKSE version number but set the Mod ID to -1.
This has set the proper version number and category for this mod. The color of the text also indicates that SKSE is not available on the Nexus. Look at the [File Tree] tab to see the contents of the folder that will be virtually placed inside the Skyrim/Data folder. Note the meta.ini file is shown which Mod Organizer uses to store all the related data for the mod and it will not be visible to the game when executed.
* Click [Close] to save and exit the window.
Mods version numbers that can be verified by the Nexus will be either Green(Current+) or Red(Out Of Date). To make the mod visible to the game:
* Check the box adjacent to the mod name.
The files located inside this mod folder will now be visible to any programs executed through Mod Organizer as if they were placed inside of the Skyrim/Data folder. Any conflicts are handled by Mod Organizer in priority order (higher priority overwrites lower priority). Give this a try now:
* Select "SKSE" in the drop down above the right pane then click [Run].
This will execute the game through Mod Organizer using the SKSE_Loader.exe. The Mod Organizer window will close as SKSE is automatically configured to do so. At this point, SKSE is now properly installed with all included script functionality. There is also a way to check you have SKSE loaded and working:
* When the game loads to the menu, open the console. This is usually one by pressing the key directly above the [Tab] key. It's often the ` or ~ key. This will open a small command prompt in the lower left corner. It may be hard to see but it should be there. Type the command "getskseversion" without the quotes. It should give output as to the version you have installed. If it's anything other than 1.7.3 then recheck the original SKSE install and the scripts install just performed.
Exit the game, and if needed ensure SKSE is correct again after checking install. Do not continue until you're sure SKSE is correctly installed.
We've now set up the profile we wish to install mods to. We've also set up a Vanilla Profile. Either a modded game or the vanilla game can be played just by changing the profile. Additionally, should you wish to make any other profile, you can simply copy that Vanilla Skyrim profile, rename it and start with that new profile.
Clean the Bethesda ESM's
With profiles now set up properly, it is time to begin modding some vanilla game files. To increase stability, TES5Edit will be used to clean ITMs and UDRs from Bethesda 's ESMs. This improves compatibility between the various DLCs and lessens the chance of instability in Skyrim. Perform the following:
* Start Mod Organizer. * Select "TES5Edit" from the drop down above the right pane and click [Run]. * Right-click inside the file listing and select "None". * Check the box adjacent to Update.esm and click [OK]. Wait for the message "Background Loader: finished" to appear in the right pane. * Right-click Update.esm and select "Apply Filter For Cleaning". Wait for the message "[Filtering Done]" to appear in the right pane. * Right-click Update.esm and select "Remove Identical To Master Records". Wait for the message "[Removing Identical to Master records done]". * Right-click Update.esm and select "Undelete and Disable References". Wait for the message "[Undeleting and Disabling References done]". * Click the [X] on the title bar to close TES5Edit. * Verify the box adjacent to Update.esm is checked and also that "Backup Plugins" is checked then click [OK].
Update.esm has now been cleaned, meaning that any improperly removed records or edited records that were identical to the base Skyrim.esm file have been fixed. Repeat the process above for all of the DLC ESMs in order selecting only one at a time. Do NOT attempt to clean Skyrim.esm itself.
Dawnguard.esm must also be cleaned twice to remove all duplicate records. When you clean Dawnguard.esm the first time, check "Backup Plugins". Do not check it the second time.
Manual TES5Edit Cleaning For Dawnguard.esm Also Required:
Open TES5Edit and load only Dawnguard.esm Once loaded Left click and open CELL > Block 5 > Sub-Block 3 > select 00016BCF. Scroll down the view window on the right to find XEZN subrecord referring to RiftenRatwayZone [ECZN:0009FBB9]. Right click and select Remove. Next Left click and open CELL > Block 2 > Sub-Block 1 > select 0001FA4C. Right click and select Remove. Last Left click and open CELL > Block 8 > Sub-Block 1. Right click and select Remove. Click the [X] in the upper right hand corner, uncheck "Backup plugins", and click [OK].
Originally, when a file was cleaned through TES5Edit using Mod Organizer it was automatically moved back to it's original mod folder and any generated files were moved to <Mod Organizer Path>/overwrite. However, it is now very likely the cleaned files and the backups will now both end up in <Mod Organizer path>/overwrite. The cleaned files will be in the overwrite directory while the backups will be in a folder called TES5Edit Backups inside the overwrite directory. The cleaned files should be moved to their own mod folder to preserve a clean Skyrim/Data folder and the backups restored from the TES5Edit Backup folder in overwrite. To resolve this problem, perform the following:
* Close Mod Organizer. * Navigate to Skyrim/Data and move the newly cleaned Bethesda ESM files to <Mod Organizer Path>/Mods/Cleaned Vanilla ESMs. * Navigate to <Mod Organizer Path>/overwrite/TES5Edit Backups and move all of the backup files to the Skyrim/Data folder. * Rename the .backup* files to their original name such as Update.esm, Dawnguard.esm and so on. * Remove the TES5Edit Backups folder from <Mod Organizer Path>/overwrite.
This preserves an absolutely clean Skyrim/Data directory and also allows our modded profile to run with the modified, cleaned vanilla ESM files. To finish up the cleaning, perform the following:
* Start Mod Organizer. * Verify SRLE Extended LOTD is the currently selected profile. * Drag the newly created mod "Cleaned Vanilla ESMs" between the "HighResTexturePack03" and "Skyrim Script Extender" mods in the left pane and activate it by checking the box.
To recap the current set up:
* Running Skyrim through Steam results in a completely vanilla experience. * Running the "Vanilla Skyrim" profile through Mod Organizer with "Skyrim" selected in the drop-down results in a completely vanilla experience. * Running the "Skyrim Revisited" profile through Mod Organizer with "SKSE" selected in the drop-down results in a SKSE enabled experience using the cleaned base ESM files.
So, now to start your modified game, always start Mod Organizer, select SKSE and press [RUN].
This program was created by DoubleYou (The S.T.E.P. resident INI Master). BethINI (pronounced "Bethany") is an attempt to restore decency to the INI configuration files for games created by Bethesda.
- Run BethINI.exe Outside of MO and make sure it is closed otherwise changes wont take effect
- Mod Organizer users should go to the Setup tab within BethINI and select the profile they wish to use via the INI Path setting. Your profiles should be autodetected.
- Under the Basic tab Click the DEFAULT BUTTON. This will refresh your INI files to the default settings for your system, with minimal tweaks.
- Under the Basic tab Click the HIGH PRESET.
- Under the Basic tab Make sure the BethINI PRESET is checked.
- Under the Basic tab Make sure the Recommended Tweaks is checked.
- Under the Basic Tab make sure Windowed Mode is CHECKED (THIS IS ONLY NEEDED IF USING ONE TWEAK)
- Under the Basic tab make sure Anisotropic Filtering is set to NONE.
- Under the Basic tab make sure ENB MODE is CHECKED
- Under the General tab make sure Intro Logos is UNCHECKED.
- Under the General tab make sure Disable Tutorials is CHECKED.
- Under the General Tab Make sure Post-Load Update Time is 2000.
- Under the Gameplay Tab Make sure 1st Person Arrow Tilt-up Angle is 0.7.
- Under the Gameplay Tab Make sure 3rd Person Arrow Tilt-up Angle is 0.7.
- Under the Gameplay Tab Make sure 1st Person Bolt Tilt-up Angle is 0.7.
- Under the Interface Tab Make sure Mouse Settings -> Lock Sensitivity is 0.0125.
- Under the Detail Tab make sure Field of View is set to 85.00.
- Under the Detail Tab make sure Particles is set to 6000.
- Under the Detail Tab make sure Reflect Sky is CHECKED.
- Under the Detail Tab make sure Shadow Resolution is set to 2048.
- Under the Detail Tab make sure Sun-Shadow Update Time is set to 0.
- Under the Detail Tab make sure Sun-Shadow Update Threshold is set to 2.0.
- Under the View Distance Tab make sure Grass Fade is set to 18000.
- Under the Visuals Tab make sure Grass Density is set to 60.
- Under the Visuals Tab make sure Grass Diversity is set to 15.
- Under the Basic Tab Click the Save and Exit button.
Post BethINI Tweaks
The first step to editing the SKSE.ini is to create it. Perform the following:
* Right-click Skyrim Script Extender in the Mod Organizer mod list. * Select "Open In Explorer". * Create and enter a folder named SKSE. * Create and open a text file named SKSE.ini.
Once this file is open to be edited, paste in the following:
[General] ClearInvalidRegistrations=1 [Display] iTintTextureResolution=2048
This enables self-healing of rogue updating scripts in saves.
Save and close SKSE.ini then exit explorer.
bGrassPointLighting=1 iMaxGrassTypesPerTexure=15 (make sure you have this.) iMinGrassSize=60 (make sure you have this.)
fInteriorShadowDistance=3000 (Make sure is this the value) fShadowLODStartFade=400.0000 (Change existing value)
b30GrassVS=0 fGrassMaxStartFadeDistance=18000 (Make sure is this the value)
bSaveOnPause=0 (Change existing value) bSaveOnRest=0 (Change existing value) bSaveOnTravel=0 (Change existing value) bSaveOnWait=0 (Change existing value)
Due to the heavily modded nature of this guide it is advised to have auto saves turned off and to create fresh new saves every time and not overwrite old preexisting saves.
SKSE Arguments (For People who do not wish to start Steam to start Skyrim)
THIS IS FOR THOSE WHO DON'T WISH TO USE STEAM TO START SKYRIM
- Click the Gears icon in the top left of Mod Organizer.
- Click on SKSE.
- Add the Following to the Arguments: "-forcesteamloader".
- Click Modify Button.
- Click the Close button.
DirectX End-User Runtimes (For Windows 10 Users)
Windows 10 users need to install the DirectX End-User Runtimes (June 2010) to make sure Windows 10 is compatible with ENB. Older versions of Windows should already have the runtimes installed.
- Download the DirectX End-User Runtimes (June 2010).
- Create a temporary new folder to store the extracted runtimes (for example, "C:\DX9 Runtimes").
- Run the downloaded executable directx_Jun2010_redist.exe to extract the files to the folder you just created.
- Open the folder and run DXSETUP.exe to install the runtimes.
ENB File Installation
- The Download link is down the very bottom of the page.
- When the file has downloaded, open the Wrapper Version folder enclosed in the archive and extract ONLY the files: d3d9.dll, enbhost.exe and enblocal.ini
- Place the d3d9.dll, enbhost.exe and enblocal.ini into the Main Skyrim Directory.
- Once extracted open the enblocal.ini and change the following setting:
Under [MEMORY], set DisableDriverMemoryManager=true if using an AMD based video card. Under [MEMORY], Set ReservedMemorySizeMb=128 (Example) (If stuttering persists, increase the value in increments of 128 ( 256, 384, 512, etc... ) until the stuttering has ceased or is as minimal as possible with the lowest possible value. The maximum value that can be used is 1024.) Under [MEMORY] set, VideoMemorySizeMb=0 Under [MEMORY] set, AutodetectVideoMemorySize=true Under [ENGINE], set EnableVSync=false This is only needed if you plan to run VSync through your Driver. Under [INPUT] set //B KeyBruteForce=0 (This should stop Brute Force Mode from ever accidentally being activated). Under [ANTIALIASING], set EnableEdgeAA=true, This will smooth edges with only a small performance loss. Under [ANTIALIASING], set EnableSubPixelAA=true. This will increase picture quality with almost no performance loss.
Idiot Check: Once this is done change UsePatchSpeedhackWithoutGraphics=false to TRUE and test to see if it is working. If it's working, change it back to FALSE when you have reached and installed the ENB from the Main guide.
Recommended Driver Tweaks
[NVIDIA Profile Inspector]
Through Nividia Inspector Load the Elder Scrolls V: Skyrim default profile then change the Following:
VSync and Refresh:
* Frame Rate Limiter: From the drop down menu select 58 * Max Pre-Rendered Frames: From the drop down menu select 3 * Vsync: From the drop down menu select Force On (this is a personal preference as I prefer the driver handle all Vsync stuff) * Apply Changes.
- If the driver is handling Vsync make sure EnableVSync is set to false in the enblocal.ini file and iPresentInterval is set to 0 in the Skyrim.ini file.
- My game seems more smooth with these setting this may not be the same for you, but remember one rule, you must have Vsync enable somewhere either through the game, your ENB or the driver.
Now we can go again on the main page and start the modding adventure of Skyrim. Start at the "Mod Installation" heading. -> Main Guide Page