Brent said:
ShaderMark has an Anti-Detector mode, to prevent just that.
And you are sure that there is no way to
work-around it in any drivers? You should know by now that there is no 100% bullet-proof anti-detector system.
Brent said:
D3D RightMark supports many more features than 3DMark, it has various PS/VS modes you can use and lots of specific tests of 3D hardware performance.
Many more features as in options, or more theoretical tests, or what do you mean?
Brent said:
Plus, both don't try to be something they are not.
They are put out there as pure synthetic tests, not as a synthetic test trying to represent game performance.
3DMark represents many things. Do read the whitepaper if you think 3DMark is representing only game performance. FYI, 3DMark03 has more to offer than only the Game Tests.
Talking about this (synthetic vs game benchmarks) reminds me of the days when 3DMark2000 and 2001 were released, and the discussions I had with various members over at 3dfxgamers.com..
Oh those days...
Brent said:
the new beta 4 of 3DRightmark adds support for ps/vs 3.0, it also supports ps/vs 2.x with dynamic flow control
Using Beta versions of benchmarks is something I have never understood. Beta means that it is beta, and that the final release might have some big changes which could affect the results. It is like you would use leaked beta (or even alpha) versions of games as timedemos, and make conclusions out of that. IMHO, doesn't work at all. Besides, how many released graphics cards do you know that support PS/VS 3.0?
Bouncing Zabaglione Bros. said:
All the more reason to put this function directly into the application instead of just crossing your fingers and hoping people will follow the rules. Heck, your own 3DMark members don't follow your guidelines - maybe you should start cleaning that up before worrying about reviewers?
Putting some new anti-detect system into 3DMark would be possible, but as we have discussed several times before, there is no 100% proof system. :? Until someone comes up with a perfect solution which works 100%, it is not a very feasible option. If 3DMark would detect driver versions and inform the user if the driver is approved or not, it would mean that we would need to patch 3DMark everytime a new driver is released and approved..
{Sniping}Waste said:
Nick put a thread in the futuremark 3DMARK 03 fourm for ppl to post site that are using un approved drivers so others can help you out.
That might help us to find more reviews using non-approved drivers with 3DMark03, but I am still sure that we need to prevent the use of non-approved drivers with 3DMark03 rather than waiting for reviews to be posted, and then contact them. Don't you agree?