New Release 275 Drivers & The Test

Launching alongside the GTX 560 will be the newest branch of NVIDIA’s GeForce drivers: Release 275 beta. This actually comes hot on the heels of Release 270, which came out only a month and a half ago.

Unlike Release 270 NVIDIA isn’t making a lot of performance promises, so this is mostly a feature release. The big item in 275 for most gamers will be further refinements to the auto-update mechanism first introduced in 270. NVIDIA has finally fully ported over Optimus’ auto-update feature, meaning that NVIDIA’s drivers can now automatically find and install profile updates in the background. However whereas Optimus profile updates were necessary for switchable graphics, for desktop users the primary purpose of auto-updating profiles is for SLI and anti-aliasing compatibility, as NVIDIA uses compatibility flags in their profiles to make those features work.

Automatic profile updates won’t completely absolve SLI from periods of incompatibility, but it should help. NVIDIA has released out of band profile updates for SLI before, but these were rather rare. If they now release profile updates much more frequently, then this will be a boon for SLI users, particularly GTX 295/590 users. Otherwise SLI is mostly limited by what can be done with a profile – if NVIDIA has to update the driver itself, then users will still need to wait for a new driver release. Which on that note, NVIDIA hasn’t changed the auto-update procedure for the drivers: profiles will auto-download and install, but driver updates must still be manually approved.

NVIDIA tells us that in the future they will also be able to deliver 3D Vision compatibility updates with profiles, but this will probably require a bit of a rearchitecting to their drivers and profiles. Currently NVIDIA’s profiles contain a few flags for 3D Vision (mainly whether it’s allowed), but there aren’t any sweeping compatibility bits as there are for SLI and AA.

Moving on, the other big functionality update with 275 is a new resizing and scaling UI in the NVIDIA control panel. The core functionality of scaling hasn’t changed much as NVIDIA has offered these controls for quite some time, but now scaling controls are available for VGA and HDMI displays, versus just DVI and DisplayPort as it was previously. There’s also a new override option or Windows 7, for forcing misbehaving programs to use NVIDIA’s scaling options instead of their own. (Ed: We’ve never actually encountered this before. If you know of any games/applications that need this option, please let us known in the comments)

As for resizing, NVIDIA has tweaked the UI to help better guide users through using overscan correction and/or disabling overscan on their TVs. The ideal method of dealing with overscan is to disable it on the TV (thereby ensuring 1:1 pixel mapping), which is what NVIDIA now first directs users toward. For users that can’t disable overscan, they can then unlock NVIDIA’s resizing controls. NVIDIA tells us that they’ve also done some work to improve resizing compatibility for games/applications that try to force standard resolutions, but we have not had an opportunity to test this yet.

The Release 275 betas should be available later today, with WHQL drivers appearing within a month.

The Test

As we mentioned in our introduction, the lack of any reference-clocked cards means that the GTX 560’s clocks – and thereby the GTX 560’s performance – is not well rooted. As a result we’ve tested our ASUS GTX 560 DirectCU II Top at a few different clockspeeds. We’ve tested the card at NVIDIA’s reference clocks of 810/4004 (GTX 560 Base), along with the slowest "mid-grade" card on NVIDIA’s release list: 850/4104 (GTX 560 Mid). NVIDIA is pitching the GTX 560 as their $199 card, so for the purposes of our review we’ll be focusing primarily on the mid-clocked GTX 560, as this is the approximate speed of most of the $199 cards. If you buy a $199 GTX 560 today, this should closely represent the speed of the card you’re buying.

Ideally 810/4004 cards will be relegated to the OEM market, but if not we also have the base clocks included for appropriate consideration. It goes without saying that we’d rather NVIDIA just create two different product lines rather than having so many cards under the same umbrella, but at this point we’re just repeating ourselves.

We’ve also included our overclocking results with the ASUS GTX 560 DirectCU II Top, colored in orange. As we were only able to reach 950/4400, the performance gains are limited.

For drivers, on the NVIDIA side we’re using 275.20 beta for the GTX 560, the GTX 460 1GB, and GTX 560 Ti. In practice the average performance difference between release 275 and release 270 is around 1% in favor of 275. On the ATI side we’re using the Catalyst 11.5a hotfix; however do note that in our testing we’ve found that performance is identical to the 11.4 drivers.

CPU: Intel Core i7-920 @ 3.33GHz
Motherboard: ASUS Rampage II Extreme (X58)
Chipset Drivers: Intel 9.1.1.1015 (Intel)
Hard Disk: OCZ Summit (120GB)
Memory: Patriot Viper DDR3-1333 three x 2GB (7-7-7-20)
Video Cards: AMD Radeon HD 6970
AMD Radeon HD 6950 2GB
AMD Radeon HD 6870
AMD Radeon HD 6850
AMD Radeon HD 5870
AMD Radeon HD 5850
AMD Radeon HD 5770
AMD Radeon HD 4870
NVIDIA GeForce GTX 580
NVIDIA GeForce GTX 570
NVIDIA GeForce GTX 560 Ti
ASUS GeForce GTX DirectCU II Top
NVIDIA GeForce GTX 550 Ti
NVIDIA GeForce GTX 480
NVIDIA GeForce GTX 470
NVIDIA GeForce GTX 460 1GB
NVIDIA GeForce GTS 450
NVIDIA GeForce GTX 285
NVIDIA GeForce GTX 260 Core 216
Video Drivers: NVIDIA ForceWare 262.99
NVIDIA ForceWare 270.51 Beta
NVIDIA ForceWare 275.20 Beta
AMD Catalyst 10.10e
AMD Catalyst 11.4
AMD Catalyst 11.5a
OS: Windows 7 Ultimate 64-bit

 

Meet Asus’s GTX 560 DirectCU II Top Crysis: Warhead
Comments Locked

66 Comments

View All Comments

  • TheJian - Wednesday, May 18, 2011 - link

    See my other posts. Nvidia finally got multithreaded rendering finished in their drivers (which should affect many games now, it's not GAME specific). Expect AMD to get theirs done soon. This isn't Civ5 or Anandtech favoring NV, it's just the beat AMD to the punch in getting drivers finished. If AMD takes another year to get their drivers done, I'm glad they report this. I hope AMD gets them done soon, or the next set of cards that get benched might show quite a few games with AMD bunched at the bottom of the list.

    NOTE: this is a DRIVER issue, not game issue. Both sides have been working on getting this in their drivers for a while. It's about time :) The game had this in it all the time (many other too, get ready for speedups if you own NV and running 2.75 drivers (whatever is latest from NV). Unfortunately my 5850 has to wait for AMD. :(
  • JarredWalton - Tuesday, May 24, 2011 - link

    You know what the best part is about Civ5? AMD is the one that gave out copies of the game to reviewers. Yup -- that and F1 2010.
  • L. - Thursday, May 19, 2011 - link

    Errr/ metacritic lol ?

    We're talking benchmarking here, not playing the game.

    AMD being poor is their problem, we shouldn't care ;)

    Besides, the way people rate on metacritic or any critic source for anything is at most a relative indicator of how people who take the time to vote feel about stuff... doesn't help that much does it ?

    Crysis 2 is NOT in the same series as Crysis 1. If you don't know why, read some more about it.
  • L. - Thursday, May 19, 2011 - link

    Two words for you mate, Bench and Mark
    The purpose of benchmarking is to get a relative idea of the performance of a component, not to test every little game out there, because of that reviewers attempt to have a most relevant panel of games/ benchmarks to test the gfx cards.

    Crysis 2 is not (yet) a relevant benchmark. Maybe when they're done writing the engine for PC's it will be, but now it's just a worthless console port.

    IF you think they're lazy, just post a list of the games you would use to benchmark and ask people how useful they find those.
  • Spoelie - Wednesday, May 18, 2011 - link

    Metro 2033 is a game that requires the force scaling flag I believe. It ignores the scaling settings in AMD's drivers on windows 7 at least..

    Coloring is wrong on the Civ5 graph (last one)
  • GeorgeH - Wednesday, May 18, 2011 - link

    Taken out of the noise of the other comment stream:

    "RE: Time to change the tests by Ryan Smith on Tuesday, May 17, 2011
    The test suite is due for a refresh, and will either be updated at the end of this month or next month once we build our new SNB testbed."

    Weren't you waiting for SNB-E? Isn't that a Q4 release? Or by "SNB" do you mean "Bulldozer" and know something that we don't?

    You've got me all curious and maybe excited and more curious and now I-don't-know-what-to-think.

Log in

Don't have an account? Sign up now