- Page 1 nVidia GeForce GTX 280
- Page 2 GT200: Graphics Architecture
- Page 3 Counter-Strike: Source
- Page 4 Call of Duty 4
- Page 5 Enemy Territory: Quake Wars
- Page 6 Race Driver: GRID
- Page 7 Crysis
- Page 8 GTX 280: Test Setup
- Page 9 GTX 280: The Card
- Page 10 GT200: GPGPU Architecture and Other Features
- Page 11 GT200: Graphics Architecture
- Page 12 Verdict
Call of Duty 4 has to be one of our favourite games of last year. It brought the Call of Duty brand bang up to date and proved that first person shooters didn’t need to have the best graphics, or the longest game time. It was just eight hours of pure adrenaline rush that constantly kept you on edge.
We test using the 32-bit version of the game patched to version 1.4 FRAPS is used to record framerates while we manually walk through a short section of the second level of the game. We find a framerate of 30fps is quite sufficient because, although the atmosphere is intense, the gameplay is less so – it doesn’t hang on quick reactions and high-speed movement.
All in-game settings are set to their maximum and we test with 0xAA and 4xAF. Transparency anti-aliasing is also manually turned on through the driver, though this is obviously only enabled when normal AA is being used in-game.
For some reason this game simply didn’t benefit that much from the various improvements made to GT200 and it is simply trounced by the 9800 GX2. We suspect this is largely due to Call of Duty 4 being a DirectX 9 based game so it is benefiting little from the more DirectX 10 orientated tweaks applied to GT200. It still runs absolutely fine though.