Thursday, March 21st 2019

NVIDIA Releases GeForce 419.67 Creator Ready Drivers

NVIDIA today surprised us with the curiously named GeForce 419.67 Creator Ready drivers. These are client-segment graphics drivers, and only support GeForce and TITAN graphics cards, and not a single Quadro product is supported. Their version numbering also aligns with the GeForce trunk. The way we read this, "Creator Ready" is a new moniker like the existing "Game Ready," and while the latter is timed to release with major AAA game launches, the former aligns with major productivity apps relevant to the client-segment that doesn't need too many professional features or certifications exclusive to the Quadro series. These drivers support GeForce GTX 10-series "Pascal," GeForce GTX 16-series "Turing," GeForce RTX 20-series "Turing," and TITAN products based on the "Pascal," "Volta" and "Turing" architectures. 900-series "Maxwell" support is removed.

These drivers introduce performance optimization for recently launched productivity applications Autodesk Arnold, Unreal Engine 4.22, REDCINE-X PRO, Adobe Lightroom, and Substance Designer by Adobe. The drivers also improve performance of existing applications. You can expect a 13 percent performance improvement with Blender Cycles, up to 9 percent with Photoshop CC and Premier Pro CC, and up to 8 percent with Maxon Cinema 4D. NVIDIA also added G-Sync certifications to ASUS VG278Q and VG258 monitors, which are adaptive-sync capable. Installing these drivers won't change the gaming feature-set of your existing drivers. These very much still are GeForce drivers, and your settings can carry forward.

DOWNLOAD: NVIDIA GeForce 419.67 Creator Ready Drivers

The change-log follows.

New Features
  • Added support for Surround using GSYNC-Compatible displays on NVIDIA Turing GPUs
  • Verified the following displays as GSYNC-Compatible.
    o ASUS VG278QR
    o ASUS VG258
  • NVIDIA Control Panel: Changed the default setting on the Manage GPU Performance Counters page.
  • [DaVinci Resolve]: Performance drop occurs. [2532482]
  • [Ghost Recon: Wildlands][Ansel]: The game experiences low performance and stuttering and then crashes when using Ansel. [2515076]
  • [HDR][Far Cry:New Dawn DirectX 11]: Desktop brightness and color gets overexposed with ALT + TAB when Windows HDR is disabled and in-game HDR is enabled. [200495279]
  • [Total War: Warhammer 2]: Poor performance when using antialiasing. [2506465]
  • [Adobe]: Artifacts may appear in Adobe applications (fixed for single-GPU case). [2533911]
  • [Apex Legends]: Screen gets corrupted when switching from windowed mode to full-screen mode when Windows HDR is enabled.[2523309]
  • [GeForce Experience]: Parts of the screen are cut off when recording video with Shadowplay. [2517587]
  • [Turing][Star Citizen]: The game flickers and then crashes to the desktop. [2518104]
  • [GeForce GTX 980]: NVAPI calls take a large amount of CPU time. [2418933]
  • [Titan RTX]: Graphics card rises about 20 degrees Celsius when running NVLINK command to enable TCC mode. [2504836]
  • [GeForce RTX 2080][Notebook][Resolume Arena 6]: The game exhibits slow performance. [2511725]
  • [GeForce RTX 2070]: With two monitors connected and active, the second monitor flickers. [2517103]
Add your own comment

13 Comments on NVIDIA Releases GeForce 419.67 Creator Ready Drivers

#1
Ferrum Master
  • [GeForce GTX 980]: NVAPI calls take a large amount of CPU time. [2418933]
Yet 900-series "Maxwell" support is removed.


Sure...
Posted on Reply
#2
R0H1T
Is that a fix or a new feature?
Posted on Reply
#3
Ferrum Master
R0H1T
Is that a fix or a new feature?
Actually the article fails to tell, that these are second WDDM 2.6 drivers(first were 421.65 through WU)

The full WDDM 2.6 feature set is not yet disclosed.
Posted on Reply
#4
Vayra86
Ferrum Master
  • [GeForce GTX 980]: NVAPI calls take a large amount of CPU time. [2418933]
Yet 900-series "Maxwell" support is removed.


Sure...
Yeah, I've seen Kepler fixes as late as 2H2018 :P

I think we should read that support EOL as a disclaimer. They don't have to anymore, but they just might. Common sense always wins... if they don't fix recent GPU issues, they lose customers.
Posted on Reply
#5
Regeneration
NGOHQ.COM
What is this 'Removed Maxwell support' nonsense? bastards.
Posted on Reply
#6
Ferrum Master
Regeneration
What is this 'Removed Maxwell support' nonsense? bastards.
That's called failed journalism. You cannot remove something where it wasn't in the first place. It is a whole new driver branch.

The correct phrase - not yet added.
Posted on Reply
#7
cyrand
Ferrum Master
That's called failed journalism. You cannot remove something where it wasn't in the first place. It is a whole new driver branch.

The correct phrase - not yet added.
On the other hand it more then likely it base on the same 419 branch the game ready drivers are based on. The process was likely optimize the the drivers for our newest architectures for the intended applications instead of games then remove support for the architecture we don't want to spend the resources optimizing for creators.

So the article wording not completely wrong depending on if you want to look at the creator branch as a new thing or just a derivative of the 419 base driver code.
Posted on Reply
#8
Gasaraki
So the question is, are they removing Maxwell support from all future drivers or just the 'creator's' line of drivers. The 'game ready' drivers will still have support for Maxwell?
Posted on Reply
#9
Ferrum Master
cyrand
On the other hand it more then likely it base on the same 419 branch the game ready drivers are based on. The process was likely optimize the the drivers for our newest architectures for the intended applications instead of games then remove support for the architecture we don't want to spend the resources optimizing for creators.

So the article wording not completely wrong depending on if you want to look at the creator branch as a new thing or just a derivative of the 419 base driver code.
I would not say anything if nvidia itself would have made the statement. It contradicts itself due to the fact, it includes fixes for 980. The branch added WDDM 2.6 function, and it is normal, they have not made every architecture compatible or tested it yet. So it includes support for Turing and Pascal. Prolly via inf mod you can make it work, but will the unknown WDDM 2.6 features work? It is unknown, as those are not even published yet, you may not even trigger the bugs.

The text about being removed is made up by someone, trying to make some sort of ripples, and then then copy pasted around the internet tech sites. It is low quality material.
Posted on Reply
#10
xtreemchaos
just installed and running sweet, i dont know if its me but ive just played 30min of fallout 4 VR to test its running my games allright and it looks to be a tad sharper.
Posted on Reply
#11
15th Warlock
Still no support for SLI in Anthem, wtf Nvidia?

The game actually runs better on my laptop than it does on my GTX1080 rig with SLI enabled, I have to manually turn off SLI before I start the game for it to run decently, that's ridiculous.

It's even more ridiculous when you consider the game was shown running at 60FPS 4K on an SLI 1080Ti setup before it was released, why did bioware and nvidia gimp SLI support before the game was released?

I know the answer to that, but it's so messed up they won't address this issue a full month after release when obviously the game was meant to support that feature, I know this was artificially handicapped to help sell more Turing cards, but come on Nvidia...

I know it sounds unrelated to this driver release, but I've been waiting patiently for a proper SLI profile since February, and Nvidia obviously solved some game related issues on this release, so it's not a driver for content creators only, no matter how hard they try to make it look that way...
Posted on Reply
#12
Vayra86
15th Warlock
Still no support for SLI in Anthem, wtf Nvidia?

The game actually runs better on my laptop than it does on my GTX1080 rig with SLI enabled, I have to manually turn off SLI before I start the game for it to run decently, that's ridiculous.

It's even more ridiculous when you consider the game was shown running at 60FPS 4K on an SLI 1080Ti setup before it was released, why did bioware and nvidia gimp SLI support before the game was released?

I know the answer to that, but it's so messed up they won't address this issue a full month after release when obviously the game was meant to support that feature, I know this was artificially handicapped to help sell more Turing cards, but come on Nvidia...

I know it sounds unrelated to this driver release, but I've been waiting patiently for a proper SLI profile since February, and Nvidia obviously solved some game related issues on this release, so it's not a driver for content creators only, no matter how hard they try to make it look that way...
Honestly, ditch that 2nd 1080ti while it still has value :p SLI is not going to last, its fast reducing to ultra niche. The entire midrange is cut out.
Posted on Reply
#13
15th Warlock
Vayra86
Honestly, ditch that 2nd 1080ti while it still has value :p SLI is not going to last, its fast reducing to ultra niche. The entire midrange is cut out.
Yes, it sucks, I mean, it was a neat proposition, buying a card, and then, when prices go down get a second card and increase your performance.

Sad to see support for multiple card rigs going the way of the dodo...
Posted on Reply
Add your own comment