Using mipmaps and anisotropic filtering to control texture shimmer

Identify a minification problem

A distant road can contain many texture texels inside one screen pixel. Sampling too little of that area makes fine lines change unpredictably as the camera moves. Increasing the source resolution can make the mismatch worse. Diagnose the projected texture footprint before adding sharpening or replacing the antialiasing method.

Use a repeatable camera path with a high-contrast road marking, a tiled wall, and a surface viewed at a grazing angle.

Give the filters distinct jobs

Mipmaps store progressively reduced images so minified samples can use prefiltered information. For a square power-of-two texture, each successive level has one quarter as many texels; the complete chain adds approximately one third to base-level storage. [1]

At oblique angles, the footprint becomes elongated. Anisotropic filtering accounts for that shape instead of treating both directions identically. [2] Its maximum setting is a quality limit, not a promise of a fixed sample count or equal performance across devices. [3]

Estimate memory and footprint

An illustrative 2048 × 2048 RGBA8 texture occupies 16 MiB at its base level. Its complete uncompressed square mip chain occupies approximately 21.33 MiB, before allocation alignment or other copies. Removing all lower levels saves about 5.33 MiB but also removes the prefiltered representations needed for stable distant sampling.

Now imagine a footprint spanning 16 texels along one axis and 2 along the other. The ratio is 8. This explains why choosing a very coarse isotropic level can blur the short axis. It does not establish that an 8× setting performs exactly eight reads; hardware chooses the implementation.

Tune with motion and inspection

Verify that every required mip exists and contains plausible data. Temporarily colour each level differently to reveal selection and streaming transitions. Compare neutral LOD bias with any sharpening bias, keeping the camera path unchanged.

Then increase anisotropy in supported steps and capture both moving-image quality and texture-related GPU cost. Inspect road markings near the horizon and UV atlas borders. Ensure that mip generation respects the signal: colour averaging, alpha coverage, and directional data can require different treatment. [1]

Avoid false fixes

Anisotropy cannot restore details absent from the source, correct broken UV derivatives, or guarantee stability for procedural patterns created after texture sampling. A sharp still image can hide severe temporal shimmer.

Choose the lowest-cost combination that preserves the intended detail during motion on target hardware. Record sampler settings alongside import and streaming settings, because changing any of them can invalidate an earlier visual comparison.

Sources

• [1] Runtime Mipmap Generation — Ignacio Castaño.
• [2] Anisotropic Texture Filtering — Microsoft.
• [3] EXT_texture_filter_anisotropic specification — NVIDIA and Khronos OpenGL Registry.