Boris, TY TY TY!
This is it! Lock down the memory management code! Don't change this perfection!
Setting VideoMemorySizeMb to same as my GPU memory made gameplay silky smooth. Panning camera was very smooth too. I tried to raise it to 2x volume, and it had some stutter. Now, about the higher-res downsampling resolution without changing the desktop...
[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=true
DisablePreloadToVRAM=false
ReservedMemorySizeMb=512
EnableUnsafeMemoryHacks=false
VideoMemorySizeMb=2048
_________________ AMD R9 6900HX, 16GB DDR5-4800
Win 11Pro 64bit on NvMe, Skyrim on NvMe 2nd partition
Nvidia GTX 1070 FE eGPU v531.209 OrganicENB SE OrganicENB LE
Phinix ExpandSystemMemoryX64=true - invalid description. As i don't have x64 OS and heard about 3.1 gb limit (which is 4 gb), couldn't test myself with VMMap, so thought it's bug in game engine when some buffer pointer used in math, so i did this variable to fix issue by using memory range of 3-4 gigabytes. At same time this greatly reduce memory fragmentation, but effective only for x64 systems as they give 4 gb of virtual address space for 32 bit applications (winxp allow to set 4 gb, but it's very buggy mode and not recommended). I don't know how to describe this to users, but seems this parameter always work for everybody, so let it be true always, some users report that even this enough against their problems.
DisableDriverMemoryManager=false - again wrong, this depends from drivers, os and videocard. Fewer chances to get CTD or low performance if driver is bad and if it have own memory manager. But if driver is good, on the contrary it can give stable work and better performance. Also when set to true, d3d will try to do everything to not show any errors, at cost of performance or long freezes, so it's kind of "do or die" parameter, while set to false it's like "you can't? okay, ctd".
DisablePreloadToVRAM=false - wrong again. Faster loading times because textures and geometry not actually created when game loading, they are creating only when visible in camera. Side effect is stuttering when object not in memory, but very useful when saved game won't load because of too much data in cells (imho simpler just to set lower quality, go to other place to save). Cell transition take longer time only when new cell objects are visible immediately, so not always valid definition.
EnableUnsafeMemoryHacks=false - yes, again. This is for videocards with a lot of video memory, because this mode is if player don't want to have any stuttering, any side effects (except alt+tab issue) or by some reason this set to false not work (reason actually other software). This mode also perfect if user have disbalanced system like 32 bit OS and videocard with 4 gb video memory. This mode don't use dynamic memory reallocation, so no compression, no enbhost.exe. Also it work only when ReduceSystemMemoryUsage=true set.
ReservedMemorySizeMb - this depends too much from 32/64 bit system and vram size. Smaller - less ram usage of the game (fewer CTDs), but bigger in most cases means less stuttering in very heavy areas where many mods used (and ugrid too high). If user have 512 mb of vram, this value 512 is also nice, because entire video memory will be dynamic, it's already small for heavily modded game, so better to not block it by static data. As i understood from posts, lower value also helps to some users with infinite loading screens (perhaps they happen because i'm forcing in cycle to free old memory and try again to allocate for new resources).
VideoMemorySizeMb - this is very unique for each system. What you wrote is correct, but not for users like Goliatron. Other d3d9 mods, web browsers, many other software want to use vram too and bad drivers add more headache. Almost all systems have vram available greater than physical vram, but some users reporting driver errors when vram is completely filled up with data (above i wrote why). If system is clean and only game is running, this value can be very huge, for example 16384 should work for rig with gf660 2 gb + 16 gb ram. But! If you have 6144 for 4 gb of ram and 2 gb vram, don't even think about running something else while playing, because there is a huge chance that non local video memory (ram actually) size will reduce because of other application and you will get very low performance or CTD.
DigitalPrinceX
Don't know if i need to spawn another one or two enbhost processes if one will not be enough (it now can handle only about 6 gb ram compressed); something with other mods not work, seems those which modify geometry; additional thread will help to reduce stuttering when cells loading; more experiments with statistics of texture usage per frame also may decrease stuttering when not enough vram, but a lot of textures; small textures on the distance may greatly increase performance to allow run even with 256 mb vram. A lot of work, but at least i may not afraid to forget how everything work and make graphic changes (which i don't remember now, ha-ha).
Yersinia79
If you have freezes with values above vram size, get another drivers and close all software, run the game only, no mods like sweetfx. If you can't, then set a bit less than vram size.
I have a HEAVILY moded Skyrim running on 3 Titans in sli and a OC i7-3770K. With the new Version 0.209 skyrim seems to access the power of my rig. Just ran around stressing my system and VRAM went up to 3,624 MB and RAM 955 MB. FPS was constantly between 50 - 60 frames with FPSLimit set to 60. Im going to do some further testing tommorow .... but looking really good so far!
By the way: I had stuttering in the past, because i raised [TerrainManager] fTreeLoadDistance higher than 75000.0000 in the SkyrimPrefs.ini ... for sure, alot of people are reporting problems because they are moding/tweaking skyrim to death .... most reported problems have nothing to do with ENBoost ...
by far the best I have seen yet. Solid 40 fps plus no crashes no freezes. I have a 3GB VRAM 7950 and fount setting it equal to my Vram was solid but setting it to 4096 gave me better performance. Haven't tried higher values although i do have 16gb ram
best version ever made!
no stuttering, no CTDs, not cell loading freezes, no freezes at all, super smooth, also when rotating cam, no endless loading times
testet on continous running through cities and heavy grassy forrests incl. fights
No charts at the moment as I have just been playing the game (as in playing versus testing) but did want to report that after an hour it was all smooth. No stutters, no crashes, smooth, good FPS. I am using:
I wanted to give a more in depth performance review of the new binary but the spam filter is halting me from saying basically anything. In short, I've tried various memory sizes up to double my actual amount and it has been flawless. Everytime I increased the value my frame rate seems to go up little by little. Great work, Boris!
ENBSeries
Thanks for the feedback. I re-uploaded with revised feature descriptions and edited my previous post here. Hopefully that will give better clarity and help people fine-tune their ENBoost settings to get the most out of their Skyrim experience.
Last edited by Phinix on 24 Aug 2013, 01:57, edited 1 time in total.
Works like a charm for me, the loadings seems are way faster compared to 0.208 (however I did not really measured, but it really look like it is).
I've been playing for more than an 1h arround winterhold and really stuttering free or CTD while I have 150 esp and tons of HD textures.
I have set VideoMemorySizeMb=4096 which is the very same amount of vram I have on my GTX 670 and I use the 326.80 driver eventhough it messes up my DoF when there's fog and sometimes the sun too..
I'll be doing some further testing in other place of the game that badly affects my performance usually and have an insane VRAM needs...
With ReservedMemorySizeMb=768 the maximum ram usage of TESV.exe was 803Mb with an average of 377Mb so awesome!
