I always save the best for last......
Image Quality Differences!!!!!!!!
ok, very few peeps will notice anything showed on this page.
yet it is clear that the biggest differances can be clearly seen in GT3....hair, sword
but take a look at what is said by Derek Perez:
""NVIDIA asked for a conference call with us to go over some of the points, and in general some of the responses from Derek Perez were fairly frank and honest. It would seem that NVIDIA agrees with tome of the optimisation policy that Futuremark have put in place, but not all as they don't necessarily tally with the internal policies that NVIDIA have. From the gist of the conversation it seems that NVIDIA feels that it is their right to optimise specifically for applications as long as it doesn't interfere with image quality - which is fine if it is benefiting games as it will benefit the end user, however in this case the image quality can be argued as there are differences in the image produce with the optimisations that NVIDIA have used in the 52.16 drivers for the 3.3.0 patch. Derek went on to suggest that they may well end up chasing each patch release and re-optimising as Futuremark puts a patch that defeats previous detections!
At one (point)we asked Derek how this sat with the optimisations guidelines that were given to press by NVIDIA, specifically the guideline that suggests "An optimization must accelerate more than just a benchmark" To which Derek's reply was "But 3DMark03 is only a benchmark" -- it was suggested that this particular guideline should read "An optimization must accelerate more than just a benchmark unless the application is just a benchmark"! ""(article was dated November 12)
hmmmm....Nov. 3rd, nVidia spells out there optimasation policy on "editors day":
We will continue to do application specific performance optimizations and compatibility fixes. We met with Futuremark and discussed the optimizations they questioned. Some of the optimizations (such as intelligent color clears and clip planes) they viewed as too aggressive, so we have removed them from our drivers. We have new, stricter guidelines in place to insure that questionable driver optimizations do not get introduced in future driver builds including:
An optimization must produce the correct image
An optimization must accelerate more than just a benchmark
An optimization must not contain pre-computed state
I realy like what follows on the same page....
""With respect to NVIDIA's optimisation guidelines, questions should be asked exactly how stringent they are being applied, or whether they are just for the purposes of appeasing the press. One the face of it here, the optimisations applied here appear to break all three guidelines - the correct images do not appear to have been produced with the 52.16 drivers, pre-computed state in the form of shader replacements appear to have been used (if this were part of a generic optimisation then it should not have been defeated by simply altering the order of instructions), and hence these optimisations would be specific to this benchmark only. Given that we first heard talk of NVIDIA's optimisations policy during the Detonator 4x.xx release of drivers there would appear to have been ample time to have removed these types of optimisations by now.""
full read
here.
mica