Jump to content
  • entries
    11
  • comments
    335
  • views
    14,259

Conglomerate 01 - Skyrim LE Essentials: Installing Skyrim, Stability Fixes, Tools


donttouchmethere

41,203 views

Conglomerate 01

 

Last Update: 21.11.2021

 

Well, here I go again, turned my Skyrim LE install into a bloody mess and now I have to clean it up.

It happens sometimes for an unknown reason (*cough*user error*cough*) and I always forget what to do.

Maybe this blog entry will help me remember?

 

 

This guide is for Skyrim LE:

 

For Skyrim SE check out this guides:

 

 

Intro:

My blog is pretty basic and should be used as a "quick" reference to prepare Skyrim LE for modding. If you want to learn more about the technical aspects on how the various Stability Fixes for Skyrim work you can start your research from here.

Main goal is to show how to install Skyrim ready to be modded and how to use "Stability Fixes" to keep Skyrim LE stable even with a multitude of installed mods.

In addition you can find here a list of tools needed to keep the game stable and fix issues.

The instructions are written in a way that a user can just work through it from top to bottom (recommend!), for a first install or a reinstall of Skyrim LE.

 

I use Nexus Mod Manager (NMM v0.8+) in combination with Wrye Bash to compensate for the NMM shortcomings, that's why you find a few NMM related hints included in this blog. The stability fixes are the same for use with any Skyrim LE setup unrelated to the used mod manager (MO, MO2, Vortex, Wrye Bash).

 

I mainly post only solutions I tried or use on my own Skyrim setup and that showed practical results. Many of the here posted fixes and tools are the absolute basics and mandatory to create a stable modding environment.

In combination with Conglomerate 02 it is possible to create a lewd base setup that can be trusted to be stable. A stable base setup is needed for troubleshooting, because it is really hard to find mod bugs or conflicts if the base setup creates glitches or worse crash to desktop (CTD).

 

 

Most used abbreviations and technical terms:

Conglomerate - Abbreviations and file types

 

What you find on this blog page:

 

  1. Installing Skyrim LE
    • Installing Skyrim LE
    • Backup and preparations before uninstalling Skyrim
  2. TES5EDIT Quick_Auto_Clean and cleaning Skyrim Master files
    • Controversial, I use it as ritual to appease the machine spirit.
  3. SKSE & SKSE.ini
    • Mandatory Papyrus expansion
    • Memory (Block) Fix
  4. Crash fixes, Crashfixplugin.ini
    • Memory allocator
    • String count fix
    • other fixes
  5. ENBoost & enblocal.ini
    • ENBoost is the standalone memory manager without the graphical effects from ENBSeries
    • Provides Skyrim with more usable memory
  6. BethINI
    • ini configuration tool and tweaks
    • fixes user errors and/or fixes changes from ini manipulating mods
  7. Savegame Tools:
    • FallrimTools
    • NetImmerse Override Cleaner (SKSE Co-Save Cleaner Utility)

 

 

1. Installing Skyrim LE

 

  • Installing Skyrim LE
 

Skyrim download and installation:

 

Before the download choose the right place to install Skyrim:

  • Install Skyrim on a separate drive/partition from the one the Operating System is installed on, or:

    • ⚠️Avoid installing Steam and Skyrim in "C:\Program Files" or "C:\Program Files (x86)" folders since Windows User Account Control [UAC] can prevent writing files by 3rd party programs.

    • Especially NMM suffers if Skyrim is installed in c:\program files.

 

After the download and installation:

After the download and installation process:

  • go to steam games library > choose Skyrim and right click on it > choose: „check local files for errors“ (only once, steam will repair and download the same files over and over)

  • go to steam games library > choose Skyrim and right click on it > choose: „update game only on game start“

 

Starting Skyrim the first time:

  • ⚠️start Skyrim via Launcher (not via SKSE) once to generate skyrim.ini and skyrimpref.ini,

    • you can find the *.ini in Users\<mygames>\skyrim

      • Users\<mygames>\skyrim:  savegames and papyrus logs can be found there too

 

Backup Time:

  • because downloading Skyrim from Steam takes hours and messing up the Skyrim installation is easy to do, its a good idea to make a zip Backup of the whole Skyrim folder: create a zip archive from \Steam\steamapps\common\Skyrim

 

  • Backup and preparations before uninstalling Skyrim
Spoiler

Sometimes it's necessary to reinstall Skyrim from scratch.

 

Usually you could just uninstall Skyrim, delete the leftovers and drop your Skyrim Backup into the old Skyrim folder.

Still this means you have to recreate all those *.ini files again and you will loose your saved character presets and mod MCM settings (*.json).

Also you will have to search for all those stability tool files again.

 

So I was thinking what files I would rescue for a faster Skyrim rebuild:

⚠️RESCUE THOSE FILES BEFORE UNINSTALLING ANY MODS

 

For NMM:

[ > Nexus Mod Manager > mods ]

  • Backup of all mod zip files.

Especially if they got renamed or modified.

Just drop the zips back into your NMM mods folder after moving or reinstalling NMM.

 

 

[ > Nexus Mod Manager > mods > categories ]

  • Categories.xml

I create lots of categories in NMM to keep the Overview.

Just drop the zips back into your NMM mods folder after moving or reinstalling NMM.

 

 

For all:

[ > skyrim ]

  • Screenshots!

Hey, some of them are actually good ?

 

[ > skyrim ]

  • d3d9.dll
  • enbhost.exe
  • enblocal.ini

Save the trouble to download them again and you have a ready to use enblocal.ini for the new Skyrim installation.

 

If you are there already also grab the:

  • d3dx9_42.dll

from the SKSE Plugin Preloader

 

[ > skyrim > data > skse ]

I just copy the whole SKSE folder.

In there you find:

  • Nioverride.ini
  • SKSE.ini
  • Mod *.json files (MCM settings and more)
  • Character Presets
  • HDT settings
  • Crashfix.ini
  • CrashfixPlugin files
  • StorageUtilData

 

[> skyrim > data]

Schlongs of Skyrim saves it's MCM json into the data folder:

  • SOS.json

 

 

After reinstalling Skyrim just grab the files needed from your backup SKSE folder.

⚠️Don't just copy the whole folder over, because some might not be needed for your new setup or might even conflict with newly installed/updated mods (for example DFC v12.x doesn't go well with json created with DFC earlier than v12.x.)

⚠️Some mods can't read a copy-pasted json right away, in that case save the MCM ingame once and exchange the json with the one you used last.

 

 

2. TES5edit and cleaning the Skyrim DLC Master files

 

 

Cleaning the Skyrim DLC Master files with TES5Edit:

 

This part is controversial. I do it every time after reinstalling Skyrim, but you can try also without this step.

Since 2019 TES5Edit comes with a new Mod cleaning feature: "QuickAutoClean"

Either way, it's good to have TES5edit installed and ready to use.

 

Reasons to clean Skyrim files and why TES5Edit is a useful tool:


Master files to be cleaned:

  • update.esm
  • dawnguard.esm
  • hearthfires.esm
  • dragonborn.esm


Cleaning Procedure:

Basically you will have to repeat those steps with each Master file in TES5Edit:

  • start TESVEdit via TES5EditQuickAutoClean.exe
  • choose only one mod ESM and press "ok"
  • TES5Edit's QuickAutoClean will clean the mod automatically, wait till it finishes it's job
  • close TES5Edit and changes will be saved
  • Repeat this procedure for all Master files

 

 

3. SKSE & SKSE.ini

 

 

SKSE & SKSE.ini:

 

What SKSE does:

  • I found this page helpful, because I like explanations that start with: "I can try to simplify this one..." [behippo]
  • Basically SKSE = Skyrim Script Extender, it extends the Papyrus Script with more functions for coders
  • In addition creating a SKSE.ini activates Memory (Block) Fix

 

Where to grab SKSE:

  • grab SKSE from here: SKSE
    • grab the 7zip archive for manual installation

 

Best way to install SKSE:

  • Install SKSE is manually from the 7z archive

 

Manual SKSE installation:

  1. unzip downloaded SKSE file
  2. Copy the following files to Steam\SteamApps\common\skyrim\:
    • skse_1_9_32.dll
    • skse_loader.exe
    • skse_steam_loader.dll
  3. The "src" folder is only useful for programmers, most users can ignore it.
  4. Copy the files from the skse data folder to Data\Scripts\ Skyrim folder. The pex files are needed by all users of SKSE.
  5. If you create mods, copy the psc files in Data\Scripts\Source\ into the Data\Scripts\Source\ folder of your installation. The .psc files are only needed if you have the CreationKit installed and intend to create or compile Papyrus scripts. It doesn't hurt if you copy the psc files over too.

 

Creating a SKSE.ini:

  • Create a SKSE.ini, because SKSE doesn't create one automatically.
  • The SKSE.ini is also activates the Memory Block Fix.
  • SKSE is also essential part of memory management, more details here:  2020 Skyrim LE Stability Guide
  • With a simple SKSE.ini you can already create a more stable Skyrim thanks to better memory management. If you need to provide your setup with more memory then check out the next chapter about ENBoost.

 

  • To create a skse.ini just use any text editor (MS Editor, Notepad++ and others)
  • The SKSE.ini is saved to: skyrim/data/SKSE
  • If the SKSE folder doesn't exist yet, just create one.
  • The SKSE.ini should look like this:

 

[Display]
iTintTextureResolution=2048
[General]
ClearInvalidRegistrations=1
EnableDiagnostics=1
[Memory]
DefaultHeapInitialAllocMB=768       the SKSE memory settings can be fine tuned with the help of Memory Blocks Log
ScrapHeapSizeMB=256
[Debug]
WriteMiniDumps=1

 

 

Alternatively download this ready to use SKSE.ini: skse.ini with folders.7z

 

 

 

4. Crash fixes, Crashfixplugin.ini

 

 

Crash fixes, Crashfixplugin.ini:

 

What Crash fixes does and why you need it:

  • Fixes various issues found here: How to debug CTD
  • Fixes the vanilla Skyrim savegame string limit for more than 65535 strings. With mods installed that rise the string count significantly you will quickly find yourself over the 65k string count limit.
    • You can check your string count via FallrimTools.
    • Crash fixes changes the savegame format to archive this. To be able to still open the save game with a savegame cleaner use FallrimTools
    • More details about FallrimTools can be found on this blog page (?pending).
  • Crash fixes comes also with a memory allocator function
  • For more information about Crash fixes and hints to create a stable Skyrim setup read the Crash fixes page. More details about what Crash fixes does can be found in it's change log (spoiler at the end of the Crash fixes Nexus page)

 

Where to get Crash fixes and it's requirement:

 

What needs to be installed and where:

  • Crash fixes files:
    • CrashFixPlugin.dll

    • CrashFixPlugin.ini

    • CrashFixPlugin_preload.txt

  • This files go to: skyrim/data/SKSE/plugin
    • if the skse/plugin folder doesn't exist yet create one.

 

  • next install the SKSE Plugin Preloader file:  
    • d3dx9_42.dll

  • the file goes into the Skyrim folder

 

Activating Crash fixes memory allocator patch:

  • open Crashfixplugin.ini
    • change this setting from 0 to 1:
      • UseOSAllocator=1
        • If UUNP RaceMenu sliders are used change the following line from 0 to 1:
          • AlignHeapAllocate=1

 

 

 

5. ENBoost & enblocal.ini

 

 

ENBoost & enblocal.ini

 

⚠️ Don't use this Guide to install a full ENB with ENB preset and a specific ENBseries version. ⚠️

 

What is ENBoost:

  • Various quotes about what ENBoost does:
Spoiler
  • Quoted from enbdev.com:
    • ENBoost is patch from ENBSeries which reduce memory usage of the games, so you may install much more modifications without crashes and errors, also it better utilize video memory of modern videocard. ENBoost often included in most recent ENBSeries and can be activated as memory manager in enblocal.ini configuration file.

 

  • Quoted from stepmodifications.org:
    • ENBoost is a memory management feature added to ENBSeries to address the crashes and freezes relating to the well-known system memory (RAM) limit of 32-bit applications. ENBoost is included by default in ENBSeries versions that support it, and can be implemented as a standalone memory manager without the graphical effects from ENBSeries. The effectiveness and performance of ENBoost is determined by a number of factors, such as size of system RAM / VRAM, quality of video card, version of Windows OS, CPU, and even motherboard memory channel speed.

 

  • Quoted from old STEP guide:
    • In order to understand how ENBoost works, it is important to first know how Skyrim manages memory. The main Skyrim game executable, TESV.exe, is a 32-bit Large-Address-Aware (LAA) application. This means that although TESV.exe can only use a maximum of 2GB of system RAM on 32-bit Windows systems, it can access up to about 3.1GB of system RAM (4GB - about 900MB of system resources) on 64-bit systems. To drive the video card in displaying Skyrim's 3D rendered graphics, TESV.exe must store object geometry (the shapes of things in the game) and texture data cached in its memory space, which is then copied to your video card's VRAM to display. The memory limit is not a problem with an unmodded Skyrim because the cached data is dynamically loaded and unloaded to make room for new data as it's needed, and it almost never completely fills up all of TESV.exe's available RAM.
    • However, when mods are added to Skyrim, the memory needed for cached data is significantly increased, and the more mods that are used, especially higher resolution texture mods, the higher the chance that TESV.exe will run out of memory. When this happens, either the program crashes or some objects do not get rendered.
    • ENBoost overcomes this memory limitation by ...
      • using available VRAM on your video card and

      • using system RAM outside of TESV.exe for dynamically allocated cached data.

    • The second method is accomplished by running an executable named enbhost.exe, which adds up to another 4GB of memory available for ENBSeries to manage per instance. The effectiveness and performance of ENBoost is determined by a number of factors, such as size of system RAM / VRAM, quality of video card, version of Windows OS, CPU, and even motherboard memory channel speed. Fortunately, a number of ENBoost user-settings have been added to account for the enormous variety of user's system configurations.

 

  • DTMT's quote:

    • "Cool! More available memory and less CTD"

 

  • Here an easy to follow video that explains the shared functions of ENBoosters and ENCabulators in detail:
Spoiler

 

 

 

Why you want ENBoost:

  • Loosely quoted from 2020 Skyrim LE Stability Guide:
    •  Frees game process memory from texture data and uses system RAM outside of TESV.exe for dynamically allocated cached data.
    • VRAM usage optimized

 

 

Optional - What you might want to install first:

  • DirectX 9 if you haven't already or later if you have issues even you're sure you installed all fixes correctly.

 

 

Preparations to install ENBoost:

  • grab Enboost from here:

  • useful tool for the videomemorysizemb configuration, if you don't use the available memory auto detection:

  • Slothability shows how to configure Enboost with Chopin support:

    • 6:59 ENBoost configuration

    • since the available memory auto-detection works now this is mainly interesting if auto-detect doesn't work for your system

  • More detail information about enblocal.ini settings here: STEP WIKI

 

 

Installing ENBoost files:

  • After downloading the ENBSeries zip, extract it and copy only the following files to the Skyrim folder (from the wrapper version folder!):
    • only install the files needed for ENBoost configuration, the other files in the ENBseries zip are needed only for a full ENB:
      • d3d9.dll

      • enbhost.exe

      • enblocal.ini

 

 

Configuration of the enblocal.ini for ENBoost:
[global]

usepatchspeedhackwithoutgraphics=true

  • CTD after using LAL bed if using ENBoost and set this to false (like you would for an ENB)

usedefferedrendering=false

 

[memory]

expandsystemmemoryx64=false

  • crash fixes will take over this part

reducesystemmemoryusage=true

enablecompression=true

reservedmemorysizemb=128

  • (-256-384-512-640-768-896-1024) pick your poison, start small and rise if there is stuttering in-game

videomemorysizemb=6144

  • check out Slothability's video for how to find the exact settings for your system or set AutodetectVideoMemorySize=true

AutodetectVideoMemorySize=true

  • If set to true ENBoost will automatically detect your available memory and ignores videomemorysizemb=6144
     

[engine]

MaxAnisotropy= 16

  • ⚠️make sure anisotrophic filtering is deactivated in the Skyrim launcher, don't forget to deactivate this function in NIVIDA settings too.

enablevsync=true

 

[antialiasing]

enableEdgeAA=true

 

[fix]

fixaliasedtextures=false

fixtintgamma=false

 

 

Changes in the skyrimpref.ini for ENBoost according to Slothability's Guide:

[display]

bfloatpointrendertarget=1

imultisample=0

imaxanisotropy=0

 

 

 

6. BethINI

 

Spoiler

BethINI

 

What does the tool do:

  • Effects the configuration files: Skyrim.ini and Skyrimpref.ini
  • BethINI optimizes the game for increased graphical fidelity and performance.
  • Repairs configuration files after user error or evil mods
  • Removes unused configuration entries and writes missing ones
  • Optional Tweaks
  • It also makes a backup of your original configuration files

 

Why you want it:

  • Badly configured Skyrim.ini, Skyrimpref.ini can cause CTD, glitches, fps drop
  • BethINI optimizes and repairs your Skyrim.ini and Skyrimpref.ini with just a few clicks

 

Grab it from here:

 

Hint:

  • if you changed manually some configuration entries for good reasons, BethINI might remove those, so you have to re-add them later after BethINI is done.

 

 

 

7. Savegame Tools:

 

  • FallrimTools
Spoiler

FallrimTools

 

What it does:

  • Needed to control your savegame
  • Needed to manipulate your savegame
  • FallrimTools includes ReSaver, which is a powerful savegame editor/cleaner.

 

Why you want it:

  • If Crash fixes changes savegame format you will need ReSaver to open it, because older cleaners like SaveTool won't be able to open it anymore if you go over the vanilla string count limit.
  • To check your save games regularly for errors.
  • Clean your save game from leftovers after uninstalling a mod or for creating a clean save before updating a mod
  • To clean your save from unattached script instances and undefined elements
  • Check for suspended stacks and a too high active script count
  • To see which mods add what to your savegame.
  • LO can be exported with ReSaver as txt to post it in LL comments

 

Grab it from the Nexus:

 

Requirement for FallrimTools:

  • FallrimTools needs Java

 

  • NetImmerse Override Cleaner (SKSE Co-Save Cleaner Utility)

Spoiler

NetImmerse Override Cleaner (SKSE Co-Save Cleaner Utility)

 

What it does (blindly copied):

  • A lightweight utility capable of deleting data from SKSE co-save files, thus decreasing both the sizes of those files and Skyrim save and load times.
  • More details here: NetImmerse Override Cleaner

 

Why you want it:

Every savegame from a modded Skyrim comes with two files:

  • *.ess
    • Main Save
      • you open that one with ReSaver (FallrimTools)
  • *.skse
    • SKSE Co-Save
      • might need cleaning too, that's where SKSE Co-Save cleaner comes into play!

 

  • SKSE Co-Save might grow over time, in worst cases it gets bloated.
  • Big SKSE sizes cause longer save/loading times, in worst cases (bad mod, bad!) it makes the savegame unable to save/load or the stored data can cause glitches ingame.

 

Edited by donttouchmethere

117 Comments


Recommended Comments



You do spoilers here just like on other posts:

 

Spoiler

Otherwise you would have to spend your time saying, "scheiss" rather than getting your blog done.

 

Link to comment
7 minutes ago, Psalam said:

You do spoilers here just like on other posts:

yes, just forgot to have a line below the last spoiler => all spoilers below got pooled to one HUGE spoiler

i guess its best to type it in word before i transfer it to LL

that gives you the chance to look over it before ppl start to suffer ^^

Link to comment
On 9/17/2018 at 12:07 AM, donttouchmethere said:

i guess its best to type it in word before i transfer it to LL

It should suffice to start EVERY SINGLE LL post with 2-3 blank new lines before you start typing anything else at all  :classic_rolleyes:

Link to comment
4 hours ago, worik said:

It should suffice to start EVERY SINGLE LL post with 2-3 blank new lines before you start typing anything else at all

weeh your the right one to ask:

if i copy paste my test from open office or word everything seems to get messed up with blank lines.

1. i copy paste

2. i save the blog

3. LL adds blank lines everywhere

4. i edit the blog again to delete those lines

5. 2nd save of the blog will be right than

 

is that normal or do i have to use another program to write text without formats?

 

or is it enough -like you posted- to add 2-3 blank lines? (LL loves to add those anyways like it seems)?

 

would it be enough to use openoffice/words "blog" formats (i used it but didnt went well, maybe i did something wrong)?

Link to comment

? we would better ask @CPU about the finer details of board editor magic.

But since useless linefeeds are added, I guess it's somewhere in the middle of  your ctrl-c -> clipboard -> ctrl-v  where you could try to get rid of your own linefeeds (if that's possible at all).

That's all on your end, that I could think of.

Link to comment
Spoiler
32 minutes ago, donttouchmethere said:

weeh your the right one to ask:

if i copy paste my test from open office or word everything seems to get messed up with blank lines.

1. i copy paste

2. i save the blog

3. LL adds blank lines everywhere

4. i edit the blog again to delete those lines

5. 2nd save of the blog will be right than

 

is that normal or do i have to use another program to write text without formats?

 

or is it enough -like you posted- to add 2-3 blank lines? (LL loves to add those anyways like it seems)?

 

would it be enough to use openoffice/words "blog" formats (i used it but didnt went well, maybe i did something wrong)?

 

My experience with using Notepad is: 1) write what I want without placing things in lines, 2) add a symbol where I want a line break to occur (I like @ but any symbol would work), 3) copy the text and 4) remove the symbol and replace with a new line. 

Thus: I think that Worik@ would make an ideal hostess@ since she is gracious, considerate and fun - would then be easily converted to:

I think that Worik

would make an ideal hostess

since she is gracious, considerate and fun

 

But that may be more work than you want.

Link to comment

grrr, out of thumbs again, will be hard to type now

 

so notepad it is? back to the roots ^^

hmmm if i am on it already, would be interesting to see what happens if i copy paste from word to notepad

Link to comment

Hello. Just got a mention here.

I will read the full blog tomorrow. If anybody can tell me what the actual problem is I may give a solution earlier.

Link to comment
9 minutes ago, CPU said:

Hello. Just got a mention here.

I will read the full blog tomorrow. If anybody can tell me what the actual problem is I may give a solution earlier.

like a ghost out of the bottle =D

 

the problem is:

if i copy paste text i wrote in word/open office and copy paste it into my blog and save the blog=> LL will add blank lines between every sentence and additionaly some at the top of my created spoilers.

only after editing the blog again and delete those blank lines i get rid of them. No issue in short texts but i think in horror about what happens if i add longer texts with more added formats.

 

whats the best way to add text from word/excel/open office into my blog

or should i use a completly other program to prepare my texts?

 

and sure if you are here and want to check what i wrote from the technical aspect that would be great too

(btw no hurry, dont think i will give up on LL in the next few years xD)

Link to comment

You can use Ctrl+Shift+V to paste without formatting.

Of couse, you will lose the format, but you get rid of the empty lines.

Just be sure the original text does not contain empty lines at the end, because these will be pasted no matter what.

 

P.S. Genie in a lamp. And you still have 2 wishes to be fulfilled. But your soul is now mine.

Link to comment

Couple of comments on your blog @Psalam

1) No need to clean all the masters. You will only save half a second on load time. The game way to load files will do it automatically. (You save a null time.)

2) If you create or edit mods, better to use the 7zip version of SKSE. Installer one will just add a few registry keys that are useless. Just grab the archive, unpack, and copy ALL in Skyrim directory.

3) LOOT, only if you do not use MO (MO2 does not have it, MO 32 bits has it.)

4) Do not use both LOOT and Wryebash. They will conflict. Prefer Wryebash in case you need to merge mods.

5) On ENBBost config, save 10% o the max possible ram on videomemorysizemb. For some reasons if you have less than 2Gb of Vram goes faster. On 4Gb is about the same. On 8Gb and more makes no difference. Keep in mind that the max real used ram for Oldrim (with ENBBost) is 6.5Gb..

 

 

Link to comment
11 minutes ago, CPU said:

You can use Ctrl+Shift+V to paste without formatting.

Of couse, you will lose the format, but you get rid of the empty lines.

Just be sure the original text does not contain empty lines at the end, because these will be pasted no matter what.

 

P.S. Genie in a lamp. And you still have 2 wishes to be fulfilled. But your soul is now mine.

thx for the quick info!

wow, okey i gave up one wish for a copy paste issue *facepalm*

about that soul thing, i am on loverslab, you realy think there is still something to harvest ? *browses horse dicks for females*

 

Link to comment
Spoiler
43 minutes ago, CPU said:

You can use Ctrl+Shift+V to paste without formatting.

Of couse, you will lose the format, but you get rid of the empty lines.

Just be sure the original text does not contain empty lines at the end, because these will be pasted no matter what.

 

P.S. Genie in a lamp. And you still have 2 wishes to be fulfilled. But your soul is now mine.

 

32 minutes ago, CPU said:

Couple of comments on your blog @Psalam

1) No need to clean all the masters. You will only save half a second on load time. The game way to load files will do it automatically. (You save a null time.)

2) If you create or edit mods, better to use the 7zip version of SKSE. Installer one will just add a few registry keys that are useless. Just grab the archive, unpack, and copy ALL in Skyrim directory.

3) LOOT, only if you do not use MO (MO2 does not have it, MO 32 bits has it.)

4) Do not use both LOOT and Wryebash. They will conflict. Prefer Wryebash in case you need to merge mods.

5) On ENBBost config, save 10% o the max possible ram on videomemorysizemb. For some reasons if you have less than 2Gb of Vram goes faster. On 4Gb is about the same. On 8Gb and more makes no difference. Keep in mind that the max real used ram for Oldrim (with ENBBost) is 6.5Gb..

 

 

 

Gee, I'm glad I didn't ask for anything for my birthday! ?

Link to comment
On 9/18/2018 at 11:10 PM, CPU said:

1) No need to clean all the masters. You will only save half a second on load time. The game way to load files will do it automatically. (You save a null time.) 

didnt know cleaning master files had something to do with speed ?

do those issues not matter anymore?: Why clean the master files

 

Link to comment
On 9/18/2018 at 11:10 PM, CPU said:

4) Do not use both LOOT and Wryebash. They will conflict. Prefer Wryebash in case you need to merge mods

what exactly is the conflict?

LOOT => for sorting first time (if you dont know the mod positions anyways) and check if mods are dirty (iiik)

Wryebash => manually sort load order, delet esp,  create bash patch (no usage of LOOT after creating bash patch, not using them at the same time)

 

for me LOOT isnt needed anymore, but it helped a lot as I started to add mods to skyrim the first year^^

the more LL mods got added the less useful was LOOT

Link to comment

This part

[Display]
iTintTextureResolution=2048

might create problems on weaker machines.

 

They could go for 1024 or even back to vanilla 256

[Display]
iTintTextureResolution=1024
;iTintTextureResolution=256 // Vanilla

 

Link to comment
On 9/18/2018 at 11:10 PM, CPU said:

Keep in mind that the max real used ram for Oldrim (with ENBBost) is 6.5Gb..

 

Spoiler

CyMmo.jpg

 

Edited by donttouchmethere
Link to comment

The OS is using some Ram and VRam memory too.

It is not used by Skyrim. The memory consumed is between 1 and 4 Gb depending on the OS and the settings.

Link to comment

I'd like to point out that without AlignHeapAllocate=1 in CrashFixPlugin.ini the game will crash when you try using RaceMenu's UUNP morphs.

Link to comment


×
×
  • Create New...