TES Skyrim 0.206

[wolfgrimdark]

quick update ran DXDIAG and 32 bit report 4GB on titan and 64 DXDIAG reported the 1.9 so ... doing some research at Nvidia and running some tools. Hopefully will figure this out ...

[charlievoviii]

quick update ran DXDIAG and 32 bit report 4GB on titan and 64 DXDIAG reported the 1.9 so ... doing some research at Nvidia and running some tools. Hopefully will figure this out ...

doesnt matter what DXDiag say. My say 4gb vram too, but i ran my skyrim from 4.8-5.2gig worth of Vram usage. So no worries

[Neuba]

quick update ran DXDIAG and 32 bit report 4GB on titan and 64 DXDIAG reported the 1.9 so ... doing some research at Nvidia and running some tools. Hopefully will figure this out ...

doesnt matter what DXDiag say. My say 4gb vram too, but i ran my skyrim from 4.8-5.2gig worth of Vram usage. So no worries

Well my graphic card got 2GB vram and dxdiag says I got 4GB. ^^

[SiSaSyco]

It seems that 206 runs really good for me. Nevertheless posting the Log:

MARK1: - 518090.062500
4057
MARK2: - 4.984420
3826
MARK3: - 0.000214
3914
MARK1: - 518136.000000
4057
MARK2: - 4.943541
3826
MARK3: - 0.000182
3914


ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=true
ReservedMemorySizeMb=512
EnableUnsafeMemoryHacks=false
DisablePreloadToVRAM=false

Nvidia Drivers: 326.19

[MOTOSXORPIO]

test is for 4gb or larger Vram correct?

v0.206 is fantastic. I played for 4 hours last night, couldn't find a reason to complain during my play.

[SiSaSyco]

I found an issue with 206.
I just tried enbeffect.fx "NXS Post Process for ENB" (http://skyrim.nexusmods.com/mods/39027) and when I change settings in Shader-Gui-Window Windows gets a critical error and restarts. The Error was like "Page fault in non paged area".
I switched to 200 again to check if I get this error, but with enb 200 there is no such error.

[wolfgrimdark]

Last test for now. I did a few things this morning - updated my BIOS and drivers and made things were current. Played some other games to make sure they were all seeing proper video card and options, which they were, and did a fresh ENB install.

First game I loaded was indoors (Helgen) and was fine - FPS was stable and as high as 52 or so. I then loaded an outdoor game in Whiterun Market. FPS was around the 1-4 mark (roughly). I was able to look up at the sky and that gave me much higher FPS so I walked into Belathors shop and my fps was all cool and happy again, in the 50's. Went back outdoors and it went back down.

Log Results:
MARK1: - 72544.289063
1665
MARK2: - 5.172683
13297
MARK3: - 0.001083
1286
MARK1: - 73263.578125
1677
MARK2: - 5.162410
13454
MARK3: - 0.000220
1454
MARK1: - 2371.810303
1664
MARK2: - 7.071536
13454
MARK3: - 0.002486
1440

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

Using Nvidia BETA drivers 326.80

I also ran a test with FRAPS running so I could screenshot the profile stats (on the odd chance it showed anything useful) from a good and bad FPS standpoint.





If there are any other tests I can do to help just let me know. For now going to use 206 with the memory functions disabled as my system runs fine on 206 with the RSMU set to false.

[Modd31]

I tried this new binary, but the game take a huge fps hit when I go outdoor even with DOF and SSAO disabled.
If I look the sky I don't get any problems, but if I move the camera down the fps drops to 0.8-1, the weird thing is that I have 300~mb of free memory in Statistics, but I didn't have this kind of problems with .202 and .204 but I have less memory available.
I have an ATI 7850 2Gb and 8gb of RAM, I don't get what's happened after the .204 release to not work anymore with my hardware..

[ENBSeries]

charlievoviii
Actually vram size reported matters as it's used by memory manager for allocations.

SiSaSyco
Such bug unfixable unless it's occur always at certain conditions.

Modd31
Run the test from previous page.

wolfgrimdark
I can't just let the mod to use any memory available, better to find out what the problem is.
Run attached test.exe without game, it's just another 3d application, post results of it here. Then run caps viewer.exe and in subtree "DirectDraw Devices"->"Primary (display)"->"Memory" post here values under "Total" category for local, non local and texture memory.

EDIT: file deleted

[wolfgrimdark]

I ran test.exe and got a window that said "Meshes.exe" with a dialogue message "Could not find tiger.x" and an OK button. That was all it did.

Using DirectX Caps Viewer I get for TOTAL:

video (local) -> 2,055,929, 856
video (non-local) -> -294,782,976
texture -> 1,761,146,880