Lines Matching refs:textures
41 Language, which provide the mechanisms necessary to access array textures.
49 textures. An array texture is a collection of one- and two-dimensional
59 coordinate for 1D and 2D array textures, respectively. The layer
67 Array textures can be rendered to by binding them to a framebuffer object
73 This extension does not provide for the use of array textures with
167 two-dimensional array textures, where it's in "q".
168 (2) Add new EXT_gpu_shader4 sampler types used for array textures. )
170 Texture lookups involving textures with depth component data can either
186 two-, and three-dimensional textures consist of a one-, two-, or
187 three-dimensional texel arrays. One- and two-dimensional array textures
261 number of layers for one- and two-dimensional array textures (height or
310 with array textures. All subsequent references to "texture array" in the
330 (modify second paragraph, p. 159 -- allow 1D array textures) The command
390 array textures, j and k are irrelevant; the texel at location i becomes
392 textures, k is irrelevant; the texel at location (i, j) becomes the
393 texture value. For one- and two-dimensional array textures, the texel is
396 l = clamp(floor(t + 0.5), 0, h_t-1), for one-dimensional array textures,
397 clamp(floor(r + 0.5), 0, d_t-1), for two-dimensional array textures.
405 texture image. For two-dimensional array textures, all texels are
415 For one-dimensional array textures, both texels are obtained from layer l,
431 array textures,
433 array, and cube map textures
434 max(w_t, h_t, d_t), for three dimensional textures.
444 h_d = 1, for one-dimensional array textures and
446 d_d = 1, for two-dimensional array textures and
465 textures, each layer is filtered independently. ...
470 three-dimensional textures and one- or two-dimensional array textures, a
475 (modify second and third paragraphs, p. 179, adding array textures and
479 textures, one- and two-dimensional array textures, and the six image
481 maintained for one-, two-, and three-dimensional textures and one- and
482 two-dimensional array textures. Additionally, a single proxy image array
497 Proxy arrays for one- and two-dimensional textures and one- and
498 two-dimensional array textures are operated on in the same way when
506 (update most of the beginning of the section to allow array textures)
508 In addition to the default textures TEXTURE_1D, TEXTURE_2D, TEXTURE_3D,
548 that access to these initial textures not be lost, they are treated as
550 three-dimensional, cube map, one- and two-dimensional array textures are
594 two-dimensional array textures, where it's in "q".
595 (2) Add new EXT_gpu_shader4 sampler types used for array textures. )
597 Texture lookups involving textures with depth component data can either
661 three-dimensional textures. One- and two-dimensional array textures are
665 For three-dimensional and two-dimensional array textures, pixel storage
686 generation support is extended to include array textures.
694 three-dimensional and array textures. All references to this token in
759 applications to bind entire three-dimensional, cube map, or array textures
764 more extensive than the more limited support provided for array textures.
774 texture lookups into array textures, this extension is pointless, given
778 the shading language to support array textures. The extension
789 S3TC texture compression is supported for two-dimensional array textures.
791 as a compressed two-dimensional textures. When specifying or querying
793 and/or returned as a series of two-dimensional textures stored
795 For array textures, images are not arranged in 4x4x4 or 4x4x2 blocks as in
804 array textures in this extension. If compressed one-dimensional arrays
810 textures), compressed sub-image updates are allowed at arbitrary locations
813 for 2D textures) and NV_texture_compression_vtc (allowing updates at 4x4x4
814 boundaries for 3D textures) is updated as follows:
836 allow compressed subimage updates of array textures via
871 textures. This is a subset of the new shading language provided by the
976 (1) Should this extension generalize the notion of 1D and 2D textures to
982 textures, and allow applications to pass TEXTURE_1D to TexImage2D (1D
988 textures in programmable shaders, so compilers can generate code
989 appropriate to the texture type. For "normal" textures, a 2D texture
992 textures, implementations must choose between compiling shaders to the
1000 non-array textures to the shaders, but it could then become the
1009 for the possibility of single-layer array textures; it may be the case
1011 array textures, but there may be cases where only a single layer might
1013 textures, but the distinction is now based on the API call.
1019 be used, as TEXTURE_1D_ARRAY_EXT and TEXTURE_2D_ARRAY_EXT textures are
1036 with texture lookups of two-dimensional array textures with shadow
1057 (4) Should DEPTH_COMPONENT textures be supported for texture arrays?
1077 lookups in two-dimensional array textures be treated as non-projective,
1082 (6) How do texture borders interact with array textures?
1088 (7) How does mipmapping work with array textures?
1094 consistency rules for array textures.
1096 (8) Are compressed textures supported for array textures?
1100 textures are treated as arrays of compressed 1D or 2D images.
1102 (9) Should these things be called "array textures" or "texture arrays"?
1104 RESOLVED: "Array textures", mostly because it was easier spec wording.
1105 Calling them "array textures" also seems like better disambiguation;
1110 * the array of texture layers (array textures)
1116 (10) If they're called "array textures", why does the extension name
1123 textures?
1130 two-dimensional array textures?
1135 operations could be defined for 3D textures as well at that time.
1137 Note that with the API chosen, one-dimensional array textures do have
1145 RESOLVED: For 2D array textures, call TexImage3D once with a NULL image
1157 (15) How is the LOD (lambda) computed for array textures?
1160 textures as it is for normal 1D and 2D textures. The layer coordinate
1170 (17) How do array textures work with framebuffer objects
1179 support provided by glGenerateMipmapEXT is extended to array textures.
1216 of mipmapped textures in
1220 now supported for 3D textures?
1226 two-dimensional array textures are specified using the three-dimensional
1230 for S3TC-style compressed 3D textures.
1242 2D array textures along 4x4x1 boundaries (we