Althornin said:I'm curious why this sort of thing has been rejected in the past.
Wonder no more, DaveH - it was done by ATI in the not so distant past, and they got slammed for it, upon the release of the 8500, iirc, there was a driver set that didnt do "full trilinear" and ATI got hammered for it.
If you're referring to the "quack" scandal, what was going on there was that the 8500 was for some reason fetching really high mipmaps (i.e. mipmaps with far too little detail) for a handful of textures in Q3 which were nonetheless heavily used enough to make a big difference in both performance and IQ. Unlike the current issue, the IQ loss was extremely noticeable when it existed.
Also unlike the current issue, there is at least a reasonable chance that this "optimization" was in fact a bug on ATI's part. (Or perhaps a working optimization that for some reason failed for those particular textures. Or an optimization that worked fine on the R1xx but for some reason did not on R2xx. That is, there was definitely active app-detection going on, but one seriously doubts that the IQ results were what ATI was expecting.)
Meanwhile, the 8500 didn't do trilinear at all when AF was enabled. Obviously that was almost two chip generations ago (another way for saying, "just last chip generation") but it does go to show how far we've come to be worrying about problems with partial trilinear that apparently can't even be seen in most situations.
EDIT: And if you're referring to the fact that the 8500 didn't do trilinear at all when AF was enabled...it didn't do trilinear at all when AF was enabled! It wasn't a driver bug but a hardware limitation; AFAIK, the 9200 you can go out and waste your money on buy today will have the exact same behavior. And straight bilinear is way way more noticeable than this partial trilinear NV3x is using in UT2003.