The definition above is somewhat passable, although it should read may yield, not yields in terms of sharp textures as the way it is worded is improper in its implication that it will yield sharper textures which is certainly not a given. Although, by pure definitive standards anisotropic filtering only implies non square- all the rest is a byproduct of adjustments to the calculations afforded by the modified sampling pattern(barring an incorrect selection of LOD bias).
That definition however, is something totally different then what you prior post stated which was a LOD bias adjustment- increasing detail on textures while mentioning nothing at all about the modifed sampling pattern which is requisite of anisotropic filtering.
I did not realize that a pragmatic functional definition of something wasnt enough to satify most people around here. Apparently we need an all out technical definition or else we're entirely wrong. :roll:
Just because he didnt specify the sampling pattern doesnt mean that he doesn't know thats how it works. Even if he didnt, it barely even matters because his defintion is perfectly fine for 99% of the people who arent so anal as to chastise someone for not specifying each and every single nuance of the definition.
People turn on anisotropic filtering BECAUSE it sharpens textures. In fact, I challenge you to find a
real world situation where turning on AF will blur or otherwise make image quality worse.
The only thing a LOD bias will do is change the distance at which one mipmap is switched for the next.
And his quote was-
It allows textures to be rendered more clearly and is especially noticable at long distances and at sharp angles.
I think if you try real hard something may start to click for you.
Thats a brilliant deduction there sherlock. Just because an LOD bias change and AF are both noticible at long distances and sharp angles do not mean that anyone is mistaken as to which is which. LOD Bias is an ugly hack to sharpen textures. AF is a more proper way to do it. Some basic logic wouldnt hurt you know.
It makes a shimmering effect because of a lack of proper sampling for the frequency that the image is being displayed at. I assume by your tone that you must be an expert on signal theory and how it relates to texture sampling in a 3D environment, why word things like a moron? Don't hold back now, please expand on what it is you think constitutes proper anisotropic filtering and what sort of shortcomings current implementations have and why those shortcoming have been made in relation to performance not to mention their resultant impact on transistor budgets on current GPUs.
Again, the same BS. People dont come here for highly technical definitions that would be utterly useless to them. They want to know what things do, and what theyre for, and how they could be helped. You are doing nothing of the sort. I dont have the time nor inclination to seek out detailed specifications of the algorithms behind every 3d technology.
And as far as tone goes, you should keep in mind who was the one to imply that a certain someone was a fool.
These forums have archives, look in to the Vid card forum on this topic and use my name as a cross reference. BFG has seen my go off on enough people over the years because of their half witted, at best, comments on texture filtering to be quite aware of how it is I will respond. Anisotropic filtering implementations in particular is something I'm rather quite obsessed with and have been for years, BFG is also quite familiar with that.
Then perhaps maybe you should stick to the highly technical or video card forums where someone might find such obtuse knowledge of anisotropic filterings, which would be more than useful in an actual discussion of the theory behind it. This thread is certainly not that place.
I quoted nVidia's tech docs in that discussion including the amount of latency DD encoding took along with the amount of samples they used to generate the effect. All you had to do was go to nVidia's site and check it out for yourself.
And you're still wrong about it, and it had very little to do with the latency of DD encoding. We could dig that all up again, but in the end I had to leave that discussion because you were failing to listen to reason.
Because someone makes a moronic statement and insults a long time acquaitance of mine and I call them on it? Please. You want to debate the topic at hand feel free to do so.
There was nothing moronic about it, and while you may be pretty satisfied with yourself for calling someone out for not specifying the actual algorithm used, in the end, you're still the one who looks the fool.