Boris
Please don't change the memory optimization code. It works wonderful! People just need to be more cautious when using custom textures.



That's me!

_________________
| i5 | 8gb RAM | GTX660 | Windows 8 | Skyrim on SSD |
My music project, Akira Project, website at Sound Cloud

Huh Boris i updated now to 215 replacing enbseries.dll and the [FIX] and [ANTIALIASING] sections updated but what is strange i don't see the FIX neither the Antialiasing Sections anymore in the Realtime GUI ?
I cant enable/disable Temporal AA from the GUI neither EdgeAA it's not displayed anymore ?
Neither i can see options like Removeblur anymore the FIX section options ?
Both sections just disappeared ?

_________________

WoodsOfYpres
314.22, all newest drivers unsupported by my winxp as they require .net 4.0 and i can't use them without nvidia control panel in case of manual installation.

CruNcher
Parameters of enblocal.ini are in smaller window which is on top of enbseries.ini window.

_________________
i5-4690k, 16Gb RAM, GTX 1060 6Gb, X-Fi Titanium, Win7 x128
I am INFP, not the brutal, godamnit.

Ahh i see, was to small thx, lol where they located always their and i mistakenly thought it was the blue box or did you moved them for 215 into the yellow box ?
I could be sure i was always scrolling in the blue box not that i lose my sanity here

Nice the Temporal AA shows less temporal Artifacts also the latency is much better with it now (did you changed something) ?

AAAhh the combination of TAA and DOF is the latency problem and that causes Temporal Artifacts (Ghosting) the DOF takes to much GPU cycles and the TAA seems to have no chance then

though the Framerate doesn't really change it seems just the high frame latency be the cause for the TAA to fail with the DOF enabled

_________________

CruNcher;

The box with Apply button and enblocal.ini settings changes it colors if you have TOD activated.

The harder you push your computer the more noticeable the ghosting will be, that hasn't changed since TAA initially was released.

Hehe in this case the Harder you push your GPU that is already @ 99% most of the time

yep the problem is the DOF Balance though but yeah DOF is the heaviest part in the whole Render chain

@Boris

Would you think it's possible to make SSAO Efficiently Scene Adaptive, in terms of the Brightness of the Scene so if the Scene becomes very dark (mostly @ nights) disabling SSAO and if the Scene becomes brighter above a certain value enabling it ?

A option todo this via the TOD though wouldn't be enough seeing that you can have some bright point lights illuminating the scene so it would really need to analyze the scene brightness and that very fast @ best even when moving in the direction or a radius of a certain light source and it predicts it will become very bright and before the scene is even reached it enables SSAO when the scene is left and it gets very dark again it disables it

For really very dark scenes i guess it could save some cycles, or would that idea be flawed ?

For example such a Scene like this

_________________

I dont have that problem like skysan4298.
Using 13.10 beta driver.

_________________
CPU :: Core i7 2600k @3.40GHz
GPU :: Sapphire Radeon HD 7870 GHz edition 2GB
Ram :: 8GB
Sound :: Creative X-Fi Titanium
OS :: Win 7 Ultimate 64-bit

Roger ! I understand. Better encourage people to polish more their presets. Personnaly, I don't need SMAA or FXAA, regarding your last additions to EdgeAA and TransparentAA. I talked regarding 90% of ENB presets I tried, that always used SMAA and LumaSharpen (and sometimes dither).
They should take example of Unreal Cinema ENB I am currently using. Calls to shaders, no external software.
I saw by the way people that are porting SweetFX features to shaders or effect.txt. So, preset creators are responsible.

You don't need to further improve memory manager. You corrected the most Skyrim's unbearable bugs (using RAM instead of video memory, 32 bits limitation,...) and probably can't do much more (regarding threading errors). I can finally enjoy the game. I can have a freeze or a CTD from time to time but It doesn't prevent me to play since I often save. These freezes and CTDs are rare and completely random (works when I restart the game) so do not bother with this.

Considering support of bugs, maybe you can add a big sticker saying you don't care about people using 3rd party softwares with ENB (OSDs monitors, SweetFX, HialgoBoost and so on). But I think people using "safe" configs deserves to be listened.
So better adding ENB preset in our signature.

_________________
Asus P8Z77-V, G.Skill TridentX 2x4go PC3-19200 CL9, Intel Core i5-3570K (3.4 GHz), Gigabyte Geforce GTX 670 WindForce 3x OC(335.23), Samsung SSD 840 Pro 128go+500Go 7200RPM SATA III, Auzentech X-FI Forte 7.1, Windows 8.1 Pro x64, The Grim and Somber ENB

I guess lot of the Problems also come from the Havok Engine the version that Bethesda implemented wasn't yet efficiently Multithread optimized
I guess we will see the new better optimized version in the next Fallout version of the Engine

_________________

Boris: Very nice job on the TransparencyAA. No complaints since enbhost.exe testing. Take a nap, or have a pajama party now, you deserve a nice rest/relaxation period. Thanks for your efforts.

_________________
FX 8350 (4.2GHz) @ 5.015GHz// DDR3 Oc'd@1949mhz//EVGA 660GTX 2GB in SLI