FREE Next-Day Delivery on in-stock items over £50! Offer ends 5PM 28.10.21

Menu

Rated Excellent
4.8 star rating
Free delivery over £50
to most of the UK
0% interest for 4 months
on purchases over £99
Custom PCs built fast
delivered in 4-5 days
3 year on-site PC warranty*
including parts & labour

FREE Next-Day Delivery on in-stock items over £50! Offer ends 5PM 28.10.21

Review: NVIDIA GTX680 Review and Benchmarks

Martin takes the NVIDIA GTX680 to it's limits and pits it against some of the latest and most demanding games available today. Then overclocks it and does it again

Dirt 3

Dirt 3Dirt 3

Next up we have Dirt 3, this is the successor to the first DX11 title; Dirt 2. Dirt 3 is pretty much more of the same; you’ve got your different race types, ranging from rally, to one on ones, to your run of the mill first out of X wins. I’m not much of a racing game fan, but I’ve never had a problem having a casual play of either Dirt 2 or 3, they’re nice and easy to get into with a varying amount of difficulties.
For Dirt 3 I ran the Ultra preset at 1920x1080 with full screen while disabling Vsync. This gave, like Dirt 2 some of the better visuals I’ve experienced in a game, especially for a racing game.
Dirt 3 is notable for being one of few games that have AMD’s “variant” of Nvidia’s “Way it’s meant to be played” this was also the same of Dirt 2, with AMD handing out many Steam codes with their graphics cards. Here are the results I acquired for Dirt 3;

ResultsResults

It’s becoming obvious that the GTX680 is nothing short of an absolute powerhouse, it’s absolutely eating through any game I’ve thrown at it so far, there’s not too much to say about the results of Dirt 3, it’s obvious that the game is very optimised with their being barely any drop in frame rate and overall maintaining a very consistent performance, which was also obvious from playing through. I expect different maps to play differently, but I don’t expect any map in Dirt 3 to really challenge the GTX680.

Metro2033

Metro2033Metro2033

I’d never played Metro2033 before I used it for my review, so I wasn’t sure what to expect. I’d always heard that it was quite a monster to run and that it wasn’t very well optimised, but that was around the time that the 5870/GTX480 were the top dogs, so I expected things to run a lot better than I’d heard, unfortunately I was let down, but I’ll get onto that later.
I ran the game at 1920x1080 with everything on maximum, the game looked quite stunning, but I wasn’t quite a fan of the art style, games that are dark and depressing in a setting such as this aren’t my preference, I prefer my games to have a more vibrant colour pallet, anyway, here are the results that I was able to amass;

ResultsResults

The results this time don’t seem quite as stellar as the rest of the results that we’ve already seen. Since I don’t have a point of reference I’m not sure if it’s just a problem with the GTX680, or its just Metro2033 with some very GPU intensive features. I’d like to note that it’s quite possible that one may be able to change settings to retain pretty much the same IQ, but with much better performance, as that tends to be the case in some games as they have subtle but GPU dependant features. The frames that were being pushed out were far from unplayable, but I’d definitely prefer an average closer to at least 50.