ENB 101 – Under the wrapper

This guide is geared for people who are installing the ENB binaries to run an ENB preset. (or to enable ENBoost)

Before we get started

This is by no means a comprehensive guide, and is geared for people who are installing the ENB binaries, either to run an ENB preset, or solely to enable ENBoost.

First a simple disclaimer. Every system is different, and everyone’s expectations are different. There are many presets available both old and new, and some impact performance much more than others. In short there are a lot of possible reasons you might have issues, and this is not a repair guide. Just be aware that you might have to try several presets before you find one you like that also works well for you.

Ok but what is it?

ENB … I have to admit, I have no idea what it actually stands for, but “Everybody Needs Boris” was by far the best answer I recieved when I asked. It is a 3D Graphic modification framework developed by Boris Vorontsov. It allows for much more detailed and creative control of the way the game processes 3D effects and lighting. The newest versions are even weather aware. The first time you see the morning sun filtering through a misty forest, and notice the perfect shadows, it will all become clear (pun intended:)

ENBs come in two parts. The files that comprise the actual code that allows the framework to run, which we call the binary, and a second series of files that contain all of the settings required to customize the “look”, which we call the preset.

The binaries also come in two versions, the "wrapper", and the "Injector". Both of them function the same, and are configured almost identically, but are accessed differently by the computer. This is important because the injector version works better for some people, and is often a fix for people having problems running the wrapper version. We will be focusing on the wrapper version in this guide, but there are instructions for using the injector version in the trouble shooting section.

Where do I get it?

The Binaries both current and archived must be downloaded directly from www.enbdev.com.

His website is a little confusing for first time visitors so Click on News, then scroll down and select Downloads, then scroll down again and select TES Skyrim.

*

That will bring you to the correct binary "main" download page. Scroll down and you will see the available binaries on the lower left hand side. The Version numbers are the links to the appropriate download pages. Boris has also been nice enough to explain the major changes for each version … but I would like to expand on that just a bit.

*

Scroll all the way to the bottom of the Binary page to find the download button.

*

While most presets will work with most binaries. Boris has been developing the enb series for quite some time, adding or removing features and modifying the binaries to improve functionality, stability, and to reduce memory usage. Some binary versions on the enbdev website are not available any more, but you can still find presets for them on the nexus, in this case you should always go UP in version, not down unless you have problems running the preset with the newer version.

Therefore, if you do find a preset that you really like the look of, and it was written for an older Binary, let’s say version V0.224 for an example; you may get unpredictable results if you try to run that preset under a much newer binary. It’s just good practice to stay as close to the original binary as possible. By all means test it with a newer binary, but be forewarned if you do get unpredictable results. In the example above you should choose binary V0.236, but you might need to try V0.221 if you have problems running the preset. I assume the versions listed for download are grouped by where Boris considers he has made significant changes.

The most important thing to remember is that the binary is not an ENB preset, it is the framework that allows the preset to run. In many if not most instances you will actually only be copying the D3D9.dll file, and ENBHOST.exe from the WrapperVersion folder. The other files contained in the folder are what are being modified by the authors of the preset, and will be supplied by them. As always, read the installation instructions of the preset to know which files are required.

Basic Installation

For ENBoost users, everything you need is in the wrapper folder, and requires no additional preset. I will cover installation and configuration of ENBoost first seeing as the configuration for running a preset is essentially the same with only minor changes.

Download the most current binary, (at the time this guide was written, V0.308) and extract it to a folder on your desktop with your preferred manager. (for ease of installation) It should contain both the wrapper and injector version folders, but we will be focusing on the wrapper version in this guide.

These files get installed in your game folder, not your data folder, therefore you can’t install them with a mod manager. However, you can install parts of the presets with a mod manager for ease of testing and uninstallation, and I highly recommend doing so. We will cover that a little later on. For now, navigate to the folder your game is installed in. For most people that will be.

X:\Steam\SteamApps\Common\Skyrim (Where X: is your game drive) or
C:\Program Files (x86)\Steam\SteamApps\Common\Skyrim (For single drive systems)

If you see SkyrimLauncher.exe and TESV.exe (applications) you are in the right folder.

If possible, I highly recommend not installing the game in your Program Files folder. Windows has file, and folder security settings in place in the Program files folders that require administrator privileges to install, update, and run correctly.

To install the ENB Binary for use with a preset or for ENBoost only, simply copy the three files listed below from the Wrapper Version folder into your game folder. ENBoost is now fully installed, but not configured. We still need to edit the ENBLocal.ini file for it to work correctly.

*

To use the binary with a preset we will be copying additional files from the preset authors download into the game folder as well. It is important to note that the these additional files are modified versions of the original files we did not copy from the binary folder earlier. It is very easy to get confused by identically named files which is why I don't recommend copying the entire wrapper folder contents, though it is safe to do so.

A quick note on memory

If there is one area where different ENB guides seem to contradict each other to the confusion of all it would have to be memory. So if you have re-read the installation instructions from different presets, looked at a few of the available videos, and even questioned the preset authors directly only to come away even more confused, You're not alone, and It's not your fault! I don't want to add to the confusion. But I will try to shed a light into the morass.

First lets look at the types of available graphic memory, and how you determine exactly what you have installed. Depending on your operating system, and video card, there are several ways of getting the correct values. The first is the simplest if you're running Windows 10.

• Right click on your desktop
  
• Select Display settings
  
• Select Advanced Display Settings (bottom of the window)
  
• select Display Adapter Properties (bottom of the window again)

In this example you can see that I am running an Nvidia GTX 980M Now lets look at the info

• The Dedicated Video Memory (VRam) is 8192 Mb or 8 Gb (1024 X 8)
  
  
• The Shared System Memory is 32746 Mb or just under 32Gb
  (Normal Ram memory the OS is willing to share, in this case half my installed ram memory)
  
  
• Finally the Total Available Graphics Memory is 40938 Mb or just under 40 Gb
  (Dedicated memory + Shared memory)

Note - If you are using a gaming laptop with advanced power optimization settings, you will likely see the low power integrated video chipset displayed instead of your 3D GPU, this is not an error. Please use the second method detailed below to determine your VRam.

I have seen instructions from multiple sites including the ENBDEV forums using all of the above values in different equations to come up with a "valid" setting for use in the INI files. It's no wonder how confusing it all seems.

The second method (and the best) would be to open your graphic card control panel, and check the listed Sytem information.

*

There is also a "VRamSizeTest" tool available from ENBDEV under downloads in the tools section. I do not recommend using this tool as the only value it will return is the "Total Available Graphics Memory" but when I tested it for DX9 on my system it actually returned a value that was 1/2 my physical Vram. I got the same value when I set the ENB to determine the Vram automatically. Do not trust either!

In my opinion, You will see the use of artificially inflated values recommended most often by people with limited Vram trying desperately to boost performance. If you have a video card with 1 Gb or less it can help, and we will cover that a little later. However the fact that you can specify a portion of your "Total Available Graphics Memory" instead of just the "Dedicated Video memory" does not necessarily make it a good idea. Shared ram memory is slower than high speed video memory, and depending on your background applications the available value can change.

Also one of the greatest strengths of running an ENB / ENBoost, are the advanced memory management features. Always keep in mind that Skyrim LE is a 32 bit game and the engine will not address any memory range above 4 Gb. The ENB binary will, and in doing so efficiently will allow you to use 2k and 4k textures in game without dropping you to single digit frame rates. In this guide we will specify the high speed memory only, and let the ENB buffer what is needed to slower memory when and if it's needed.

The ENBLocal.ini configuration

Most of the settings will remain unchanged to run ENBoost, and I will focus on just those settings that need to be modified for your system. Below are links to the ENBLocal Wiki pages provided by the S.T.E.P team. It is a very good reference to what most of the settings in the INI file do.

Http:/wiki.step-project.com/ENBoost
Http:/wiki.step-project.com/Guide:ENBlocal_INI/Memory
(Note - the STEP guide advocates using the VRamSizeTest tool but only after shutting down all open applications, then subtracting a percentage. As I mentioned above... Don't trust it!)

Below is the current ENBLocal.ini file provided with Binary V0.308
The configuration comments are my own.

[PROXY]

EnableProxyLibrary=false
InitProxyFunctions=true
ProxyLibrary=other_d3d9.dll

[GLOBAL]

UsePatchSpeedhackWithoutGraphics=false
For ENBoost installation “ONLY” you must change this Value to true
For use with an ENB preset, leave this setting as false

UseDefferedRendering=true
IgnoreCreationKit=true

[PERFORMANCE]

SpeedHack=true
EnableOcclusionCulling=true

[MEMORY]

ExpandSystemMemoryX64=false
A fix for 32-bit memory limitations. If you have a 64-bit Operating System set this value to true to enable working with large Memory blocks (Up to 192 Gig with compression enabled) However it has been reported that this feature can conflict with Sheson’s memory patch (now part of SKSE) if the initial heap stack is set to a value above 512mb (768Mb in SKSE). It is recommended to set this value to false in that situation, and of course with 32 bit systems also.

ReduceSystemMemoryUsage=true
Must be set to true to enable ENBoost memory reduction

DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
EnableUnsafeMemoryHacks=false

ReservedMemorySizeMb=XX
This is the Vram “swap-file” buffer setting.

• For systems with up to 1 Gig of Vram XX=64
  
• For systems with up to 2 Gig of Vram XX=128
  
• For systems with over 2 Gig of Vram XX=256

For systems with over 4 gig of Vram, or units with multiple graphics cards running in bridged
mode, 256 is still the official recommended value, however increasing this setting (in small
amounts) seems to help reduce stuttering in heavily modded systems. (I’m using 512)

VideoMemorySizeMb=XXXX
This is the amount of Vram you wish to make available to ENBoost. This value is based on
your VIDEO memory. (See memory section above) For systems with under 1 gig of Vram it is recommended to use the actual value of the Vram (512 for a 512Mb card), but this is the one instance where I would advocate adding a percentage of the Shared System Memory in 256 Mb blocks and testing performance. Every system is different, you will need to test for yourself.

For systems with 1 Gig of Vram or more, I use a simple rule of thumb … Multiply 1024 by the amount of Vram (in Gb), and subtract the buffer amount.
(IE: 2048-128=1920 for a 2 Gig card, 3072-256=2816 for a 3 Gig card)

The official documentation recommends subtracting 128 for all video cards, but I have found for systems with large amounts of Vram reducing this value by just that little bit more seems to improve stability.

For systems with over 4 Gig of Vram, there is a docummented issue that DX9 running in Windows 8 and 10 caps available Vram to 4064 Mb. After extensive testing I have determined that the best performance and stability for Skyrim are achieved by limiting the VideoMemorySizeMb value at 3584 (4096-512) That seems to be a “sweet spot” and I’ve found that every value I’ve tested above that, actually reduces performance slightly, not the other way around.

Edit - The DX9 limitation has been addressed by Windows and is no longer relevant. I have not returned to retest with the current binaries, but accepted wisdom is to just set the correct physical Vram minus the buffer.

I should mention However that Nvidia has recognized issues in the past with Vram settings above 3.5 Gig and recommended that value as an upper limit as well. I haven’t done extensive testing with other graphics cards, and you should keep that in mind if running a high end AMD card. This information may have also changed since Microsoft addressed the DX9 memory issue.

Enable Compression=false
This value is the default setting from enbdev, and works very well for systems with large amounts of Vram. For systems with limited Vram (under 2 gig) I would recommend setting this value to true for a more efficient use of available Vram.

AutodetectVideoMemorySize=false (Not recommended!)

[THREADS]

DataSyncMode=0
PriorityMode=0
New in ENBoost 6.x These settings correct problems with the way Bethesda handles multi-threading code. As per Boris’ recommendations, they should remain disabled (0) unless you are unable to load the game at all. Currently the most stable tested values are 2 for data, and 3 for priority, However Boris warns of significant performance impact.

[MULTIHEAD]

ForceVideoAdapterIndex=false
VideoAdapterIndex=0

[WINDOW]

ForceBorderless=false
ForceBorderlessFullscreen=false

[ENGINE]

ForceAnisotropicFiltering=true
MaxAnisotropy=16
ForceLodBias=false
LodBias=0.0
AddDisplaySuperSamplingResolutions=false

EnableVSync=false
If using Vsync to correct screen tearing, set to true, and you will not need to enable the limiter

VSyncSkipNumFrames=0

[LIMITER]

WaitBusyRenderer=false

EnableFPSLimit=True]
Must be set to TRUE to enable the fps limiting. However, if Vsync is enabled, and/or your monitor is set to 60Hz. This is probably not required.

FPSLimit=60.0
The Skyrim physix engine (Havok) does not work well above 60 FPS, and can/will cause very unpredictable results. I recommend limiting at 60, or even a little lower for less powerful systems.

[INPUT]

//shift
KeyCombination=16
//f12
KeyUseEffect=123
//home
KeyFPSLimit=36
//num / 106
KeyShowFPS=106
//print screen
KeyScreenshot=44
//enter
KeyEditor=13
//f4
KeyFreeVRAM=115
//B
KeyBruteForce=66

You can modify which hot keys are assigned to the ENB here. I preferred grouping the keys I use from F4 through F8, (115-119) but this is strictly a personal preference to allow logical grouping of hotkeys from other mods, and offered only as an example.

[ADAPTIVEQUALITY]

Enable=false
Quality=1
DesiredFPS=60.0
(Match to FPS Limit, or a little below, but leave disabled by default)

[ANTIALIASING]

EnableEdgeAA=false
EnableTemporalAA=false
EnableSubPixelAA=false

[FIX]

FixGameBugs=true
FixParallaxBugs=true
FixParallaxTerrain=false
FixAliasedTextures=true

IgnoreInventory=true
For use with a preset, I would recommend setting this to true so as not to re-render inventory screens in HD ... it does not improve appearance, and tends to look “jittery”

(IgnoreLoadingScreen=true ... I was recommending adding this line to the INI file as well, and unsure why it had been removed from the current enblocal.ini, but have just been informed that it's now integrated, and no longer required. This would be a good example of why you need to be careful of which binary version you choose, and it's relationship to the preset)

FixTintGamma=true
RemoveBlur=false
FixSubSurfaceScattering=true
FixSkyReflection=true
FixCursorVisibility=true
FixLag=false

[LONGEXPOSURE]

EnableLongExposureMode=false
Time=1.0
BlendMax=0.0

That completes the configuration of ENBoost. All other values can be left at their default settings unless you are experiencing problems, and are directed by the ENBoost team to make the changes. You can skip the next section, and there is no need for you to edit the Skyrimprefs.ini, but you should check the general message section, so you know what to expect.

ENB for use with a preset

Download the closest binary to the preset you’ve chosen as described above, and extract it to a folder on your desktop (for ease of installation) with your preferred manager, it should contain both a section for installation into the game folder (as described for ENBoost users) and optionally an ESP file or series of ESP files patched for use with specific mods.

There are too many presets to possibly list the instructions here, and I urge you to take the time to read the instructions provided by the author, as some presets require the editing of additional INI files included with the wrapper for the preset to function properly. An example would be the K-ENB presets which require your monitor’s resolution to be added to two additional files.

Copy all the files provided by the author of the preset into the game folder, not the ones supplied by the binary. Then copy the D3D9.dll and ENBHOST.exe files from the binary wrapper folder to the game folder, and answer yes to over-write the files.

Here we get just a little fancy … the instructions for the preset at this point will probably explain to you which ESP file to choose, and give you instructions to copy it into your Data folder. For ease of testing, and uninstallation, I would recommend the following installation method instead.

Select the correct ESP file following the supplied instructions for that preset. Copy that ESP or group of ESP files to your desktop, right click on the group, and select “add to archive” (depending on which compression software you are using) and name the archive the same as the preset, or preset with patches. Install this archive into Skyrim using your preferred mod manager like any other mod. This simplifies testing, removing, and updating the preset without the need to remember all of the correct files. I also highly recommend adding notes as to which patches are included.

We’re almost there, but not quite finished.
Before we continue… while you’re still in the game folder. Open the SkyrimLauncher, choose options and re-select your “Detail” level, in the options tab, then exit.

If you’re installing manually, or using a mod manager that does not support profiles, we now need to navigate to your games save folder. Normally this will be…

C:\Users\“your user name”\Documents\My Games\Skyrim

You are looking for Skyrimprefs.ini. Right click on it and choose “copy” then right click again anywhere in the folder and choose paste. Right click on the original INI again, and choose edit (A good habit to get into, you now have a backup copy of your original file, just in case.)

Again I can’t stress enough how important it is for you to read the installation instructions from the preset author as some of the recommended values may be specific to that preset only … I will give you the changes to the lines I have found to be common for most/all presets. Scroll down to the [Display] section and look for the lines below.

iMaxAnisotropy=16 (the values will vary depending on your detail level)
iMultiSample=8
bFloatPointRenderTarget=0

Change them to read

iMaxAnisotropy=0
iMultiSample=0
bFloatPointRenderTarget=1

If you’re modifying a vanilla installation, you will also need to add the lines below to the same section. Order is not important.

bTreesReceiveShadows=1
bDrawLandShadows=1
bDrawShadows=1

The final topic is for users of profile based mod managers such as Mod Organizer, and the newest versions of Nexus Mod Manager. I personally use and prefer Mod Organizer as does S.T.E.P. and this is a quick display of the power and benefits of the program. Mod Organizer keeps a separate folder for each profile, and separate copies of your Skyrim.ini, and Skyrimprefs.ini for each profile. You will need to edit the INI files in each profile separately to enable the ENB for all your builds… Simply select the profile, click on the “tools” button, and edit the INI files right from there.

General Messages

Aside from any additional instructions specific to your preset, you are now ready to run the ENB. Be forewarned, it will take significantly longer get through the initial load with an ENB running … this is normal.

If you are running only ENBoost, you will see a message in red in the upper left corner of your screen stating that ENBoost is loading without graphics support. This is also normal, and not a warning. It's unfortunate the message is in red.

If you failed to correctly edit the Skyrimprefs.ini file as listed above, you will see one of two possible additional messages…

The first one is very clear, and will simply state that bFloatPointRenderTarget is not enabled (The preset will not load) This value must be set to 1 to enable the preset.

The second message is a little more cryptic. And will tell you that hardware antialiasing is enabled and certain functions of ENB are being disabled. You will also see this message if you open the launcher and re-select your “details” then exit. You must correct the iMaxAnisotropy, and iMultiSample, they must both be 0. You will get some very strange results until you do, by strange results I mean things like missing water in streams, or fire pits happily smoking away with no flames in them. The first time this happens to you it can be a bit disconcerting.

Trouble Shooting

The Injector version uses primarily the same installation and configuration steps, but adds the additional requirement that before you load your game, you must to run the injector’s executable first. (through MO if you are using it) This is important because some graphics drivers handle the Injector version better, and some background programs can interfere with the wrapper version which the injector version lets you work around. We focused on the wrapper version in this guide as that covers the majority of installations, but if you're having problems I would try the injector version.

The instructions in the guide are all still valid. Simply copy the three files from the Binary injector folder into your game folder, then delete the d3d9.dll file you copied earlier.


All that remains is create a shortcut to the ENBinjector.exe file on your desktop, or add it as a binary in Mod Organizer if you are using it, and remember to run the injector before loading the game.

Final thoughts

If you are trying out different presets searching for the right look, it can get a little messy deleting and over writing the same files and folders over and over. A trick that helps me a bit is to keep a Temp-ENB folder on the desktop, and copy the current binary and preset you're testing there as well as the game folder when you install it. That way you have an immediate reference as to the correct files that need to be deleted before you install the next one.

If you need / want a profile that doesn’t use an ENB, with others that do … I’m afraid you will need to edit the ENBLocal file manually. I would recommend creating a “with, and without” version of the INI so you can simply copy the correct one into the game folder as needed.

One last thing to mention while in game with an ENB or ENBoost enabled, is clearing the Vram. Currently “F4” I have found that when I first load a game (new or continuation), load a save game while in game, fast travel, or just exiting a city for example; clearing the Vram and waiting a second or two seems to force everything to “settle down and play nice” It’s a good habit to get into if you’re having any type of random issues, or experiencing momentary hesitations (micro stutters)

Acknowledgements

I Would very much like to thank Nazenn for his very welcome contributions,

Just Chill for pointing out the DX9 limitation issues,

Black Album and MageThis for pointing out advanced power features affecting default GPU

Black Album keeping everything readable.

Change Log

1.6.2017 added change log (long over due)
1.6.2017 re-wrote a substantial portion of the text, and added appropriate images.
1.7.2017 Added memory section and additonal screen shots
1.7.2017 completed additional recommended edits
1.8.2017 Added note about displayed windows default GPU
9.14.2019 Edited DX9 memory cap warning ... Thanks Grumpy

[stcaFylnO]

Avrie! THANK YOU again! I got so utterly confused researching this topic. I got redirected to your guide, focused solely on it, and got the Wrapper ENB Boost set up no problem. I'll try to tackle a Preset some other day.

[WhyWadeWhy!?]

Understood. Thanks.

[Avrie]

I'm a bit eyeball deep setting up a new business at the moment. I still say run the launcher and set your graphics back to high. If it's Vram related that will use a lot less and allow for testing. clearing the Vram is clearing the Vram. If it's still crashing on you, you have to look deeper. Even with a properly set up system you face the odd CTD it's the price we pay for a hefty mod list. Start a thread and post all the info you can ... lots ofg people around to help. Me guessing is not going to help that much.

[WhyWadeWhy!?]

Thanks for the reply. My esp order is for sure at its optimal load order. I used LOOT and then manually adjusted esps I was told by mod authors on where to good. I'm almost certain that it's a VRAM thing as I get these crashes not from exceeding my memory hack or any script heavy events but just randomly strolling outdoors. I'm trying to get this solved before I can hop onto my 200+ mod playthrough I've been setting up for months. There any way you can personally help me out? I understand if it's too much and you simply don't have the time, and I thank you regardless for even helping me this far. Should I use skyrim performance monitor, make the skyrim launcher changes? What would you find to be a good place to start?

[Avrie]

Personally I'd run your launcher, and set your graphics to High instead of ultra and see if it makes a difference before blaming your video setup. You might hasve something else going on ... test first ... sledge hammer later :)

[Avrie]

Finally there is the matter of making sure your resource priorities match your load order. This is easy with good managers like Wryebash, and Mod Organizer... But a hidden function and real PITA for "dumb" managers like NMM. With Wryebash as an example, LOOT will sort the Mods tab, but then it's your responsibility to manually match the installers tab to match the LOOTed load order (using common sense for locating non ESP mods) Simple enough for WB... With NMM you'd have to let LOOT sort the order, copy the order to notepad, then uninstall all mods, and reinstall in the looted order ... Like I said a real PITA, but hey NMM is dumb. I can't wait for Vortex.

[Avrie]

Tough one to answer first thing in the morning, without knowing your full system specs, seeing your mod list, and reviewing your ini files. These types of game always try to utilize prerendering as much as possible so seeing your GPU fairly maxed out is not uncommon and doesn't directly point to a problem. (though it still might) There are also combinations of mods that can produce localized crashes "for no reason" (Open cities is a good example ... great mod but doesn't play well with some others, and taxes a good machine to it's limits)

[WhyWadeWhy!?]

Hey man. It's me again. I promise this is most likely my last question haha. Anyway, even when I clear VRAM with f4 key I do end up experiencing some crashes. I'll have to do a skyrim monitor test, but my regular GPU usage is at 100% when I experience the crash. But my system reports I'm always at 100%, so its easy to assume I'm using some instense visual mods. Are there any solutions you can potentially point me towards. Do I go for 1k instead of 2k textures, do I go for SMIM lite? I also heard people exprience less crashes by increasing the VRAM size and lowering the buffer size. This apprently lowers crashes but increases stuttering. I'd appreciate your opinion on all this and where and how to strart about this..

Thanks!

[WhyWadeWhy!?]

Wow, I never even knew about this. Thanks plenty, this information is just crucial.

[Avrie]

Clear vram is part of the enb binary ... you can verify the key under the [input] section of the ENBLocal.ini file (double check ... Boris likes to screw me up and change keys ... it used to be F4, but I haven't checked the v03.15 binary)

As for how often and where it happens. Crossing cell boundries is the worst, and a lot of it also falls under which texture mods you have loaded, and the default resolutions. IE: if you're running all HD 4K tree mods you might want to clear a few times in the forest. It's mostly common sense. I found I would notice a slight lag, and imediately cleared the Vram. It gets to be a habbit, and a good one