TES Skyrim 0.206

[MaxG3D]

Weird, for me DxDiag also show false report, I have 670 2GB and it shows 4GB. Both 32 and 64bit.

[ENBSeries]

Modd31
Thanks, but i just more confused because of that info, may be statistics is broken inside d3d or driver after allocation i do at start to detect available size of video memory.

Here is another test which generate enbseries.log file, just start the game end exit it after main menu, post result here. Of course only important for those users who have strange results of video memory size reported (so low performance with the mod).

EDIT: file deleted

[wolfgrimdark]

Here you go. I had SweetFX and FRAPS both disabled (although I am still using SKSE - let me know if I need to disable that as well). I am also on 326.80 drivers (Beta) - went back to them when 314.22 didn't make any difference.

MARK1: - 19444.294922
1335
1207
1079
951
823
695
567
439
311
183
55
4023
3895
3767
3639
3511
3383
3255
3127
2999
2871
2743
2615
2487
2359
2231
2103
1975
1847
1719
1591
1463
1335
1207
1079
951
823
695
567
439
311
183
55
4023
3895
3767
3639
3511
3383
3255
3127
2999
2871
2743
2615
2487
2359
2231
2103
1975
1847
1719
1591
1463
1335
1207
1079
951
823
695
567
439
311
183
55
4023
3895
3767
3639
3511
3383
3255
3127
2999
2871
2743
2615
2487
2359
2231
2103
1975
1847
1719
1591
1463
1335
1207
1079
951
823
695
567
439
311
183
55
MARK2: - 0.001441
13632

ENBLOCAL settings:

[PROXY]
EnableProxyLibrary=false
InitProxyFunctions=false
ProxyLibrary=d3d9_sweetFX.dll

[GLOBAL]
UsePatchSpeedhackWithoutGraphics=false
UseDefferedRendering=true
ForceFakeVideocard=false

[PERFORMANCE]
SpeedHack=true

[MULTIHEAD]
ForceVideoAdapterIndex=false
VideoAdapterIndex=0

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

[WINDOW]
ForceBorderless=false
ForceBorderlessFullscreen=false

[ENGINE]
ForceAnisotropicFiltering=true
MaxAnisotropy=16
EnableVSync=false
AddDisplaySuperSamplingResolutions=true

[LIMITER]
WaitBusyRenderer=false
EnableFPSLimit=false
FPSLimit=60.0

[refusedzero]

Testing the new v2.06 d3d9 right now. I have bad stuttering and some unloadable saves again with the previous .205 version. Will share SPM shortly.

2x Crossfire 6970 AMD, 16gig RIPJAW RAM, I-5 3500, (will give more specs if needed).




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

Getting weird CTDs when going from interior to exterior locations. No CTDs present when ENB gone or using v.204. Much, much less stutter for me though, it's now very smooth.

[ENBSeries]

Ok, i see now how it work. Well, workaround possible, but if vram will go to the limit game may crash, i can't track all stats then.

[Modd31]

Hello again, I did the test with the new file.
Here the result:
MARK1: - 46183.929688
1481
1353
1225
1097
969
841
713
585
457
329
201
73
4041
3913
3785
3657
3529
3401
3273
3145
3017
2889
2761
2633
2505
2377
2249
2121
1993
1865
1737
1609
1481
1353
1225
1097
969
841
713
585
457
329
201
73
MARK2: - 0.000139
5600

I was using 2 proxy dlls (SFX and one for Sharpen I received from Oyama), do I have to do it without them?

[CruNcher]

Weird, for me DxDiag also show false report, I have 670 2GB and it shows 4GB. Both 32 and 64bit.

There are different values complete allocated Video Ram shared with System Memory and the Dedicated Video Ram which is the Real Physical Value you have on the Card
For Windows NT 6 the Dedicated memory is important not the Physical

Since the GPU is more a integral part of the OS Resource handling it has become more complex and also Applications like the Web Browser can influence a lot these days if they running on VRAM, i had already a lot of problems with ENB and Firefox

4 GB i guess is the normal allocation for a Intel NT 6 64 bit system (3GB Shared)
I have also these 4 GB allocated but in real i have 1 GB Physical VRAM it seems very normal at least on a Intel IGP system as Intel allocates also this Memory for their IGP
and running in the IGP and Dedicated GPU mode.

[Phinix]

Some feedback from users:

USER: Hmm, something's way wrong. With .200 binaries and your mod, performance version, I have about 26-30fps on Windhelm docks in snowy weather. (on a STEP install, so admittedly lots of textures) With 2.06 and your latest file, performance version, I am somehow crawling between 1 and 5 fps barely able to move around. I had backed up the old files, went back to them, and performance was back to normal. Very odd to say the least, dont see what could account for such a large drop. Edit: I should specify this weird behavior around Windhelm docks seemed quite specific to the area. I had normal FPS with 206 in some other places. So maybe its just a massive conflict between a 206 feature and one of the mods I have affecting the area graphically.

ME: Strange. I just replayed the beginning of Dragonborn last night, so I know exactly the area you are talking about (was there just before I got on the boat) , and I had no slowdown at all. Most likely this would be mod or config related, but there are a few things to check. Did you check this utility to make sure your enblocal.ini settings are correct for your video card and system? Also, are you running a ugrids value greater than 5? You might also want to try some of the tweaks I mention in the description one at a time in that area: Try DisableDriverMemoryManager=true and see if that helps, if so it may be driver issues. Lastly, try ReduceSystemMemoryUsage=false and if that works post your video card specs, how much VRAM, and what type of OS (32-bit or 64-bit), as there are other options in the ENBoost settings in enblocal.ini you could try, like EnableUnsafeMemoryHacks=true or ReservedMemorySizeMb=256, but I'd have to know your specs to say for sure.

USER: YES, I do use an AMD card but with the recommended settings. "Also, are you running a ugrids value greater than 5?" - NO

ReduceSystemMemoryUsage=false solved the issue completely, shooting me up from 1-3 fps back to 28-ish in the area in question. Which is funny because in the 200 config files, I'm using ReduceSystemMemoryUsage=true without any FPS issues whatsoever.

My conclusion is that the new system is a lot more aggressive about reducing system memory usage and cripples the game in areas with high memory usage. Given my texture packs, stuff like WATER, the 'real ice' texture which I think is extra demanding for some reason, enhanced snow, Snow/Wet effects, hand-placed waves all around the bay, the extra NPCs around and other stuff like that, I guess that my memory footprint in that specific area (and likely others) crosses a threshold of usage that 206 is struggling with. 200's more lax memory reduction probably doesn't care about letting me allot what is required. I recall that Pre-ENBoost, that area was occasionally a bit crash prone for me, which would make sense if I was running into the 3.1 barrier. Final observations would be to add would be that if I turned to look at the ground or a wall instead of the bay, my FPS would shoot right back up. Also, my GPU wasnt heating unusually, so pretty clearly a CPU or VRAM/RAM bottleneck causing this.

For now, given that "ReduceSystemMemoryUsage" is a pretty big part of why I want ENBoost, I'll revert to 200 again, unless you have other suggestions. If you're in touch with Boris, perhaps you can copy my feedback. Or I could post in the ENBoost discussion. I'm sure this issue will only affect people with heavily modded installs.

Specs: x64 Win7, 8Go DDR3, Intel i5 2500K@4.2Ghz, Radeon HD 6970 2GB with 20% OC. Also using SSD acceleration.

Just FYI.

[ENBSeries]

Is this solve performance issues?

EDIT: file deleted

[wolfgrimdark]

Is this solve performance issues?

Ah your amazing, I was holding my breath while the screen was loading ... and it worked. I took him in and out of a few buildings in Whiterun, then ran through the Tundra and while there was some minor stuttering (killer grass mods) it never once locked into a low FPS.

Will do another test with SPM but wanted to report back with the good news so far.

EDIT:
I played for another 15 minutes - ran around tundra, ran into a mine, fought bandits ... all went well, no sudden drops to 1-4fps. Some stuttering and the like but as I said outdoors I have a lot going on. SPM wasn't taking proper samples though so going to try it again.