Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by michaelj, Jan 15, 2020.
So, perhaps there will be another insider driver
Peeps, we all know what the purpose of hardware scheduling is in relation to this driver but do we have any actual hard numbers that show whether this tomfoolery is actually benefiting us with relation to minimum/average frames attained within a gaming environment. Googling reveals lots of explanations but no hard numbers as to whether this feature is effective or not.
Can anybody shed any light on this? @Astyanax, you got any insight into this bro? I suppose that the biggest improvement, if any would be observed with low end gaming rigs!
The numbers are:
BUT there is one thing that I initially perceived as if hardware scheduling only makes things worse. Most likely this will be fixed on the release. But with the driver 450.12 (and older WDDM 2.7) in DirectX 12 games this function negatively affects the FPS. I even wrote about this in one of the old topics. But then it turned out that this problem is observed only with DirectX 12 games, and with DirectX 11 and Vulkan games the difference is exclusively for the better
Aaah!, Thanks @EugeneJackKhoros...
Your answer may go some distance in explaining why Shadow of the Tomb Raider bench results are within 1 frame of each other regardless of Hardware scheduling setting (on or off)... I have only done prelim tests using DX12 games. Categorically no synthetics... So the general advice regarding Scheduling is to leave it on if you have support for it?
The link you provided actually shows a substantial & impressive improvement when scheduling is active.
If your an Insider , on fast builds ,latest builds and drivers are part of the drill.
Tomorrow, the 450 driver will be officially released and will be published on the Nvidia website.
Source of this info bro, else it's nonsense in these here parts...
[QUOTE = "ReaperXL2, сообщение: 5770156, участник: 232418"]о_О
Источник этой информации, братан, иначе это чепуха в этих вот частях ... [/ QUOTE]
Sorry dude but I can't understand that.
'Manuel' is a noun in the English language that never the less leaves me & others still none the wiser to your previous statement regarding the release date for 450.12 WDDM 2.7.
Last vulkan 1.2 isnt working on this set. Or its just me? Neither wolfnein 2 neither doom 2016. Its only me or general?
he just rewrote what you said in russian.
He has no source. at all.
Just tried both of those games myself and it would appear that you are correct. Doom and Wolfy both refuse to use 1.2 Vulkan, instead referencing the native 1.1 that is installed with the driver.
This now leads us back to a previous question that i asked in an earlier post on this thread whereas red team drivers were manually updated with the vulkan runtime but steadfastly refused to acknowledge the update and again references only the vulkan api native to the driver package.
Contrary to this behaviour is the display of the current vulkan api installed which shows as 1.2 situated in wow64 system folder.
This proves that regardless of Vulkan API installed by a user or software, the gpu driver will only reference that which is native to the package, not what is installed within the system.
It goes some way to reveal just how much misinformation is being voiced in good faith but that ultimately results in a chaotic understanding of the hardware that we care so much about...
We need a definitive source for this information How else are we gonna make progress as enthusiasts trying to understand how our hardware functions?
I hope tomorrow we will see this driver when it is published on the official website of Nvidia.
these have never supported vulkan 1.2
OK. Thanks @Astyanax. Given my recent testing results your answer makes sense.
I'm posting my initial question and subsequent responses so that members may fully understand my latest comments regarding the vulkan api.
After reading through my original question and the answers I received, you can understand my wanting of a definitive source for this stuff...
I would expect a 445.xx driver long before we see an exclusive Windows version # 2004 driver release. Win version #2004 wont be out until next month I believe.
"While DirectX Ray Tracing and Variable Rate Shading are supported in Windows 10 today, Microsoft’s Windows 10 ‘20H1’ update will add DirectX support for Mesh Shading and Sampler Feedback, as well as update DXR to version 1.1. NVIDIA will be ready on the day of Windows 10 20H1 release with full driver support for all the new and updated DirectX 12 Ultimate capabilities."
I do believe the current 450 driver does not support either.
"Today, you can get started developing with DirectX 12 Ultimate features with NVIDIA GeForce 20 Series hardware. Driver version 450.56 has support for Mesh Shaders, VRS, DXR 1.0 and Sampler Feedback. DXR 1.1 support is coming very soon – we’ll update this blog with the correct driver version to look for and where to find it soon!"