With 0.201, my frame rate is being locked at 30 FPS, except when I look at the sky. I've tried ReservedMemorySizeMb=512 and 1024, always the same problem. With version 0.200, my frame rate never went below 40 FPS. Also, my RAM and VRAM usage didn't really change from version 0.200 (max RAM usage for both 0.200 and 0.201 was approx. 900 MB and maximum VRAM usage was approximately 1750 MB). I have a GTX 660 Ti 2GB video card.

On this PC...
CPU: Core2D E6400
RAM: 4GB
VGA: GTX550 (1GB VRAM)
OS: Win7x64

The other one is a bit better and has the same issue.

Still the most stable and Performant Setup for my System with Crazy low memory usage , but i don't thrust SPM and i test entirely without it

[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
ReservedMemorySizeMb=512
EnableUnsafeMemoryHacks=true


these results haven't changed since 198 for me

also i honestly think ENBs testing methodology should be changed with a ENB preset that is not only pressuring the system on it's highest level but also optimized and using the whole featureset and imho that is Opethfeldt his astonishing overall ENB work that is not biased towards one goal but tries to push ENB the way Boris visions it and is really Gameplay optimized in all regards and this consistency as hard it it might sound no other ENB preset Author has reached yet.

just my 2 useless cent

_________________

0.200: ebhost.exe 1450MB, TESV.exe 750MB
0.201: ebhost.exe 962MB, TESV.exe 758MB
I like how 0.201 reduced 33% memory usage on the same area which is outside Whiterun.

Boris,
can DisablePreload flag be two flags for interior and exterior, so we can set it to true for interior but false for exterior? Don't know if this is even possible to detect the cell loading is interior or exterior.

_________________
i7-3770, 8GB XMP-2132
Win10v1909 64bit on SSD, Skyrim on 2nd SSD
Nvidia GTX 1070 FE v441.87
OrganicENB SE
OrganicENB LE

@Boris

DisableDriverMemoryManager=true

i think this can make Nvidias Driver and Windows to act a little bit strange after long play time applications such as the Windows Picture Viewer can only allocate 1 HD image after running ENB with this and it shows a Memory warning when trying to open the next HD PNG
Funny is it can only not load them in the Windowed mode but in Fullscreen it works

Boris forget that a Windows Hard Drive Space issue 20 mb werent enough to display a downscaled HD PNG in Windowed Mode (Microsoft)

_________________

This is not correct for me. I have 4GB of vRAM on my GTX 680 and a very minimal install of skyrim bordering pure vanilla. 0.200 stutters far less and when looking at a particle system such as fire. Difference is 29 fps loss when looking at fire with version .201 versus only an 8 fps loss with .200. Version .201 also stutters way more in general than .200, in all actuality version .200 didn't stutter at all or at least not that I could even notice while version .201 stutters quite a bit and is very noticeable.

Nightasy
If you look at fire with low fps, press key to free ram. If performance increase, this just means textures allocated in system memory by driver, i not sure yet how to workaround this. You have too much texture mods installed or if video memory not filled completely, then it's not mod at all, may be driver.

skysan4298
Preload functionality useful only at loading stage,so no interior/exterior separation.


I just found that compression i did cost a lot of performance when memory for textures not enough while looking at some objects and heavy stuttering occur. Will try to prebuffer them uncompressed, let's say about 100 mb buffer to keep them. Compression itself is very helpful when enbhost.exe not running or 32-bit OS.

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

I see the flag can be toggled from the ENB Gui, so thanks for making that can be toggled from in-game. I have a few save and a few cell locations I consistently would get the infinite load, so I'll toggle it to true for those cells. Those are always interior for some reason.

_________________
i7-3770, 8GB XMP-2132
Win10v1909 64bit on SSD, Skyrim on 2nd SSD
Nvidia GTX 1070 FE v441.87
OrganicENB SE
OrganicENB LE

My FPS was locked at 30 when in flora heavy sections and pretty normal everywhere else, (interiors were 60 FPS). At first I thought this was done on purpose and I actually liked it because I seemed to get almost no stuttering, but then I reloaded Skyrim and it (the FPS) seemed to go back to normal yet the stuttering seemed to be fairly low compared to previous versions as well. Overall, a good thing so far ^^

Not sure if any of this is helpful at all but I had the same problem (fps locking at 30) with .201 and I tried similar changes. However I fixed it by disabling Vsync (in skyrim ini, driver, and enb) and just enabled fpsLimit and set the fixPhysics to true.

I have been trying to push my system trying to see what settings help provide stability while getting as much quality as possible. Compared to .200 I got a very small boost of about 5 fps outdoors.

I am currently using Somber Antique Ultra Quality. Roughly 150 mods (109 esp files) with Bethseda HR textures plus dozens of HR (2k and 4K) textures from various modders.

SOME AVERAGES on 201:
No down-sampling at 1920x1080: Memory 1518, VRAM 1773, Disk I/O 9MB, CPU 12%, GPU 65% Threads 41, FPS 39 (was locked at 30 till I made changes)

Hardware down sampling from 2560x1440 to 1920x1080: Memory 2002, Vram 3012, Disk I/O 4MB, CPU 10%, GPU 94%, Threads 40, FPS 24.

Memory settings for both:
[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
ReservedMemorySizeMb=1536
EnableUnsafeMemoryHacks=false

I also found I had massive stutters looking around but when I bumped memory up to 1536 (from 1024) they went away. Not sure if it was the memory that did that or some other factor I overlooked.

System: Intel i7-3930K CPU @ 3.2 - x12 Win7 64b; 16GB Ram, 6GB Vram on GTX Titan. Game installed on my SSD.