Why not? I can just label the article "A study on NVIDIA's Beta Detonator 50 drivers" and it can be about certain NVIDIA GFFX cards, with some image output comparisons of HL2 with ATI cards, to show any possible image output differences between ATI DX9 and GFFX cards.Joe DeFuria said:Reverend said:Don't get all upset now... I was thinking in terms of a possible article detailing why the beta Det50s is like what Gabe described ("optimizations that may go too far"), i.e. what NVIDIA is doing with the beta dets. Not in reviews.
How can you do an article like that without testing the drivers? Me confused.
And if something odd is happening, then the report is made in the article. It would be hard, for instance, to mistake lack of precision for a bug.I mean, it can be equally unfair to nVidia, if you start picking out things as quality comprimises which actually turn out to be bugs and are fixed in the official release. In short, I just assume you stay away from unlreased drivers in general.
Surely we have all seen stuff described by NVIDIA as "bugs" in their official drivers... do we know if they are indeed bugs, do we take their word for it, even if the drivers are official?
If NVIDIA hands reviewers drivers that cannot be made available to the public, perhaps it may be a good idea for a reviewer to find out the reason why exactly these drivers are not public, and reveal their findings. I mean, you're not the slightest bit interested to know why NVIDIA gives these beta drivers to reviewers just for HL2 testing? You're not interested in an article that attempts to corroborate Gabe Newell's words about "optimizations gone too far"?Once they are released, then they can be praised (or bashed) for their performance / quality improvements (or degredations.)
The point is, such articles are fine as long as the point is made about what exactly is the nature of the article.