This time, we’ll be trying out Windows 7 Professional, 64-bit. These are the results:

DirectX 9:

DirectX 10:

Since it’s variable benchmarks, the results vary from time to time, so that these two manage to match each other is not too shabby.

Edit: On an extra note, the CPU usage jumped to about 80-90% on DirectX 9 and 10, hmm… I wonder if being on 32-bit before had bottlenecked MT Framework’s ability to use 4 cores? Or was it that my readings back on Windows XP 32-bit for CPU usage were inherently bad?

This time, with a Core 2 Quad, Q6700:

Same settings as before.

If you want to know how CPU-bound this game is… on my E6600, the CPU usage was at 100%. On the Q6700, the CPU usage only spiked at about 35-45%.

On a sidenote, my temperatures were 25 degrees idle and 35 degrees load. I think it’s because I screwed up my thermal paste application earlier (using OCZ FreeZe), and now I got it right. Ambient is also 25 degrees celsius, so this is pretty insane.

This time, with a Geforce GTS 250 1 GB:

Interesting results. The game doesn’t look as visually impressive as Resident Evil 5. Then again, RE:5 was put out about 3 years later, so it’s somewhat unfair to compare the two. Using 190.38 Forceware, and settings were maxed (disabled AA, however).

I should note that the game boasts a Core 2 Quad logo at the beginning of the game when you start it. It also sports an nVidia logo.

Now if you haven’t gotten it yet, I suggest you do. Here’s my results for the Variable Benchmark:

Settings were 1680×1050, no AA, High on Shadows, Texture, and Overall Quality. Uncapped framerate, no V-Sync. ForceWare was the latest at time of writing, which is 186.18. Before I used 182.02 and CPU usage went from 90-100%, though the result then was 40.1 average FPS. 186.18 ForceWare puts it at most 80% CPU usage and 40.4 average FPS. I wonder if it has something to do with PhysX…