Quitch said:
Which is exactly why asking for a way to disable it at this point seems a little premature. Why disable a good as/higher IQ + higher performance method, except through not really understanding it?
I don't think the cry should go out for such an option unless the method is found inferior, which so far it hasn't. Even if it is, who's to say this isn't one or two easily correctable cases? Some people seem obsessed with maintaining very old tech because they understand what it does. "I know what tri does so I wish to force it because tri is best." It's living in the past.
So, because you don't get why people would like to disable trylinear, you want to impose your point of view on others so they can't disable it?
Choice is always power. It's not the fact that we want to disable it, we want to have the choice. We can try it on/off, probably decide that we want it on and be very happy with it.
You have to remember, it's in human nature to yearn for what you can't have. People are rarely satisfied with what they have. By removing the option for full trilinear, ATI is making it more desirable than it should be.
ATI have already stated that the driver is already running an analysis in software (at texture upload time) and sets a flag or variable to enable/disable trylinear for that texture in hardware. I bet it's not even going to cost them
one miserable man/hour to put an "if registry entry exists then set trylinear flag to 0". Come on. One man hour is
very generous . They'd need maybe 20 minutes to implement the option and 40 minutes to test it.