Regarding the whole quack mess... I had at least 4 conversations with Dave Nalasco on that issue and wrote a lengthy editorial about it at Rage3D. However, with what I have learned since then, I can safely say that Dave did not have all the info when he said what he said about ATI purposely doing what they did.
The reason he was saying that was because indeed... ATI did have Quake3 Engine specific code paths in their drivers. However the reduced IQ due to that code path in that one driver set was a bug. The reduced IQ was not intentional, and has been noted many, many time since then, the next driver set maintained the enhanced performance from the Q3 code path, without reducing texture detail.
ATI was incredibly poorly equipped to deal with the quake/quack issue from a PR standpoint... and while I think a lot of Dave and crew at ATI that was in constant contact with Many web sites, they should have figured out what was going on before they made statements about what was actually going on.
The reason he was saying that was because indeed... ATI did have Quake3 Engine specific code paths in their drivers. However the reduced IQ due to that code path in that one driver set was a bug. The reduced IQ was not intentional, and has been noted many, many time since then, the next driver set maintained the enhanced performance from the Q3 code path, without reducing texture detail.
ATI was incredibly poorly equipped to deal with the quake/quack issue from a PR standpoint... and while I think a lot of Dave and crew at ATI that was in constant contact with Many web sites, they should have figured out what was going on before they made statements about what was actually going on.