ENB explanation

[Cowgoesmoo3]

I just got a neat new computer meaning I can finally play

 

I have an i7 5500u 2.5 ghz and geforce 950m, just in case you wanted to know generally what kind of comp I have

 

I heard for all these years about ENB's, and i've seen pictures, but I really don't know how they work. I tried them at some point on my old computer but couldn't understand how to get them to work.

 

Does anyone have suggestions for a new skyrim setup involving ENB's or explanations of WHAT enb's and their related mods are, or what they do....?

[Cowgoesmoo3]

THanks

[Thallassa]

ENB Background

ENB is a program that hacks Skyrim's (and other games') rendering engines. It was made by a crazy Russian software developer, and can be found here. The documentation is scattered and written in somewhat broken English by a genius who understand this stuff at a level way beyond most people and is *almost entirely* unable to explain it to lay people, so this is my attempt to explain how it works based on my interpretation of what I've read from him, from other people who are also trying to interpret him, and testing by various people. Mostly the STEP team.

ENB consists of: ENBhost.exe, d3d9.dll, ENBseries (which is all the graphics stuff: It includes an enbseries folder which contains many other files dependent on the preset, and enbseries.ini, which contains settings specific to graphics), and enblocal.ini (which contains settings that are universal to enboost and enb, and some graphics settings).

ENB does not function with out d3d9.dll (assuming wrapper version). Therefore, moving that out of the skyrim folder will disable ENB, *including the memory patch*. d3d9.dll requires directX 9 to function. While directX 11 is fully backwards compatible, DirectX 12 is missing some features that are required. Therefore, if you are using windows 10, see here.

 

ENB graphics

is the single most important thing to making a beautiful skyrim. Honestly, just ENB with no other changes can lead to something that's greatly improved over vanilla. *That comes at a cost*. Even the simplest ENB setup will drop fps. The most complex ones will bring even the most powerful computer to its knees (I'm talking sub 20 fps on a 980).

There are hundreds of enb presets on the nexus, and each has a different look. They can mix and match with any traditional mods. Which mods you use alongside ENB can greatly change its look. Differences in monitor calibration can greatly change its look. You will have to try multiple ENBs before you find one that's perfect for you. Don't just settle on Realvision. Freely tweak the settings as you wish.

If you want a place to start, I like this ENB comparison with screenshots and benchmarks.

For installation: Follow STEP, and make sure your steps are consistent with the instructions on the page of the ENB preset you wish to use.

ENB haxx

Part of ENB is changing Skyrim memory allocation to allow it to use more memory than a 32 bit program can normally use. This is "ENBoost" and can be used independently of ENB graphics. Skyrim is a large-address-aware 32bit program. That means it can use 3.1GB of memory. The rendering engine loads everything it needs to load into both RAM and VRAM. This means it can use up to however much VRAM you have, in RAM, and in VRAM, but no more.

ENBoost fixes that. ENBoost allows Skyrim to load things into RAM *or* VRAM. (Some things must still load into both). ENBoost also allows things to load into more space than Skyrim can use normally (more than 3.1 GB). It does this by putting the additional things it needs to load in a separate executable, ENBhost.exe. These make things already loaded so it's much faster for Skyrim to access them from ENB's wrapper. (This executable does not need to be launched; it will launch automatically if you are using the wrapper version of ENB).

Currently, ENBoost does not allow you to use more than 4 GB VRAM on windows 10 or some 8.1 installs. see here.

It is important that you set up ENBlocal.ini correctly. Not doing so can lead to CTDs, other errors, and memory. Because it is so hardware dependent, you must take any advice on it as *recommendations* and *do your own testing* before calling it done.

As usual, STEP covers all the settings.

 

UsePatchSpeedhackWithoutGraphics=

Do you want ENB graphics? Do you have an ENB preset installed? Then that should be false. Do you *not* want ENB graphics? Do you *only* want the memory patch without graphics? Then it should be true. I see people randomly switching it back and forth for no reason to try to get rid of the red message that says which way you have it. DON'T DO THAT. If you have it set the correct way for your purposes, then the message is just confirming you have it right!

After that, time to fiddle with some memory settings. Here are my recommendations:

[MEMORY]

ExpandSystemMemoryX64=false ; Set to true if you have 64 bit memory and default SKSE settings; otherwise set to false to prevent random crashes.
ReduceSystemMemoryUsage=true ; leave true
DisableDriverMemoryManager=false ; leave false
DisablePreloadToVRAM=false ; leave false (unless you have very low VRAM and love stutter).
EnableUnsafeMemoryHacks=false ; leave false

ReservedMemorySizeMb=128 ; This can be any value of: 64, 128, 256, 512, or 1024. It defines how much space is left empty in the VRAM so that new resources that need to be loaded can immediately go into it without having to empty old things out. Increasing it can decrease stutter which occurs when Skyrim needs to unload things from VRAM so that it can load new things into VRAM, but increasing it too much can cause you to run out of VRAM or cause stutter when things move from RAM to VRAM. Some people report that with the most recent version of ENB, they actually had to decrease it to 64, which eliminated all stutter.

VideoMemorySizeMb=6144 ; This is TOTAL VIDEO MEMORY SIZE, which can be measured with the dx9 version of this tool. It's approximated by RAM + VRAM - 2048. Whichever way you measure it, you gotta leave some space over for your windows install (300ish for 64 bit and 170ish for 32 bit) and any programs you like to run in the background (I leave an extra GB or two just in case). Highest possible value is 10240. Setting this value higher can INCREASE stutter and possibly performance because it will make Skyrim need to move things from RAM to VRAM more often, but will also prevent running out of memory. Decreasing the value too much may cause serious issues such as failure to load or crashing (not to mention not taking good advantage of your system. I would never set it lower than 3.1 GB (because below that... you're telling Skyrim to use LESS memory than it can natively use).

 

EnableCompression=false ; leave false unless you are severely limited by VRAM; setting to true may cause stutter.
AutodetectVideoMemorySize=false ; leave false. This setting doesn't always work correctly and you should manually set video memory size.

Other settings
[WINDOW]
ForceBorderless=true
ForceBorderlessFullscreen=true

This allows you to alt-tab smoothly without Onetweak, but may come at a performance cost.

[Engine]
EnableVSync=true
VSyncSkipNumFrames=0

This is one way to keep skyrim from going over 60 frames. If you have a 120 or 144 hz monitor, you can set it to skip frames (skip 1 for 120 or 3 for 144. I think.). Some people report a small performance cost to vsync.


[LIMITER]
WaitBusyRenderer=false
EnableFPSLimit=false
FPSLimit=10.0

Leave false. It doesn't work right. Use your graphics card utility to limit fps instead if you don't want to use vsync.

FixParallaxTerrain

This is all or none. If you have parallax landscape mods such as vivid landscapes, this must be set to true or the parallax textures will look like crap. If you have non-parallax landscapes because your mods don't cover everything, this must be set to false or the non-parallax textures will look like you're tripping. This doesn't affect non-landscape textures, and non-landscape textures don't have the same "all or none" issue as this does. To effectively use parallax landscape features, I recommend either amidianborn landscapes or Skyrim HD tribute parallax landscapes + Vivid Landscapes. Either combo will cover all landscapes. Pfuscher's mods *do not* cover all landscapes.

Incorrect setup

1. Enbseries.ini must be designed for the same version of ENB as the one you're using (within reason). If you're using an ENB designed for 0.2xx, you *must* use an 0.2xx enb d3d9.dll or the game will break. If you're using an ENB designed for 0.6xx, you can use 0.6xx or 0.7xx download from enbdev.com but you *cannot* use 0.2xx download or the game will break. And so on.

2. ENBSERIES.INI Notice: If you have crash at start or when game loaded, then find all variables with value -1 (minus one) and set them to 0.

3. If you have a laptop with an Nvidia graphics card, there is a good chance that your switchable graphics depends on Nvidia Optimus, which is incompatible with ENB. If you notice unexpectedly low fps when using ENB or even ENBoost alone, or if on the starting screen the ENB message states that it is using Intel HD xxxx, then you need to use the *injector* version of ENB.

4. It is possible to set up ENB to work with Hialgoboost or Sweetfx using proxy libraries. Other things that require d3d9.dll may be incompatible (such as skyrim performance monitor, although that does have a compatibility option which is functional, or virtual reality headsets). In this case, use the injector version of ENB.

Edited November 5, 2015 by Thallassa

[Cowgoesmoo3]

ENB Background

 

ENB is a program that hacks Skyrim's (and other games') rendering engines. It was made by a crazy Russian software developer, and can be found here. The documentation is scattered and written in somewhat broken English by a genius who understand this stuff at a level way beyond most people and is *almost entirely* unable to explain it to lay people, so this is my attempt to explain how it works based on my interpretation of what I've read from him, from other people who are also trying to interpret him, and testing by various people. Mostly the STEP team.

 

ENB consists of: ENBhost.exe, d3d9.dll, ENBseries (which is all the graphics stuff: It includes an enbseries folder which contains many other files dependent on the preset, and enbseries.ini, which contains settings specific to graphics), and enblocal.ini (which contains settings that are universal to enboost and enb, and some graphics settings).

 

ENB does not function with out d3d9.dll (assuming wrapper version). Therefore, moving that out of the skyrim folder will disable ENB, *including the memory patch*. d3d9.dll requires directX 9 to function. While directX 11 is fully backwards compatible, DirectX 12 is missing some features that are required. Therefore, if you are using windows 10, see here.

 

ENB graphics

 

is the single most important thing to making a beautiful skyrim. Honestly, just ENB with no other changes can lead to something that's greatly improved over vanilla. *That comes at a cost*. Even the simplest ENB setup will drop fps. The most complex ones will bring even the most powerful computer to its knees (I'm talking sub 20 fps on a 980).

 

There are hundreds of enb presets on the nexus, and each has a different look. They can mix and match with any traditional mods. Which mods you use alongside ENB can greatly change its look. Differences in monitor calibration can greatly change its look. You will have to try multiple ENBs before you find one that's perfect for you. Don't just settle on Realvision. Freely tweak the settings as you wish.

 

If you want a place to start, I like this ENB comparison with screenshots and benchmarks.

 

For installation: Follow STEP, and make sure your steps are consistent with the instructions on the page of the ENB preset you wish to use.

 

ENB haxx

 

Part of ENB is changing Skyrim memory allocation to allow it to use more memory than a 32 bit program can normally use. This is "ENBoost" and can be used independently of ENB graphics. Skyrim is a large-address-aware 32bit program. That means it can use 3.1GB of memory. The rendering engine loads everything it needs to load into both RAM and VRAM. This means it can use up to however much VRAM you have, in RAM, and in VRAM, but no more.

 

ENBoost fixes that. ENBoost allows Skyrim to load things into RAM *or* VRAM. (Some things must still load into both). ENBoost also allows things to load into more space than Skyrim can use normally (more than 3.1 GB). It does this by putting the additional things it needs to load in a separate executable, ENBhost.exe. These make things already loaded so it's much faster for Skyrim to access them from ENB's wrapper. (This executable does not need to be launched; it will launch automatically if you are using the wrapper version of ENB).

 

Currently, ENBoost does not allow you to use more than 4 GB VRAM on windows 10 or some 8.1 installs. see here.

 

It is important that you set up ENBlocal.ini correctly. Not doing so can lead to CTDs, other errors, and memory. Because it is so hardware dependent, you must take any advice on it as *recommendations* and *do your own testing* before calling it done.

 

As usual, STEP covers all the settings.

 

UsePatchSpeedhackWithoutGraphics=

 

Do you want ENB graphics? Do you have an ENB preset installed? Then that should be false. Do you *not* want ENB graphics? Do you *only* want the memory patch without graphics? Then it should be true. I see people randomly switching it back and forth for no reason to try to get rid of the red message that says which way you have it. DON'T DO THAT. If you have it set the correct way for your purposes, then the message is just confirming you have it right!

 

After that, time to fiddle with some memory settings. Here are my recommendations:

 

[MEMORY]

 

ExpandSystemMemoryX64=false ; Set to true if you have 64 bit memory and default SKSE settings; otherwise set to false to prevent random crashes.

ReduceSystemMemoryUsage=true ; leave true

DisableDriverMemoryManager=false ; leave false

DisablePreloadToVRAM=false ; leave false (unless you have very low VRAM and love stutter).

EnableUnsafeMemoryHacks=false ; leave false

 

ReservedMemorySizeMb=128 ; This can be any value of: 64, 128, 256, 512, or 1024. It defines how much space is left empty in the VRAM so that new resources that need to be loaded can immediately go into it without having to empty old things out. Increasing it can decrease stutter which occurs when Skyrim needs to unload things from VRAM so that it can load new things into VRAM, but increasing it too much can cause you to run out of VRAM or cause stutter when things move from RAM to VRAM. Some people report that with the most recent version of ENB, they actually had to decrease it to 64, which eliminated all stutter.

 

VideoMemorySizeMb=6144 ; This is TOTAL VIDEO MEMORY SIZE, which can be measured with the dx9 version of this tool. It's approximated by RAM + VRAM - 2048. Whichever way you measure it, you gotta leave some space over for your windows install (300ish for 64 bit and 170ish for 32 bit) and any programs you like to run in the background (I leave an extra GB or two just in case). Highest possible value is 10240. Setting this value higher can INCREASE stutter and possibly performance because it will make Skyrim need to move things from RAM to VRAM more often, but will also prevent running out of memory. Decreasing the value too much may cause serious issues such as failure to load or crashing (not to mention not taking good advantage of your system. I would never set it lower than 3.1 GB (because below that... you're telling Skyrim to use LESS memory than it can natively use).

 

EnableCompression=false ; leave false unless you are severely limited by VRAM; setting to true may cause stutter.

AutodetectVideoMemorySize=false ; leave false. This setting doesn't always work correctly and you should manually set video memory size.

 

Other settings

[WINDOW]

ForceBorderless=true

ForceBorderlessFullscreen=true

 

This allows you to alt-tab smoothly without Onetweak, but may come at a performance cost.

 

[Engine]

EnableVSync=true

VSyncSkipNumFrames=0

 

This is one way to keep skyrim from going over 60 frames. If you have a 120 or 144 hz monitor, you can set it to skip frames (skip 1 for 120 or 3 for 144. I think.). Some people report a small performance cost to vsync.

 

 

[LIMITER]

WaitBusyRenderer=false

EnableFPSLimit=false

FPSLimit=10.0

 

Leave false. It doesn't work right. Use your graphics card utility to limit fps instead if you don't want to use vsync.

 

FixParallaxTerrain

 

This is all or none. If you have parallax landscape mods such as vivid landscapes, this must be set to true or the parallax textures will look like crap. If you have non-parallax landscapes because your mods don't cover everything, this must be set to false or the non-parallax textures will look like you're tripping. This doesn't affect non-landscape textures, and non-landscape textures don't have the same "all or none" issue as this does. To effectively use parallax landscape features, I recommend either amidianborn landscapes or Skyrim HD tribute parallax landscapes + Vivid Landscapes. Either combo will cover all landscapes. Pfuscher's mods *do not* cover all landscapes.

 

Incorrect setup

 

1. Enbseries.ini must be designed for the same version of ENB as the one you're using (within reason). If you're using an ENB designed for 0.2xx, you *must* use an 0.2xx enb d3d9.dll or the game will break. If you're using an ENB designed for 0.6xx, you can use 0.6xx or 0.7xx download from enbdev.com but you *cannot* use 0.2xx download or the game will break. And so on.

 

2. ENBSERIES.INI Notice: If you have crash at start or when game loaded, then find all variables with value -1 (minus one) and set them to 0.

 

3. If you have a laptop with an Nvidia graphics card, there is a good chance that your switchable graphics depends on Nvidia Optimus, which is incompatible with ENB. If you notice unexpectedly low fps when using ENB or even ENBoost alone, or if on the starting screen the ENB message states that it is using Intel HD xxxx, then you need to use the *injector* version of ENB.

 

4. It is possible to set up ENB to work with Hialgoboost or Sweetfx using proxy libraries. Other things that require d3d9.dll may be incompatible (such as skyrim performance monitor, although that does have a compatibility option which is functional, or virtual reality headsets). In this case, use the injector version of ENB.

Thanks so much. Can you tell me where you found this?

[Thallassa]

Thanks so much. Can you tell me where you found this?

 

I wrote it!

 

I've got quite a bit of documentation written up in the wiki at https://www.reddit.com/r/skyrimmods/wiki/index. Other people have written documentation there too, like Terrorfox1234, Nazenn, and others. Much of the information comes from STEP as mentioned; the rest of it I picked up from reading various forums, including this one, and testing myself.

Edited November 9, 2015 by Thallassa