Write Mask: Difference between revisions
Re-categorization. |
→Stencil Mask: Two-sided stencil. |
||
Line 37: | Line 37: | ||
== Stencil Mask == | == Stencil Mask == | ||
Stencil write masking works slightly differently. | Stencil write masking works slightly differently, in two ways. First, the [[Stencil Buffer]] is always an unsigned integer (of some bitdepth), so the mask here is an actual bitfield, rather than simply being on/off. | ||
The other difference is that the [[Stencil Test]] can be different for the [[Triangle Facing|two sides of triangles]]. Therefore, the stencil write mask can be set for either side, or both at once. | |||
The bits | To set the stencil bitmask, use this function: | ||
{{funcdef|void {{apifunc|glStencilMaskSeparate}}(GLenum {{param|face}}, GLuint {{param|mask}});}} | |||
The {{param|face}} determines which stencil bitmask facing is being set. It can be {{enum|GL_FRONT}}, {{enum|GL_BACK}}, or {{enum|GL_FRONT_AND_BACK}} to set the bitmask for both sides at once. The bits set in {{param|mask}} are the only stencil bits that will be affected by any subsequent rendering commands. | |||
The {{apifunc|glStencilMask}} function can be used as shorthand for {{enum|GL_FRONT_AND_BACK}}. | |||
[[Category:Sample Writing]] | [[Category:Sample Writing]] |
Revision as of 18:21, 3 February 2015
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:
- All drawing commands.
- Framebuffer clearing calls, glClear and glClearBuffer.
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:
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, in two ways. First, the Stencil Buffer is always an unsigned integer (of some bitdepth), so the mask here is an actual bitfield, rather than simply being on/off.
The other difference is that the Stencil Test can be different for the two sides of triangles. Therefore, the stencil write mask can be set for either side, or both at once.
To set the stencil bitmask, use this function:
The face determines which stencil bitmask facing is being set. It can be GL_FRONT, GL_BACK, or GL_FRONT_AND_BACK to set the bitmask for both sides at once. The bits set in mask are the only stencil bits that will be affected by any subsequent rendering commands.
The glStencilMask function can be used as shorthand for GL_FRONT_AND_BACK.