facebook rss twitter

NVIDIA rolls out GeForce 301.42 WHQL drivers

by Parm Mann on 23 May 2012, 11:39

Tags: NVIDIA (NASDAQ:NVDA)

Quick Link: HEXUS.net/qabg3v

Add to My Vault: x

NVIDIA driver updates don't come around as quickly as we'd hope - the last release dates back to early March - but when a new driver does become available it tends to pack a fair few upgrades.

This week, GeForce users are being treated to version 301.42, the first WHQL-certified unified driver from the R300 family of driver.

The new release supports all 8-series GPUs and beyond (including the new 600-series range) and introduces a long list of improvements that includes performance gains of up to 20 per cent in certain games, expanded 3D Vision support, over a dozen updated SLI profiles, added support for four-way SLI using the GeForce GTX 670, and a collection of single- and multi-GPU bug fixes.

Following on from last month's beta release, the WHQL driver retains support for NVIDIA's high-speed FXAA algorithm, as well as Adaptive VSync and Frame Rate Target, and NVIDIA has a lengthy blog post extolling the virtues of FXAA sampling that you may find interesting.

Head over to GeForce.com if you're ready to pull down the 160MB update, and if you've already made the transition, let us know how you're getting on in the comments below.



HEXUS Forums :: 14 Comments

Login with Forum Account

Don't have an account? Register today!
Really great to bring features like Adaptive V-Sync and frame rate cap to owners of older cards. Well done nVidia!

FXAA is kind of outdated now though, especially given it's only v1 that's in the control panel. MLAA v2 is slightly better, but SMAA is far superior.
Adaptive V-Sync is awesome. Understanding the different types of AA is OTOH a PITA, it's so confuzzling….
Pleiades
Adaptive V-Sync is awesome. Understanding the different types of AA is OTOH a PITA, it's so confuzzling….

Hexus should write an accurate and comprehensive article on it….
Anti-aliasing has always been a tricky one to explain… even back when there was only one generally used method.
Steve
Anti-aliasing has always been a tricky one to explain… even back when there was only one generally used method.

That's why I'm asking for an article from the pros at Hexus rather than suggesting we forumites pile in ;)