News for hackers. Stuff that matters.
Re:Mipmap selection in too much detail by llm_nerd on Wednesday May 14, 2025 @08:09AM (#43983541)
This isn't my specialty, and ultimately it really doesn't matter to the core point of this good submission about how the GPU chooses mipmap level to use, however the article gives the impression that we pre-calculate mipmap levels to improve distant aliasing, though the problem they demonstrate is solved with trivial texture filtering.

Mipmaps are a performance optimization. You could just use a 4096x4096 brick texture across your entire game, and then use texture filtering to make it look good both close and far, but that means that rendering a distant wall polygon that might fill just a few pixels of the viewport needs to filter and apply a 16.7 million texel texture, redoing the filtering again and again and evicting everything else from caches just for that one texture. If instead it can apply a 32x32 pre-filtered texture to loads of distant objects, there are obviously massive performance ramifications. Which is why mipmaps are used, letting massive textures be used for those cases where the detail is valuable, without destroying performance when it's just some distant object.

Re:Mipmap selection in too much detail by pema99 on Wednesday May 14, 2025 @12:05PM (#43986167)
I agree that mipmapping is an optimization, but I also don't really consider it incorrect or misleading to call it a technique for mitigating aliasing - it's a practical technique for doing so. Fair point though, and perhaps I should have mentioned this.