Far Cry 2 Dissected: Massive Amounts of Performance Data

AMD Driver Caveats and Major Open Issues

The issues with AMD's driver and hotfix for Far Cry 2 have been fairly public. The 8.10 driver didn't really deliver on some performance points while the first hotfix had some rendering issues. The next couple hotfixes fixed some things and broke others, and we still don't have a driver from AMD that gives us the results we want. The 8.11 driver only incorporates the final hotfix changes, but we will have to wait until a newer hotfix is released or 8.12 for any hope of a better experience on Far Cry 2 with most AMD hardware.

While people have been talking about the issues, we've spent quite a bit of time looking at this problem (and the AMD driver issues are one of the major reasons this article is as delayed as it is). And we'll lead off with the bottom line: the Radeon HD 4870 1GB is the only AMD card not in some way afflicted, and it also happens to be the card we would recommend for the best single GPU experience on Far Cry 2 at any setting except 2560x1600 with 4xAA. But that is not an excuse for the kind of horrific experience we've had with every single other AMD solution when playing this game.

The stuttering issue people have pointed out with AMD hardware is not an issue with the 1GB part in our experience. The rest of the line up suffers greatly from random hitches that aren't so much stuttering in our tests as they are temporary slow downs. We were also unable to test CrossFire, as CrossFire only works with 4xAA enabled. Even then CrossFire performance is erratic and stutters more than single card solutions (except for with the 4870 X2 or two 1GB 4870 cards that is). We aren't quite sure what the CrossFire issue is, but it seems clear that there is some graphics memory issue somewhere, and not only because of the huge discrepancy between the performance of the 4870 512MB part an the 1GB part.

In our tests, we initially wanted to take the 3 run average for each test. This was not something we could do with AMD hardware as even our benchmark sessions were marred with ridiculous stuttering and slow downs. We would have performance range from 25 to 55 frames per second on any given test. Rather than take the average, we decided to take the highest performance run for NVIDIA and AMD. It is worth noting that most of the performance results for NVIDIA were within less than a frame per second difference, so average versus max performance run isn't that different.

This does mean that our tests paint AMD hardware in a better light than the actual experience will be, at this point in time, with every card except the 4870 1GB. The average FPS data was just not usable as our line graphs looked more like sine waves than anything logical; nothing made any sense at all. Our choice to publish this article now is based on the fact that we absolutely expect AMD to fix their performance issues in Far Cry 2 as soon as possible. Far Cry 2 is a major title and AMD is a major GPU maker: there is simply no excuse for this sort of problem.

So the trade off for going forward with best-case scenario numbers is this page explaining the problems and a plea to AMD to change their approach to driver development for the good of the consumer.

Maintaining a monthly driver release schedule is detrimental to AMD's ability to release quality drivers. This is not the first or only issue we've seen that could have been solved (or at least noticed) by expanded testing that isn't possible with such tight release deadlines. Yes, consistent and frequent driver releases to improve compatibility and performance are a necessity, but doing anything to excess is a very bad idea. Moderation is key and AMD severely needs a better balance here.

We've been mentioning this as an issue in passing when it pops up and causes us problems, but this is starting to get ridiculous. It is one thing when previous fixes are broken or when older games fall off the grid and are neglected. But when a major title like Far Cry 2 is released to incredibly poor driver support, it is time to wake up and realize that something is wrong. This is not the first time we've seen issues with a newly released game, but the problems we've had with AMD drivers and Far Cry 2 are some of the worst we've ever experienced.

And this time it isn't just us. This isn't prerelease hardware or a beta software package. This isn't a quick fix "oops I forgot something" kind of bug. Though we tend to see problems a lot more frequently than end users, we do see a lot more issues with AMD drivers than NVIDIA. Even though not all those issues are things that we need to bother end users with, the probability of hitting a bug that will affect end users is much higher when you've got a higher number of bugs to worry about in general.

Now don't get me wrong, AMD drivers are still much better than they were before Catalyst. Back during the transition to Vista, ATI drivers were hands and feet above NVIDIA drivers for a long time (and they didn't hang XP out to dry either). AMD has maintained a unified driver model where NVIDIA had to break up their driver for different hardware generations for a while.

And now it is time for AMD to learn from their mistakes and change over to a more manageable and sensible driver release policy. Double the time between driver releases, do much much more testing across hardware platforms and games, and maybe even regularly release partly QA'd beta drivers in between WHQL drivers if there's something that needs a quick fix.