that's why we expect the parties determinant for the satisfaction of our preferences to play by the established rules (read stick to API definitions)
No, that's why I expect the parties determinant for the satisfaction of our preferences to
deliver a variety of products, such that we can choose a product that most optimially matches our needs.
you do realize the r200 deprived all those who prefer fligh-sims of proper visual experience, don't you?
As long as we're making blanket statements, you do realize that the NV20 deprived all those who perfer faster performance on FPS shooters the proper performance experiences, don't you?
specs are out there for a reason!
Right...and again, I ask you for the "specs" on advanced filtering techniques.
why do you think the whole human society is built upon perdictability, stated in social-order-enforcing laws???
Please don't tell me you you just made that analogy...
cool. email this opinion of yours to JC and read the answer you get from him carefully.
I don't have to e-mail him.
http://www.webdog.org/cgi-bin/finger.plm?id=1&time=20011117012727
Closely related subject: in his wrap-up, here's the important part, IMO.
I'm not fanatical on any of this, because the overriding purpose of software is to be useful, rather than correct,
As a DEVELOPER, I expect carmack to "desire" correctness for many of the reasons he mentioned in that .plan update. But in the end, "correctness" is not important.
Of course, we're not talking about "This is suppossed to render a green cube, but it renders a red sphere instead" type of "incorrectness. We're talking about performance / quality trade-off implementations.
The only real solution for Quake3 is to just disable TC entirely, or use DXT3 compressed textures.
