Post
The technique that keeps textures from turning into a blurry or shimmering mess when viewed at angles or distances.
When a textured surface is viewed at an angle or from far away, each screen pixel covers multiple texels (texture pixels). Without filtering, the renderer must pick a single texel, producing ugly shimmering and aliasing. Bilinear filtering smooths this by averaging nearby texels, but surfaces viewed at steep angles still look blurry because it samples a square region when it should sample a stretched one. Anisotropic filtering fixes this by sampling along the direction of the surface's tilt, preserving sharpness on angled surfaces like roads stretching into the distance or floors viewed from a low camera. The quality difference between bilinear and 16x anisotropic filtering is immediately visible on any surface that recedes from the camera, and the performance cost of anisotropic filtering on modern GPUs is essentially free.
Example
In any racing game like Forza Motorsport, the road texture stretching into the distance is a perfect test case. With bilinear filtering, the road becomes a blurry smear past the car's hood. With 16x anisotropic filtering, lane markings and asphalt detail remain crisp all the way to the horizon. The original Quake (1996) shipped with only nearest-neighbor filtering, giving its textures a famously crunchy, pixelated look that later source ports corrected with bilinear and trilinear options.
Why it matters
Texture filtering is one of those settings that massively improves visual quality at almost no performance cost on modern hardware. It is also a great example of how rendering is full of tradeoffs between mathematical correctness and computational cost, with decades of clever engineering making the correct solution practically free.
Related concepts