gkar1 said:I really was not surprised by the blatant cheating, its the hypocrisy of the company, first attacking the benchmark and now cheating to get a better score. Complete lack of ethics. Sad thing is the fanbois(reviewers and consumers alike) will turn a blind eye to it.
doesn't anyone else think 3dMark is silly. its becoming less and less representative of actual real-world performance, and it's vulnerable to this sort of cheating.
dream caster said:8)
the one million dollar question:
Can this "bug" be related to GF5900 advantage in Doom3 demo?
nelg said:Perhaps this shows why 3Dmark03 is a good bench mark. If you have the pro version you can see who's been naughty and who's been nice.
its a mighty big coincidence, eh, that the driver bug just happens to not screw up really while the camera remains "on track", but the minute you leave it, it looks like you are playing doom2 with "noclip" and are running around outside the level.BenSkywalker said:I know nVidia's driver team it thought of very highly, but do people really consider them so good that this couldn't possibly be a bug? Not saying that it is, but why would they screw up GTA Vice City in the same fashion? Doesn't have a bench that I'm aware of.
Solomon said:It would be a hard sell to sell that the Doom III scores could of been inflated because of this anamoly with the 44.03. The reason ID supervised the results. So if it did in fact happened in Doom III. It wouldn't make ID very credible in some aspects. Just my two cents.
I know nVidia's driver team it thought of very highly, but do people really consider them so good that this couldn't possibly be a bug?
Althornin said:its a mighty big coincidence, eh, that the driver bug just happens to not screw up really while the camera remains "on track", but the minute you leave it, it looks like you are playing doom2 with "noclip" and are running around outside the level.BenSkywalker said:I know nVidia's driver team it thought of very highly, but do people really consider them so good that this couldn't possibly be a bug? Not saying that it is, but why would they screw up GTA Vice City in the same fashion? Doesn't have a bench that I'm aware of.
Too big of a coincidence to really swallow, imo.
But what if it's deliberately drawing the sky first in order to create a more stressful benchmark? Sure, there probably are better ways to do that, but that's irrelevant. 3dmark was created to run in a certain way in order to provide repeatable, comparable results across a variety of vidcards. Cheats which circumvent those methods are inexcusable.Uttar said:And heck, anyone drawing the sky before everything shouldn't expect GPU companies not to cheat IMO. It's just too unoptimal.
I don't really think that not clearing the colour buffer is really critical. . . UT by default doesn't clear it, at least in OpenGL. That was one of the problems I encountered while trying to create a "wallhack" cheat (never actually used online). I think it's the same for a lot of engines and demos, actually. . .Uttar said:The buffer clearing problem surprises me most however. From the looks of the screenshot, it seems like they're still clearing Z, but not color. Odd, considering the NV3x got Fast Color Clear. So yes, they're cheating, but I'd be surprised if they got more than a 3% boost from that.