toyota
Lifer
- Apr 15, 2001
- 12,957
- 1
- 0
theres plenty of evidence that the benchmark is off for me and others. if someone is getting in the 20s with a gtx285 and dedicated 9600gt for physx and I am getting the same or higher with my plain gtx260 then yes the benchmark is flawed. also like I said I can get wildly different max framerate number just doing the test back to back. this is true on both computers I have ran the built in benchmark on. its just a flythrough and can be very inaccurate.In your case you had your CPU @ 1.8ghz turn out faster results next and slower on another day. Seems to me that is inaccurate when you don't get the same consistent results as you are testing different scenarios on different occasions.
While I got consistent results and eliminated the anomaly. You spent hours on a demo and benchmark? Perhaps you should play the game and stop concentrating on benchmark numbers as I have no problems playing the game with my cpu @ 2.2ghz or 3.045ghz. Then again I have GTX260 216SP @ faster clocks and pulling faster frame rates than you with your E8500 and GTX-260 192SP @ lower clocks.
If you don't use the built in benchmark that's fine but you used built in benchmark in RE5 only to test CPU portion of this test where it's not testing actual game play. And you have NO evidence of Batman benchmark being flawed. Then again reviewers like legionhardware used the exact same benchmark in their reviews. All benches have some margin of error BUT I've eliminated these anomalies to give you consistent results on mine.
I only used the RE5 benchmark because it seemed to be very consistent when doing repeated runs. you are right though that it wasnt reflective of how good the actual gameplay is. in the actual game I rarely go below 40-45 fps with my cpu at 1.8 and only during lots of enemies do I dip below 40. I think what little sluggishness I feel is just the game itself. with my cpu at 3.16 I rarely come off below 55-60fps even when using vsync though. either way the game does play well and that fixed benchmark is a worst case scenario.
Last edited: