Talk:Mipmap

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computer graphics (Rated Start-class)
WikiProject icon This article is within the scope of WikiProject Computer graphics, a collaborative effort to improve the coverage of computer graphics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
 

Technically...[edit]

"Mipmaps require 33% more memory than a single texture. "

Isn't this supposed to be 50%? It's clear from the picture as well that mipmapping adds exactly 50% of the surface area of the original to the new one (which is 33% of the new bigger image, not the old one). Please correct it back if I am wrong or misunderstood something. Choephix (talk) 15:23, 22 January 2013 (UTC)

Don't count the white area Striepan (talk) 21:45, 31 January 2013 (UTC)

Untitled[edit]

2 Things:

(1) This sentence doesn't seem to make sense: "Rendering speed increases since the number of texture pixels ("texels") being processed can be much lower than with simple textures."

(2) I don't think that "cache coherency" is the correct term here. "Cache coherency" goes down? It is also used again later.

128.83.144.47 (talk) 21:07, 29 January 2009 (UTC)RMS

Rendering speeds increased?[edit]

This seems not to be the case. I have Grand Theft Auto: San Andreas (PC), it gives you the option to turn on/off mip mapping. When its on my frames per second ratio drops to five fps. When I have mip mapping turned off however, the fps ratio is eighty fps. Mip mapping seems to be like anti aliasing, it draws more than the default would, in attempt to make the image smoother. So, it makes no sense for it to render it faster.

More textures = slower rendering speed Yakisan (talk) 08:27, 19 August 2009 (UTC) —Preceding unsigned comment added by 166.164.109.44 (talk)

if activating mipmaps brings your game from 80fps down to 5fps, it's more likely a problem with the game or your computer, not with mipmapping itself. if you have enough memory aviable, mipmaps speed it up. --83.77.196.218 (talk) 00:31, 9 October 2009 (UTC)
Mip-mapping counteracts one effect: oversampling. This occurs when more pixels are available to copy than available on the screen. Mip-mapping gives the rendering algorithm less pixels to choose from, resulting in smoother (but blurrier) rendered images.
Knight666 (talk) 16:00, 23 January 2010 (UTC)

Alpha considerations[edit]

There should probably be a mention of alpha in mipmaps. E.g. for transparent mipmaps, if you don't pre-multiply the alpha you can end up with artefacts bleeding in from the transparent pixels, as discussed here: http://blog.wolfire.com/2009/01/scaling-images-with-alpha/Pengo 05:15, 6 April 2011 (UTC)

MIP maps?[edit]

The subject is called "mipmaps" and everything else is also referenced as mipmap. BUT, the beginning references MIP maps first. Is it a good idea to swap these two words to make sense to the prioritized word (mipmaps)? 88.134.36.87 (talk) 16:07, 21 April 2011 (UTC)

Generating mipmaps using Fourier transform?[edit]

In the article it says that more sophisticated algorithms for generating mipmaps, "perhaps based on signal processing and Fourier transforms", can also be used. Is this just a qualified guess or is there actually some reference for this? —Kri (talk) 09:53, 10 July 2011 (UTC)

Isn't this strictly handled by the Hardware/API nowadays?[edit]

If yes, it has to be clearly shown on the article. --fs 09:34, 14 December 2011 (UTC)