TES Skyrim 0.277

[skynet3021]

Also any ENB after 266 gives me stuttering when i turn the camera

I also noticed this, now that I know someone else hit it I tried to find out why.
I deleted all of my enb-related files from the skyrim directory and installed 277 wrapper from scratch. To narrow it down I disabled effects. The only changes from the defaults are below:

Code: Select all

enbseries.ini
	UseOriginalPostProcessing=true
	UseOriginalObjectsProcessing=true
enblocal.ini
	VideoMemorySizeMb=4096

Note that I have a bunch of mods and am overtaxing vram. I suspect the high memory use compared to vram size is a big part of what's going on here.
My GPU is Nvidia GTX 670 (2GB), I have 16GB of system memory, OS is Windows 7 x64

All testing at "coc guardianstones" when at main menu.
vram is full according to the skyrim performance monitor and GPU-Z. The memory reported in "windows task manager" is as follows:
enb 277: TESV.exe - 851MB, enbhost.exe - 2160MB, system 6.35GB
enb 264: TESV.exe - 855MB, enbhost.exe - 2199MB, system 7.65GB
One nice thing is that the system memory use is quite a bit lower with the newer version, but I don't think that matters in my case.

Even with the 264 enb I got stutter when turning around (swapping textures in/out? I don't know) but with the more recent ENBs like 277 it’s considerably worse. It seems like once everything's loaded in it's fine - it's just that first time I turn around that things stutter, and this stutter has increased dramatically. It's the difference between some choppiness (~5fps maybe) to a one-second pause.
I narrowed it down to something between 264 and 269. One of the big changes was terrain parallax so I deleted all modded textures from data/textures/landscape (not subdirs though) and there was no difference.

Boris, I don't expect you to know what's going on here but I can narrow it down better if I had the versions between 264 and 269. Is there a way I can get those older releases?

[ENBSeries]

I said there is no changes which may affect stuttering, ENBoost was not changed. The only important changes which are for reducing video memory usage by removing some render targets and reuse another instead of them, any lags produced after such changes are bad driver optimizations or broken driver optimizations for the mod, if they exist at all. Please stop talking about this, i will not do anything and will not answer any more.

[TreyM]

TreyM
The next thing I'm doing in updating my own preset (whenever I can get myself to not get tired of Skyrim in 3 minutes) is remove a palette texture altogether and use procedural correction. It allows for overall higher quality and a more HDR image. Everything that can be done with a palette can be done through other, more powerful tonemapping and color correction techniques already available through ENB. Palette textures are sorta the lazy man's way to do it. Companies like Epic are simply out to make money and if they can use shortcuts to produce a better image than they had before (even if its still inferior to what they COULD do) then they'll do it. Such techniques also fit very well into ReShade and MasterEffect since they are by their nature generic for use with many games. ENB gets tailored to one game at a time.

Ah, would you mind getting in touch with me via PM to explain how the procedural correction works? (To avoid spamming this thread)

[myztikrice]

FPS counter is bugged and updating multiple times a second

[ENBSeries]

It's your pc buggied with crapware, fps counter is perfect.

[snsmac]

@TreyM for LUT take a look here:viewtopic.php?f=7&t=4394

[benhat]

when i use "filter bluriness" of "reflections" i get a giant blur step from 0.10 to 0.11. and the rest e.g. from 0.11 to 1.00 does not do enough in my opinion, or there is no way to have it set less blurry than that 0.11 limit. so i think there is a bug, or is it something on my side (some setting of reflections that influence it that way?) ?
thanks
(this is not 0.277 specific, it has been that way for me a long time now)

[ENBSeries]

It's not a bug. Applying filter properly means reading texture with certain offset of at least one neighbor pixel. Internally blurring range parameter is discrete to fit offsets.

[benhat]

ok that makes sense, thanks.

[TreyM]

@TreyM for LUT take a look here:viewtopic.php?f=7&t=4394

FANTASTIC!