CTD and Performance patch ENBoost (by Boris Vorontsov)

[Aiyen]

Its still a test version. If you do not want (as much) hassle then stick with v200 otherwise wait until the next "major" version.

[Salvador]

Version 0.204 runs a lot better for me. You can set the ReservedMemorySizeMb= really low on this version. Simply backup your current dll file, you can easily switch back.

[DoYouEvenModBro]

Version 0.204 runs a lot better for me. You can set the ReservedMemorySizeMb= really low on this version. Simply backup your current dll file' date=' you can easily switch back.[/quote']

I currently have a 3gb VRAM card with ReservedMemorySizeMb=1024. Do you think that is too large?

[Salvador]

Version 0.204 runs a lot better for me. You can set the ReservedMemorySizeMb= really low on this version. Simply backup your current dll file' date=' you can easily switch back.[/quote']

I currently have a 3gb VRAM card with ReservedMemorySizeMb=1024. Do you think that is too large?

If using 0.204, yes.

 

Max you should use is 512. The lower you go, the less stutter, however, the higher a chance for freeze or CTD, but you need to go really low for that. Try 384 and see how that goes. You need to find the sweet spot really, which if dependant on your mod list and hardware.

[DoYouEvenModBro]

Version 0.204 runs a lot better for me. You can set the ReservedMemorySizeMb= really low on this version. Simply backup your current dll file' date=' you can easily switch back.[/quote']

I currently have a 3gb VRAM card with ReservedMemorySizeMb=1024. Do you think that is too large?

If using 0.204' date=' yes.

 

Max you should use is 512. The lower you go, the less stutter, however, the higher a chance for freeze or CTD, but you need to go really low for that. Try 384 and see how that goes. You need to find the sweet spot really, which if dependant on your mod list and hardware.[/quote']

Why are the values lower than they were for 0.200 - 2.202?

[Salvador]

Version 0.204 runs a lot better for me. You can set the ReservedMemorySizeMb= really low on this version. Simply backup your current dll file' date=' you can easily switch back.[/quote']

I currently have a 3gb VRAM card with ReservedMemorySizeMb=1024. Do you think that is too large?

If using 0.204' date=' yes.

 

Max you should use is 512. The lower you go, the less stutter, however, the higher a chance for freeze or CTD, but you need to go really low for that. Try 384 and see how that goes. You need to find the sweet spot really, which if dependant on your mod list and hardware.[/quote']

Why are the values lower than they were for 0.200 - 2.202?

Because Boris changed the memory manager, and added dynamic unloading of the VRAM. Which means if less than 64mb free VRAM space is left it automatically unloads a bunch of data. Naturally this means that only really big memory spikes cause a problem.

However, I just follow his words and advise, as I have no clue what goes on under the hood in the d3d9.dll and Enbhost.exe. He said this version needs lower values with 512 max.

 

With 0.204 I can load saves with ReservedMemorySizeMb=128 that I couldn't load before with anything lower than 640 (the saves my wife uses, she uses tgm and carries loads of items). I also have less stutter now.

[ibleedmonster]

No SLI does not share memory... Even Boris cannot do anything about that since it is an inherit limit on the hardware level.

Motherboard and Graphics chip developers would have to create new architecture for that to be possible.

 

Also I think that his approach is going to hit a stability wall soon enough. There are still nobody that are able to run exterior with full 4k afterall. I have only verified that you can run with higher ugrids values if using only 1k textures mainly with an SR mod list fairly stable. Although at my resolution of 1440p then performance takes a serious hit, since that also means that AO filter etc has to be applied on a much larger area... which really hurts my poor gtx 660.

I can run 4k textures... for about 1hr or 2 in game miles whichever comes first

but no seriously... I have toned back some of my texture mods and could use some help setting up an ENB if anyone has the time and wouldnt mind giving me a hand, just PM me if there are any volunteers.

 

I am running mostly 2k textures now with some 1k's and etc and was hoping I could preserve my install if the ENB performance enhancer actually works, if it doesnt I have an alternate set of textures ready to go for testing already which lowers resolution again.

 

ATM I am running 340+ with about 110 esp's, its a highly modified S.T.E.P. install but typically runs at 60 FPS everywhere. only issue I have is the 3.1 Gb limit which I'm very hopeful that this will fix.

 

@aiyen by 1440p do you mean 1440p or do you mean 1440 resolution? I ask cuz I am running in 1080p which is 1920 resolution.

 

on a final note, the matter of infinte load screens, a lot of my experiences and others i have helped mod the game get infinte load screens when they hit the 3.1 Gb limit, on a load screen it wont cause a crash it will just cause it to hang. this can be easy to do if you are at 2.4g ram then go into a building or etc and it loads a lot of newer non shared textures.

[Aiyen]

1440p = 2560x1440 as far as I have understood the term! So far nobody have corrected me so I assume people know what I mean! (If it is technically correct is another matter!) :D

 

If you need any help setting up ENB just throw me a PM with the specifics... I am always happy to help and learn some more!

 

So far I can also run with mostly 2k in exteriors without the normal issues... the few issues I have had might as well have been script related, or just due to bad optimization of my mods since I updated quite a few of them without all the tes5edit steps.

 

Last test was playing for roughly one hour before a CTD... which for the amount of script mods and the quality of the textures is okay for me if it turns out to be the case.

[ibleedmonster]

aye kewl will do ty man...

 

N I looked up your monitor I guess maybe it is 1440p.. television formats for definition arent always intuitive, 720p for example.. but 1440p is close enuff! LoL

[c0c0c0]

Max you should use is 512. The lower you go, the less stutter, however, the higher a chance for freeze or CTD, but you need to go really low for that. Try 384 and see how that goes. You need to find the sweet spot really, which if dependant on your mod list and hardware.

What if I go the other way?  I've got a 2 gig card, and I'm still getting fair regular CTDs and ILSs (Infinite Loading Screens).  I'd definitely give up some FPS to cut back on that.  What would happen if I went with, say, 768?

[Aiyen]

A random egg boiler in the general vicinity of your house will blow up!

 

 

Joke aside.

 

If you go up then you will experience more stuttering, but the game should be more stable at smaller texture loads.

If you get massive texture loads, then the stutter might get so bad that the game will freeze up or just CTD.

 

At least that is how I have understood it so far.

[c0c0c0]

Is it just texture loads, or do ENB settings figure in as well? I use only 1K textures for exterior settings, with a mix on interiors (but a preference for 2k). I'm wondering if I can do something like increasing the reserved memory, and pay for it with SSAO, or something like that. I could also disable some of my texture packs, but I want to know if there is anything I can more easily live without.

 

Also, doors appear to be particularly problematic. Is there a trick to minimize the risk of a CTD, like waiting a few seconds to open it, or hitting Shift-F12, or any voodoo like that?

[Aiyen]

Increasing the AO and reflection filter size should make them take up more space as they become more detailed I think.

 

As for stopping transition CTD´s then first make sure that your LOD textures are not too high res. It is a known cause of issues.

[Valamyr]

207 seems like a major step up! Stability is higher than ever for me, and it fixes the issues I had with 206 where some areas suffered dramatic performance losses. (rare issue I'm told).

 

I use the version bundled wih Phinix Natural ENB. I'm just saying, this is a must try for anyone who has stability issues, and not just obviously-RAM-related ones.

 

It wont fix a borked save or mod conflicts, but it does wonders on a properly built one.

[ibleedmonster]

I second what Valamyr said... I went from a crash every 45mins or every second building change to absolutely no crashing at all.

also would like to point out that PNENB is VERY lightweight and and very unobtrusive. it "can" be a little dark at times but aside from that I see absolutely no reason NOT to use this ENB as a general solution.

 

I have noticed a very slight stutter, though i wouldnt even consider it a stutter but it is noticeable to me... its not consistant at all so im guessing this is due to the cacheing being at 512?

if I lower this value can I just lower it or does it need to be in specific increments? Basicly I think dropping from 512 to 384 would be too aggressive. I think perhaps 448 would be more appropriete but am not sure if that slight amount would even have an effect