Bug in 3DMark 2003, cheating is imminent?

Irs2k3 · 02-15-2003, 07:46 PM

1) Set your 3D card at default clock with your favourite overclocking utility
2) Open 3D Mark 2003
3) Start benchmarking, then press Escape so that benchmarking can't finish.
4) Now open your favourite 3D card overclocker again and overclock it like there's no tomorrow
5) Benchmark again, but this time let the benchmark finish
6) Publish your score to the Online Browser for the world to see

If you look carefully, you will see that the 3D Card clock that is being reported is the one you had when you started 3D Mark, and not the actual overclocked values that you used. So it seems that 3D Mark checks for the clock when it starts and NOT when it benchmarks! As you can easily realize, unless this flaw is patched, there is no way you can tell whether the scores you see are coming from overclocked cards or not. I guess FutureMark should move swiftly now and patch this version

02-15-2003, 07:55 PM

This bug has existed since 3dmark '99. Not really a bug, but rather an oversight. You can do this in MANY benchmarking programs. And some games respond strangely to a CPU speed change.

Try this in Unreal, for instance, with a CPU overclocking utility like Soft FSB.

MoPhat · 02-16-2003, 12:06 AM

Thanks for pointing this out, irs2k3. I never knew this...

You've added to this knowledge box on top of my shoulders.

Irs2k3 · 02-16-2003, 06:15 AM

Quote
This bug has existed since 3dmark '99. Not really a bug, but rather an oversight. You can do this in MANY benchmarking programs. And some games respond strangely to a CPU speed change[/b][/quote] Your wrong, If this "Oversight but its still a bug " exist why they didnt fix itsince 3dmark99. suffice to say that 3dmark03 still has some bugs, we will wait and see...

02-15-2003, 07:46 PM	#1 (permalink)
Irs2k3 is on the 1st circle: Limbo Join Date: Nov 2003 Posts: 17 Hellbux: 36,064	1) Set your 3D card at default clock with your favourite overclocking utility 2) Open 3D Mark 2003 3) Start benchmarking, then press Escape so that benchmarking can't finish. 4) Now open your favourite 3D card overclocker again and overclock it like there's no tomorrow 5) Benchmark again, but this time let the benchmark finish 6) Publish your score to the Online Browser for the world to see If you look carefully, you will see that the 3D Card clock that is being reported is the one you had when you started 3D Mark, and not the actual overclocked values that you used. So it seems that 3D Mark checks for the clock when it starts and NOT when it benchmarks! As you can easily realize, unless this flaw is patched, there is no way you can tell whether the scores you see are coming from overclocked cards or not. I guess FutureMark should move swiftly now and patch this version

02-15-2003, 07:55 PM	#2 (permalink)
Falkentyne Posts: n/a Hellbux: 0 [Check]	This bug has existed since 3dmark '99. Not really a bug, but rather an oversight. You can do this in MANY benchmarking programs. And some games respond strangely to a CPU speed change. Try this in Unreal, for instance, with a CPU overclocking utility like Soft FSB.

02-16-2003, 12:06 AM	#3 (permalink)
MoPhat is on the 1st circle: Limbo Join Date: Jan 2003 Posts: 18 Hellbux: 955	Thanks for pointing this out, irs2k3. I never knew this... You've added to this knowledge box on top of my shoulders.