TES Skyrim 0.269

[ENBSeries]

Pfuscher
Transparent objects do not produce reflection, even if they do have specular. Cubemaps are ignored for reflection, because they have nothing in common with amount of reflection. The types of objects with reflection are undefined, any of them.

pasking
Absolutely wrong. Value of available memory is written at game start and in profiler of editor, that is max and you must not set bigger than that.

[pasking]

Boris,

I apologize for the newbie question.It is that my game performs constant 38FPS outdoors, but falls to 26FPS in shifts. I read that in W7X64 systems with more than 8GB RAM the bill would 4096-170.

I ask these questions because I am doing a manual for Portuguese-Brazilian and users must be exact to the beginners points.

I need to do step by step, as I teach an NGO and our course of game developers start learning how to make mods for Skyrim !!!

Our work exists only because of their talent.

Thank you for responding and continue their work.

[Pfuscher]

Thanks again!

[ENBSeries]

pasking
There is no math actually, because amd and nvidia have different amount of shared video memory dependent from os and amount of ram. When i wrote long time ago how to calculate this, information was based on pc with relatively low amount of ram. As i said in previous post, texture memory size is valid value, otherwise it can be seen by some utils. If amount of memory set is too big, mod will work properly, but in the case of no more free memory available it will lead to delays to free some space and this process is repeatable, so stuttering in other words.

[Oyama]

Boris
Top corner's counter now works smoothly. Thanx for the update.

[TwoArmedMan15]

Hello, Boris. With the new 0.269 version, the FPS counter is still flickering for me. Also, the memory auto-detection does not seem to be working. The profiler always reads 0 Mb memory detected, and the ENB always uses whatever is set for VideoMemorySizeMb, regardless of whether AutodetectVideoMemorySize=true or false.

This could be an AMD specific issue, cause I've noticed everyone who has said the new 0.269 is working for them has an Nvidia card. My GPU is an AMD r9 280.

[Edit] Nevermind. It's fixed now. The FPS counter is still flickering but the memory autodetection is working. I just had to reinstall the d3d9.dll and enbhost.exe. I don't know what was causing the memory to not be detected, but reinstalling fix it. :/

[Jafin16]

It's not an AMD specific issue. Works perfectly for me, including fps counter.

[wolfgrimdark]

I have been trying out a variety of presets with it. I do get the flickering FPS but everything else is fine and it doesn't bother me. Just giving some extra feedback.

[pasking]

pasking
There is no math actually, because amd and nvidia have different amount of shared video memory dependent from os and amount of ram. When i wrote long time ago how to calculate this, information was based on pc with relatively low amount of ram. As i said in previous post, texture memory size is valid value, otherwise it can be seen by some utils. If amount of memory set is too big, mod will work properly, but in the case of no more free memory available it will lead to delays to free some space and this process is repeatable, so stuttering in other words.

Boris,

Thanks for helping me.
For my case, what is the configuration that you indicate to memory?
Even using shadows and textures 1024x1024 have stuttering!
Set up the memory of the VGA to 4096 and reserved to 512. I went up to 1024 and also failed to resolve.
And much obliged for your patience.

[ENBSeries]

I don't think that stuttering happens because of wrong setting. Try to disable compression, if enabled. And try this configs:
[MEMORY]
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=true
EnableUnsafeMemoryHacks=false
ReservedMemorySizeMb=512
VideoMemorySizeMb=3400
EnableCompression=false
AutodetectVideoMemorySize=false

For amd cards it seems DisableDriverMemoryManager=true is the best