3dmark 2003 score, compare this!

[NEVERwinter]

waah?!?!
compare these:

MINE
http://service.futuremark.com/compare?2k3=318410

and
THIS GUY
http://service.futuremark.com/compare?2k3=137848

how can he got nearly 200 fps in game1???? o.o curious.... EDIT: uh.. yeah.. more than 200!

 

[kylebisme]

nearly 200? he got 247, and he obviously did something fishy to get there. you can hack any benchmark you know, unless you see the test run yourself or know someone you trust did you might as well take it with a grain of salt.

 

[Don Vito Corleone]

No way. My system benches over 4000 on 3DMark03, and I still got way less than 247 fps on Game 1. This seems like an error all around.

 

[Metalloid]

Not only that, but look at his overall score and his scores on the 2nd and 3rd game. You don't get 250fps in game one and 7.4fps in games 2 and 3.

 

[NesuD]

well his project name does include the sentence "nice little bug in 3dmark2003" wonder what the bug is

 

[ArmchairAthlete]

Maybe he is teh 1337 h@x0r

 

[jiffylube1024]

Originally posted by: NesuD
well his project name does include the sentence "nice little bug in 3dmark2003" wonder what the bug is

Yeah first thing I noticed too... it's pretty obvious.

 

[NEVERwinter]

yeah.. i wonder what the bug is ;/ first I thought it's caused by R8500 BIOS on LE card.. but then I realize that I also using the same BIOS for my LE card LOL

 

[dfloyd]

This definatly doesnt say alot about using 3dmark as a benchmark anymore. Not that there was not enough contreversy (Spelling?) before this. Now you got a way to trick the system into giving more fps. Wonder if Ati will release a driver that does this soon

 

[Gariputo]

Could be this bug (Neowin)?:
Bug in 3DMark 2003, cheating is imminent?

Although the scores here seem way higher.

 

[Goi]

Interesting that you should mention the Neowin bug...I've noticed this myself while I was checking my overclocking stability. I'd launch at some clockspeed to test for any immediate artifacts in Game 1, then abort the benchmark, increase the clockspeed, then test again. After I settled for the highest stable clockspeed, I ran the benchmark fully and submitted the score, but it'd report my initial clockspeed...

 

[kylebisme]

Originally posted by: Gariputo
Could be this bug (Neowin)?:
Bug in 3DMark 2003, cheating is imminent?

Although the scores here seem way higher.

ya, cheating is bound to be possable in any bechmark. any benchmark that you didnt not watch yourself or at was watched by someone you trust should always be taken with a grain of salt.