Nvidia GeForce 384.76 Download & Discussion

me too

 

I don't think this is new to this driver set, I'm still on 382.53 and my GPU's idle and 139MHz.

 

vulkan api updated too? because have beta developer testing this... and always in next major branch changes the updates goes to whql drivers

 

One other new thing, not strictly driver related - it looks that the 1.6.1 patch for The Division added DX12 DLL for HFST shadows so HFTS is actually working in DX12 in The Division now.

Xbox APIs are different from PC's and it's generally a lot easier to make a good low level renderer for a fixed h/w platform. I just don't think that Ubisoft will be able to get better performance out of DX12 than they get in DX11, but who knows...

Thanks, guys. So they did actually upgrade this capability and Maxwell got the upgrade as well, nice.

You are using a Titan card which is reference only, all Pascal reference cards are idling out on the same 139 MHz AFAIK, it's the custom OC versions which had higher idle clocks previously for some reason.

Heh, this one is interesting to the point where I'd say this is a bug of the driver distributive - they install the same old 1.0.42.1 Vulkan runtime but the Vulkan driver itself reports that it is supporting Vulkan 1.0.46.0. So theoretically the driver is limited by the runtime which is supplied within the same package.

 

215MHz idle to 139MHz , Definatly did that i checked my hardware monitor before i installed these.

 

a bad thing?

 

Code:

Direct3D 12 feature checker (March 2017) by DmitryKo
https://forum.beyond3d.com/posts/1840641/

Windows 10 version 1703 (build 15063)

ADAPTER 0
"NVIDIA GeForce GTX 970"
VEN_10DE, DEV_13C2, SUBSYS_136619DA, REV_A1
Dedicated video memory : 3221225472  bytes
Total video memory : 4294901760  bytes
Video driver version : 22.21.13.8205
Maximum feature level : D3D_FEATURE_LEVEL_12_1 (0xc100)
DoublePrecisionFloatShaderOps : 1
OutputMergerLogicOp : 1
MinPrecisionSupport : D3D12_SHADER_MIN_PRECISION_SUPPORT_NONE (0)
TiledResourcesTier : D3D12_TILED_RESOURCES_TIER_3 (3)
ResourceBindingTier : D3D12_RESOURCE_BINDING_TIER_2 (2)
PSSpecifiedStencilRefSupported : 0
TypedUAVLoadAdditionalFormats : 1
ROVsSupported : 1
ConservativeRasterizationTier : D3D12_CONSERVATIVE_RASTERIZATION_TIER_1 (1)
StandardSwizzle64KBSupported : 0
CrossNodeSharingTier : D3D12_CROSS_NODE_SHARING_TIER_NOT_SUPPORTED (0)
CrossAdapterRowMajorTextureSupported : 0
VPAndRTArrayIndexFromAnyShaderFeedingRasterizerSupportedWithoutGSEmulation : 1
ResourceHeapTier : D3D12_RESOURCE_HEAP_TIER_1 (1)
MaxGPUVirtualAddressBitsPerResource : 40
MaxGPUVirtualAddressBitsPerProcess : 40
Adapter Node 0: 	TileBasedRenderer: 0, UMA: 0, CacheCoherentUMA: 0, IsolatedMMU: 1
HighestShaderModel : D3D12_SHADER_MODEL_5_1 (0x0051)
WaveOps : 1
WaveLaneCountMin : 32
WaveLaneCountMax : 32
TotalLaneCount : 26624
ExpandedComputeResourceStates : 1
Int64ShaderOps : 1
RootSignature.HighestVersion : D3D_ROOT_SIGNATURE_VERSION_1_1 (2)
DepthBoundsTestSupported : 1
ProgrammableSamplePositionsTier : D3D12_PROGRAMMABLE_SAMPLE_POSITIONS_TIER_2 (2)
ShaderCache.SupportFlags : D3D12_SHADER_CACHE_SUPPORT_SINGLE_PSO | LIBRARY (3)

ADAPTER 1
"Microsoft Basic Render Driver"
VEN_1414, DEV_008C, SUBSYS_00000000, REV_00
Dedicated video memory : 0  bytes
Total video memory : 4294901760  bytes
Failed to create Direct3D 12 device
Error 887A0004: The specified device interface or feature level is not supported on this system.

FINISHED running on 2017-06-30 00:38:33
2 display adapters enumerated

Oops, I forgot that I am at 382.05...

 

So is this DX12 change a good thing?

 

WATCH_DOGS 2 crashes during loading for me with this driver, although oddly there's no error recorded in the Event log. I thought it might be triggered by MSI Afterburner v4.4.0 Beta 12 or RTSS v7.0.0 Beta 26 which I'm using but the game still crashes with an exception added for it.

 

Here is with new drivers

Code:

Direct3D 12 feature checker (March 2017) by DmitryKo
https://forum.beyond3d.com/posts/1840641/

Windows 10 version 1703 (build 15063)

ADAPTER 0
"NVIDIA GeForce GTX 970"
VEN_10DE, DEV_13C2, SUBSYS_136619DA, REV_A1
Dedicated video memory : 3221225472  bytes
Total video memory : 4294901760  bytes
Video driver version : 22.21.13.8476
Maximum feature level : D3D_FEATURE_LEVEL_12_1 (0xc100)
DoublePrecisionFloatShaderOps : 1
OutputMergerLogicOp : 1
MinPrecisionSupport : D3D12_SHADER_MIN_PRECISION_SUPPORT_NONE (0)
TiledResourcesTier : D3D12_TILED_RESOURCES_TIER_3 (3)
ResourceBindingTier : D3D12_RESOURCE_BINDING_TIER_3 (3)
PSSpecifiedStencilRefSupported : 0
TypedUAVLoadAdditionalFormats : 1
ROVsSupported : 1
ConservativeRasterizationTier : D3D12_CONSERVATIVE_RASTERIZATION_TIER_1 (1)
StandardSwizzle64KBSupported : 0
CrossNodeSharingTier : D3D12_CROSS_NODE_SHARING_TIER_NOT_SUPPORTED (0)
CrossAdapterRowMajorTextureSupported : 0
VPAndRTArrayIndexFromAnyShaderFeedingRasterizerSupportedWithoutGSEmulation : 1
ResourceHeapTier : D3D12_RESOURCE_HEAP_TIER_1 (1)
MaxGPUVirtualAddressBitsPerResource : 40
MaxGPUVirtualAddressBitsPerProcess : 40
Adapter Node 0: 	TileBasedRenderer: 0, UMA: 0, CacheCoherentUMA: 0, IsolatedMMU: 1
HighestShaderModel : D3D12_SHADER_MODEL_5_1 (0x0051)
WaveOps : 1
WaveLaneCountMin : 32
WaveLaneCountMax : 32
TotalLaneCount : 26624
ExpandedComputeResourceStates : 1
Int64ShaderOps : 1
RootSignature.HighestVersion : D3D_ROOT_SIGNATURE_VERSION_1_1 (2)
DepthBoundsTestSupported : 1
ProgrammableSamplePositionsTier : D3D12_PROGRAMMABLE_SAMPLE_POSITIONS_TIER_2 (2)
ShaderCache.SupportFlags : D3D12_SHADER_CACHE_SUPPORT_SINGLE_PSO | LIBRARY (3)

ADAPTER 1
"Microsoft Basic Render Driver"
VEN_1414, DEV_008C, SUBSYS_00000000, REV_00
Dedicated video memory : 0  bytes
Total video memory : 4294901760  bytes
Failed to create Direct3D 12 device
Error 887A0004: The specified device interface or feature level is not supported on this system.

FINISHED running on 2017-06-30 01:10:30
2 display adapters enumerated

 

So, is that a yes?

 

Not afaik , just weird.
Also with this new driver i can't start Watch Dogs 2 it just crashes to the desktop without any kind of notification.

 

good, this driver support now direc3d 12 DDI 12 on fermi at now?

 

From the Geforce forums for those with Watchdog 2 issues.

From ManuelG

 

Can anybody report on the Gsync 144Primary/60Hz secondary display frame drop/stuttering bug? Would like to update my 3 months old driver

 

yep and i just bought the game to give it a try, now i have to go back to .53 just to play this game

 

Yes. Higher binding tier allows the GPU to manage more assets without the need to use CPU to re-bind them when the slots are running out. Tier 3 basically has no limitations on the number of bound assets. This is a performance optimization.

 

So is this a hardware thing, or can it be done through software? I'm wondering why they waited so long to introduce it into the drivers. I mean, Maxwell v2 came out nearly 3 years ago.

That said, it's not as though we've had any games out recently that used the new binding model, so nothing was harmed by this delay.

 

Just clean installed these drivers after a DDU run. D3D12 resource binding tier did go from 2 to 3. Idle clocks dropped to 139MHz on the core, every driver since 378.xx through 382.xx had it at 165MHz. I noticed that the NVCP has the "allow experience improvement program" option under the help tab. Is that new?

As for DX12 games that may have benefited from these drivers, my benches for Gears 4 (built in bench) and both Forza's (custom route for benching) are exactly the same down to about 0.2 FPS difference at most. May try Hitman 2016 later to see if that is better or not against the 382 drivers.

Other than that, I'm going to keep using these drivers until I see a reason not to.

 

Some benchmarks:







Pretty solid performance with gains in most games tested, the only game which don't seem to like it much is RoTTR.

Well, it's becoming increasingly difficult to say what is h/w and what is s/w as both the h/w and the s/w complexity is rising and sometimes you can find new ways of using the same h/w. It is a bit surprising that they've found a way to extend this tier three years after Maxwell's launch but you should consider that DX12 was not their primary optimization target until Pascal launch so it's likely that we're looking at the results of about one year of full scale DX12 optimizations.