Difference between revisions of "Write Mask"

From OpenGL.org
Jump to: navigation, search
(Color Mask)
(Clarification on framebuffer clear.)
Line 7: Line 7:
  
 
* All drawing commands.
 
* All drawing commands.
* {{apifunc|glClear}} and {{apifunc|glClearBuffer}}.
+
* [[Framebuffer#Buffer clearing|Framebuffer clearing calls]], {{apifunc|glClear}} and {{apifunc|glClearBuffer}}.
  
{{note|This does not apply to operations that affect images that just so ''happen'' to be part of the current framebuffer. For example, if you use [[Image Load Store]] to modify an image's data, the write mask will not affect that write even if that image is also part of the current [[Framebuffer Object]] (of course, trying to write to the same image in two ways also yields undefined behavior). The write mask only applies to write operations that specifically go to the current framebuffer.}}
+
{{note|This does not apply to operations that affect images that just so ''happen'' to be part of the current framebuffer. For example, if you use [[Image Load Store]] to modify an image's data, the write mask will not affect that write even if that image is also part of the current [[Framebuffer Object]] (of course, trying to write to the same image in two ways also yields undefined behavior). The write mask only applies to write operations that go through to the current [[Framebuffer]].}}
  
 
Even though the mask only applies to writes to a framebuffer, the mask state is ''not'' [[Framebuffer]] state. So it is not part of a [[Framebuffer Object]] or the [[Default Framebuffer]]. Binding a new framebuffer will not affect the mask.
 
Even though the mask only applies to writes to a framebuffer, the mask state is ''not'' [[Framebuffer]] state. So it is not part of a [[Framebuffer Object]] or the [[Default Framebuffer]]. Binding a new framebuffer will not affect the mask.

Revision as of 22:23, 29 July 2013

The Write Mask is the part of the rendering pipeline that allows or prevents color, depth, or stencil components from being written to the current framebuffer.

The Fragment Shader can output one or more color values, as well as a depth value. The stencil state also causes the emitting of a stencil value. After blending, logic ops, and depth/stencil tests, the fragment values can be written to a sample in the framebuffer. The masking state can prevent certain components from being written.

Note that masking state affects all functions that modify the Framebuffer. This includes:

Note: This does not apply to operations that affect images that just so happen to be part of the current framebuffer. For example, if you use Image Load Store to modify an image's data, the write mask will not affect that write even if that image is also part of the current Framebuffer Object (of course, trying to write to the same image in two ways also yields undefined behavior). The write mask only applies to write operations that go through to the current Framebuffer.

Even though the mask only applies to writes to a framebuffer, the mask state is not Framebuffer state. So it is not part of a Framebuffer Object or the Default Framebuffer. Binding a new framebuffer will not affect the mask.

Color Mask

The color(s) output from the fragment shader can be masked. Each individual color component, R, G, B, and A, has a separate mask. So it is possible to prevent certain color components from being written.

Each separate color buffer, as defined by the glDrawBuffers function, has a separate mask.

To set the mask for a particular draw buffer, use the glColorMaski function:

void glColorMaski(GLuint buf​, GLboolean red​, GLboolean green​, GLboolean blue​, GLboolean alpha​);

The buf​ parameter specifies which of the color buffers to set the mask for. This can be any value on the range [0, GL_MAX_DRAW_BUFFERS). The other values are set to GL_TRUE to enable writing that component and GL_FALSE to disable writing it.

The function glColorMask can be used to set the mask for all draw buffers. This is useful for quickly re-enabling write masks on all output buffers.

Depth Mask

The depth buffer write can be masked, thus preventing the depth buffer from being updated. This useful for implementing transparency. Masking is controlled by this function:

 void glDepthMask(GLboolean flag​);

Setting flag​ to GL_TRUE means that the depth is written.

Stencil Mask

Stencil write masking works slightly differently. The stencil buffer works in terms of a bitfield (usually with 8-bits). Therefore instead of taking a boolean value, the stencil mask is an integer:

 void glStencilMask(GLuint mask​);

The bits that are set in mask​ are the bits that will be written.