Quote:
|
if u condone cheating at this level, where will it stop?
|
How are we to know this "cheat" is nothing more than a simple error in nVidia's mipmapping routine? Am I to believe it is a "cheat" because a couple of hardware sites opted to run this story for whatever reasons? You can witness that this article did not appear in TechIMO's front-page news for Friday.
Such a simple mipmapping error has happened before on many occasions dating all the way back to the earliest 3dfx 3D cards, why not again? All it takes it a slight deviation in a complex mathematical calculation, or a numerical truncation too early in the pipeline, or a slight rounding problem, or.... you get the point.
ATI has also been found (even admitted) optimizing drivers for FutureMark benchmarks (among other popular 3D programs) over the past months, but no media sources seem to ever discuss those "cheats." Sadly, this is because most media review sites have to directly negotiate with ATI to obtain review hardware. In contrast, these same sites can often bypass nVidia and go straight to board vendors to acquire nVidia review products. I hope everyone sees a distinct difference in those two scenarios from a media standpoint.
Even worse, companies like Trident have used driver-level auto-detection routines to determine when the 3DMark executable was being loaded to enact a set of render "optimizations" that make nVidia’s "cheats" appear to be legitimate features in comparison. Forget about mipmapped textures, how about whole missing frames?!
Robert Richmond