Jump to content
  • 0
prizner

Correct Enblocal Settings

Question

So I was installing SkyRealism using the enb guide and I noticed the site https://www.iparadigm.org/pages/pnenb/ENBoost.html used for getting parameters for the memory section of enblocal no longer works. After some digging I found there were some formulas to come up with the needed information but as I am still unsure if I fully understand them I was wondering if anyone here could help? I have gtx 680 4GB and 12GB of ram with a i7 980x. Thanks!

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

I have a GTX 670 & 16gb of Ram; getting good results with reserved memory @ 512 and video memory size @ 10,240 (which I believe is the maximum value).

Share this post


Link to post
Share on other sites
  • 0

Based on my specs above do you have any thoughts on what my video memory size should be set to? I am a little apprehensive to set mine that high considering I have only 12gb of ram and then 4gb on my card. Where you seem to have a little more headroom in ram.

Edited by prizner

Share this post


Link to post
Share on other sites
  • 0

Given your abundance of RAM, you can even get a bit higher at

 

ReservedMemorySizeMb=

 

768-1024 are values that were recommended by Boris on more than one occasion.

 

10240 MB is indeed the max. value for "VideoMemorySizeMb". The optimal formula is

 

your Video Memory Size - 128 MB.

 

But if you add the max. value, it won't make a difference. But cards with just 1024 MB RAM should use the formula and add

 

1024 - 128 = 896

 

as the best value. I also comply to this with my 3GB ATI.

Edited by thommaal

Share this post


Link to post
Share on other sites
  • 0

Actually, the information I gave, needs a huge disclaimer. I cite jafin16 from an ENB forum thread:

 

 

The memory management features of ENBoost (included in ENBSeries) affect both RAM and VRAM. Essentially, a DirectX 9 application (like Skyrim) mirrors the textures loaded into vram, in the RAM as well. The whole issue is that when Skyrim hits 3.1Gb of RAM (NOT vram) the game crashes, because it's a 32-bit application and can't handle more memory. What ENBoost does, in short (and I may be wrong on some of the exact specifics, but this is the gist of it), is it frees up the system memory, by not mirroring everything and offloading some of that to VRAM, and some a large chunk of it gets offloaded to the enbhost.exe application. So the 128gb future proofing that Boris did is for system RAM, NOT vram. Vram isn't really a factor. I mean, the more you have, the better, but I have never used my 4Gb of VRAM and I have a MASSIVE load order with a lot of texture/mesh packs installed and a fairly heavy ENB setup. However, if I add up system ram used by Skyrim and ENBhost.exe I regularly hit right about 3.5-4gb.Anyways, hope that explains it.TL;DR It's for system memory, not video memory.Oh, and one last thing. The parameter, VideoMemorySizeMb parameter does indeed tell ENB how much VRAM you have. However, if you set it to a higher amount, the game will then be able to use some of your system memory as VRAM. RAM isn't usually as fast as VRAM but more is always better. The formula you've seen go around is for 64-bit OS's and is VRAM+RAM-2048=VideoMemorySizeMb (maxes out at 10240). I set mine to 8192 (see my system specs below.)

Edited by thommaal

Share this post


Link to post
Share on other sites
  • 0

Why not just use the autodetect feature?

 

 

At first i was going to but then I read so many conflicting comment on some people saying use your base vram as parameters (which auto detect seems to use) other saying use more than vram aka ram+vram-2048. So I though i would just ask some people with more experience. Thank you all for your help I think I have it figured out now

Share this post


Link to post
Share on other sites
  • 0

Actually, the information I gave, needs a huge disclaimer. I cite jafin16 from an ENB forum thread:

 

 

 

The memory management features of ENBoost (included in ENBSeries) affect both RAM and VRAM. Essentially, a DirectX 9 application (like Skyrim) mirrors the textures loaded into vram, in the RAM as well. The whole issue is that when Skyrim hits 3.1Gb of RAM (NOT vram) the game crashes, because it's a 32-bit application and can't handle more memory. What ENBoost does, in short (and I may be wrong on some of the exact specifics, but this is the gist of it), is it frees up the system memory, by not mirroring everything and offloading some of that to VRAM, and some a large chunk of it gets offloaded to the enbhost.exe application. So the 128gb future proofing that Boris did is for system RAM, NOT vram. Vram isn't really a factor. I mean, the more you have, the better, but I have never used my 4Gb of VRAM and I have a MASSIVE load order with a lot of texture/mesh packs installed and a fairly heavy ENB setup. However, if I add up system ram used by Skyrim and ENBhost.exe I regularly hit right about 3.5-4gb.
 
Anyways, hope that explains it.
 
TL;DR It's for system memory, not video memory.
 
Oh, and one last thing. The parameter, VideoMemorySizeMb parameter does indeed tell ENB how much VRAM you have. However, if you set it to a higher amount, the game will then be able to use some of your system memory as VRAM. RAM isn't usually as fast as VRAM but more is always better. The formula you've seen go around is for 64-bit OS's and is VRAM+RAM-2048=VideoMemorySizeMb (maxes out at 10240). I set mine to 8192 (see my system specs below.)

I gave this a quick test and I think it really improved my performance! I have 2 GB graphic card and 8 GB of ram. I set VideoMemorySizeMb to 2048 (as per my VRAM) and I must say that sometimes I get big stutter when turning around (a clear indication of hitting VRAM limitations), especially when there are a lot of NPC in the picture (I use 1K for exterior textures, but 2K for NPCs and most of the equipment). 

 

I have changed VideoMemorySizeMb to 8192 (as per the formula above) and loaded a recent save, where a large battle occurs (Extended Encounters mod), something between 15-20 NPCs (my char + 2 followers, some bandits, a Redguard party, a giant, a farmer with a cow, some mercenaries  etc. - so A LOT of different textures loaded) and the battle went really smooth, only some minor stutters when turning around.

 

As I said, this was only a quick test in a spot I knew is bad, as I've had some problems with it yesterday when I played - first time I encountered it my game froze for about 30 seconds during getting off my horse, then another 15 sec freeze when I tried to turn back and run to fight. Now all played very smooth, no issues. 

 

I will do some more testing soon to confirm, but initial thoughts are that this formula is actually working. I just hope it's not a placebo! 

Share this post


Link to post
Share on other sites
  • 0

The formulae is in theory sound... the main issue it is that is assumes that you also have a super optimal motherboard, and otherwise decent system that can handle the bandwidth you request it to do. 

 

In general if you get any excessive stuttering, slowdowns etc. then it all comes down to just trying to alter those two values.... and your driver version ofc

 

 

I have used 8192 with 2Gb VRAM and 16Gb RAM since ENBoost came out and it has been the best option ever since... I could go to 10Gb but never saw any indication of the game asking that much with my memory requirements... it usually caps out around 8Gb. 

 

ofc. you will most likely ALWAYS get some stuttering when scrolling around really fast, and when loading new cells, but this is to be expected... people tend to forget that skyrim is a giant openworld game... not a closed in single player level with highly efficient LOD generation. 

Share this post


Link to post
Share on other sites
  • 0

The formulae is in theory sound... the main issue it is that is assumes that you also have a super optimal motherboard, and otherwise decent system that can handle the bandwidth you request it to do.

It always comes down to the specific system at work. The first formula I mentioned works well even for low-end systems, the second one is better suited for higher end and well maintained systems. The hardware is definitely an issue here, as is the OS; 64bit users seem to fare better (not surprisingly) - but, in the end, it boils down to: Just give it a try.

Edited by thommaal

Share this post


Link to post
Share on other sites
  • 0

Hm.. from what I've read leaving a little vram for other applications can be beneficial, e.g. going for 2000 in case of 2048 mb vram. Maybe this explains Rootsrat's crashes but appearently the outcome can vary from setup to setup.

I'm wondering why there isn't an explicit feature to preload textures to ram. From what I've read the method of setting VideoMemorySizeMb above vram seems unofficial but works for some people (Boris once complained about people setting VideoMemorySizeMb to high amounts). The downside for people having access vram could be that vram is crammed with textures you don't need while the textures you do need are in ram when turning around. This is speculation though as I do not understand much of the inner workings of ENBoost.

Ayien what texture resolution do you use? Maybe ENBoost just preloads as many textures as it can while leaving some working space.

Share this post


Link to post
Share on other sites
  • 0

Hm.. from what I've read leaving a little vram for other applications can be beneficial, e.g. going for 2000 in case of 2048 mb vram. Maybe this explains Rootsrat's crashes but appearently the outcome can vary from setup to setup.

I'm wondering why there isn't an explicit feature to preload textures to ram. From what I've read the method of setting VideoMemorySizeMb above vram seems unofficial but works for some people (Boris once complained about people setting VideoMemorySizeMb to high amounts). The downside for people having access vram could be that vram is crammed with textures you don't need while the textures you do need are in ram when turning around. This is speculation though as I do not understand much of the inner workings of ENBoost.

Ayien what texture resolution do you use? Maybe ENBoost just preloads as many textures as it can while leaving some working space.

Just to clarify - I don't get VRAM/RAM related crashes, I don't get other CTD's ofter either tbh. It's clearly not enough VRAM problem, as the game freezes when it tries to load new textures as the camera rotates the view. Once the textures are loaded, it comes back to normal. And again - these freezes happen ONLY where there are a lot of various NPC's in an exterior area - it's pretty much OK in the cities as well, only happens in the open world with load of NPCs

 

I will do some more testing soon and report back. And yeah, I agree there are a lot of factors to whether it works or not, like hardware set up, OS architecture, other software running in the background etc.

Share this post


Link to post
Share on other sites
  • 0

I threw out the VRAM formula weeks ago and just started using my actual GPU Memory Amounts. In DXdiag it will tell you on the display tab what your approximate "total" video memory is and that's the best number to use minus a little bit overhead.

 

For example:

 

DXDiag tells me 4095 MB's, so I use 3968 for VideoMemorySizeMb.

 

Weeks ago, with great success, I also have started using much larger ReservedMemorySizeMb settings. Boris has dropped a few bombs of late concerning how that settings interacts and the just of it is if you have limited VRAM, upping that setting to a larger percentage of you physical VRAM might be beneficial. I have 1GB VRAM, so I set mine at 512 or 768 depending on the ENB Preset that I am running. So, ENB is juggling my Skyrim with these settings:

 

[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
EnableUnsafeMemoryHacks=false
ReservedMemorySizeMb=768
VideoMemorySizeMb=3968

EnableCompression=true
AutodetectVideoMemorySize=false

 

They are tailored to my system.

Share this post


Link to post
Share on other sites
  • 0

Interesting. A few questions;

 

1. Have you found any significant differences with EnableCompression set to false?

 

2. Im running skse 1.7 alpha. With ExpandSystemMemoryX64 set to true, skyrim crashes for me. Boris did say that this was a compat issue, and hes not fixing it. Do you run skse 1.7, and if so, how are you avoiding the crash?

 

3. You mention upping ReservedMemorySizeMb higher if you have limited VRAM. By limited VRAM do you mean purely in regards to your computer, or in regards to Skyrim? I have 4GB VRAM, which I would not call limited in regards to computers. However, in Skyrim exteriors i frequently hit my VRAM limit, so it could be limited in regards to Skyrim.

Share this post


Link to post
Share on other sites
  • 0

Outstanding research Keith. Sounds like the simplest solution may be to just set autodetect=true and assume it all goes to plan. I really appreciate your diligence in chasing down answers to these questions, and then posting them here for the community's benefit (sounds corny, I know).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.