Skyrim TES.exe 3.1gb memory ceiling issue

[ENBSeries]

The reason of low fps happen with memory manager enabled is only when video memory not enough. Low VideoMemorySizeMb also produce same problem. Very big (like 1024) ReservedMemorySizeMb or very low - the same result. Only balancing these two variables is the key.

[Duredel]

I've just finished trying reserved memory settings from 64 to 2816 and at around 1536 the hitching began to subside but there was no noticeable improvement between 1536 and 2816. Once I started noticing the amount of memory tesv.exe was consuming increase as the reserved memory setting was increased I was hoping that I could get it to consistently cap out at 2.5gb or so, keeping it down in the green range while minimizing the amount of memory off-loaded on enbhost. Unfortunately there seemed to be limit and tesv.exe would briefly pop above 2gb and then back down around 1.7 or so, ensuring that enbhost would always be holding at least half a gig or so.

Anyways, the hitching is still present, especially when in heavily populated areas so I've come to the realization that the best solution will be to review my installed mods and start dumping ones I don't need and replacing what texture packs I can with performance versions.

Thanks!

[ENBSeries]

What value do you have for VideoMemorySizeMb?

[Duredel]

I'd tried both 3968 (4096-128) and 10240. I also tried it with AutodetectVideoMemorySize true and false. Oddly enough I've never seen my GPU memory exceed 1.8gb at any time so I don't know if there is some sort of limit there considering it was always ranging between 1.5 and 1.8gb regardless of location, including interiors.

[ENBSeries]

Tru AutodetectVideoMemorySize=false and VideoMemorySizeMb=3700, ReservedMemorySizeMb=512. If issue will not go away, make screenshot when fps is low in such conditions with editor visible and spoiler of profiler visible, what it show up in there by amount of memory used. I can make several builds for testing, but it's very boring and long process.

[Duredel]

Here you go. It's kinda hard to make out the Perfmon readout in the upper-left but it says:

RAM: 803 (MB)
VRAM: 1,785 (MB)

When idle (as in, not turning or in combat) the Available video memory in the Profiler will hover around 170mb or so.

[Duredel]

I played around with it some more and discovered if I set AutodetectVideoMemorySize to true it'll return with 1760 MB, which makes sense as I've never seen the VRAM number much higher than that on SPM while running the ENB dll.

However, if I reload without ENB running (removing d3d9.dll from the Skyrim folder) and retest it I will see the VRAM increase well beyond 1760mb. In 2 minutes of testing I managed to hit an area with 2.2GB of VRAM used as per SPM.

So, the question is why would not all 4GB be registering with your d3d9.dll? Could it be because it's seeing the onboard Intel HD 4600 adapter (which I believe does have 1760mb)? This is a laptop so it has both an Intel and the GTX780M onboard and will let one or the other GPU take control depending on the nVidia profile. Tesv.exe is set to use the nVidia which is confirmed by the fact that SPM is also configured to monitor the nVidia. You can see the SPM onscreen display while playing, therefore the game is indeed using the correct adapter.

I did try setting ForceVideoAdapterIndex to true but the game would not load with any other index number other than zero (I tried 0 through 6) and zero would still just show 1760mb. Any other index number would get the "Failed to initialize renderer" error when trying to launch tesv.

Thanks!

UPDATE: I think I may have resolved the problem by switching to the Injector version. Now the profiler is registering something closer to 3.7GB! If there is a way to make this work with the wrapper please let me know.

[ENBSeries]

I don't understand if issue totally solved or just statistic of vram.

[Duredel]

It seems to be. Switching from the wrapper to injector upped the available VRAM from 1760 to 4030 or so. I'm guessing that the wrapper was being presented with the VRAM total for the Intel HD 4600 GPU rather than the 4GB total from the nVidia GTX780M. Using the injector circumvented this problem. So, now that it's not having to swap vram out at all it's smooth as glass again AND ReduceSystemMemory is still enabled. Here's what I'm using now:

[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
EnableUnsafeMemoryHacks=false
ReservedMemorySizeMb=512
VideoMemorySizeMb=3968
EnableCompression=true
AutodetectVideoMemorySize=true

[menko]

I use a similar card, the GTX 680M and for sure you should set EnableUnsafeMemoryHacks=false.

If set to true i get a lot of stutter.

The only thing is that get CTD even when i dont reach the 3.1 limit and i have 4gb of Vram and 16gb of ram.

Is it normal??

Pd. Boris can we use 2k textures of is it too much to handle for the game in exteriors?