If like us you are a fan of first-person shooters, then there is a good chance you have spent the better part of this year anticipating the arrival of Far Cry 2. Last week marked the release date for this awaited sequel, and so we immediately jumped in and bought our copy. However, rather than play the single player mission from start to finish and then go into some multiplayer action, we have been hard at work for bringing you this article.

As usual our in-depth performance review takes various ATI and Nvidia graphics cards and compares them in this new first-person shooter title. Having recently completed a similar article with Crytek's Crysis Warhead, we have been keen to see if Far Cry 2 is just as demanding.

The quality presets tested include Ultra High, Very High, and High, which will be tested at 1280x1024, 1680x1050, and 1920x1200 resolutions. The built-in Far Cry 2 benchmark tool has been used to test the various graphics cards, so you will be able to accurately compare your systems performance to ours.

Read the full review at:
http://www.techspot.com/review/123-farcry2-performance/

Please leave your feedback here. Thanks!

FarCry 2 is good and all... but it just feels like a console port, like many games that have been released in the past year. Too bad though, it could have been great.

There will surely be an SLI fix coming out soon. No way my GX2 can continue to perform so badly.

I would like to compare my system's performance to the performance of the computers on the far cry 2 techspot performance review, but the article does not specify whether the short or long ranch is used. Does anyone know which ranch was used? If I had to take a guess I would say that the long ranch is used.

Ranch Small was used.

How sure are you about that?

Relatively

If we had of used the long test you would only be able to read out the article now and not 3 months ago.

I'm pretty sure he knows what he's talking about. Steve was the writer of the article you are referring to

Ok, lol. I didn't realize that. Thanks for the help, bro. I'm guessing the reason my machine doesn't measure up is because i'm on a c2d and not a c2q. Oh, and not using DX10 also throws in another variable.