Lines Matching refs:mipmap
60 number of accessible mipmap levels in the texture associated with a GLSL
67 unless the texture has a full mipmap chain and is used with a mipmapped
102 ability to query the number of accessible mipmap levels in a texture
117 where <q> is the maximum mipmap level specified in the "Mipmapping"
192 The textureQueryLevels functions return the number of mipmap levels
237 - A texture is "mipmap complete" if it has a full set of mipmaps, from
241 to be mipmap complete. Note that immutable format textures will
242 always be considered mipmap complete.
245 mapping. A texture that is not mipmap complete can still be
250 mipmap levels and are always considered mipmap complete; however,
251 applications can add (or delete) mipmap levels to TexImage* textures at
255 mipmap complete, an implementation might choose to manage the texture in
263 - allocate memory for the subset of the full mipmap chain that is
266 - speculatively allocate memory for the entire mipmap chain
275 that are complete, even if they aren't mipmap complete. For example, a
283 RESOLVED: As with the mipmap-incomplete case, the value returned is
309 textureQueryLevels() is called for a texture that *is* mipmap complete
315 be mipmap complete and accessed with a mipmapped minification filter.
317 with an allocation holding the full mipmap chain.
320 of "extra" mipmap levels until they are actually required. For textures
321 without immutable formats, mipmap levels can be added or removed at any
339 will be mipmap complete only for primitives (C), (D), and (E). For
343 and further mipmap level changes might occur. For primitive (C), the
344 texture is mipmap complete, but the non-zero mipmap levels still aren't
382 textures that are mipmap complete or not, incomplete or unbound
388 - Add issue 4, describing what happens for mipmap complete textures that
391 mipmap chain as resident.