Not sure if anyone posted this already, I did a search and didn't find anything.
Futuremark published new guidelines for allowed driver optimizations:
It is prohibited to change the rendering quality level that is requested by 3DMark.
It is prohibited to detect 3DMark directly or indirectly. In its sole discretion, Futuremark may approve detection in order to fix a specified hardware error.
Optimizations that utilize the empirical data of 3DMark are prohibited.
Generic optimizations that do not violate the above rules and benefit applications in general are acceptable only if the rendering is mathematically consistent with that of Microsoft® DirectX® reference rasterizer.
Full Article: <A HREF="http://www.futuremark.com/pressroom/pressreleases/?092303" target="_new">http://www.futuremark.com/pressroom/pressreleases/?092303</A>
I think the biggest thing here is drivers aren't allowed to detect 3dmark is running, so that should stop application specific optimizations.
Futuremark published new guidelines for allowed driver optimizations:
It is prohibited to change the rendering quality level that is requested by 3DMark.
It is prohibited to detect 3DMark directly or indirectly. In its sole discretion, Futuremark may approve detection in order to fix a specified hardware error.
Optimizations that utilize the empirical data of 3DMark are prohibited.
Generic optimizations that do not violate the above rules and benefit applications in general are acceptable only if the rendering is mathematically consistent with that of Microsoft® DirectX® reference rasterizer.
Full Article: <A HREF="http://www.futuremark.com/pressroom/pressreleases/?092303" target="_new">http://www.futuremark.com/pressroom/pressreleases/?092303</A>
I think the biggest thing here is drivers aren't allowed to detect 3dmark is running, so that should stop application specific optimizations.