Vulkan-Docs/doc/specs/vulkan/man/vkCmdClearAttachments.txt

88 lines
3.1 KiB
Plaintext
Raw Normal View History

2016-02-16 01:53:44 -08:00
vkCmdClearAttachments(3)
========================
Name
----
vkCmdClearAttachments - Clear regions within currently bound framebuffer attachments.
C Specification
---------------
include::../protos/vkCmdClearAttachments.txt[]
Parameters
----------
pname:commandBuffer::
The command buffer into which to insert the command.
pname:attachmentCount::
The number of attachments to clear.
pname:pAttachments::
A pointer to an array of structures describing the attachments to clear
and the values to clear them to.
pname:rectCount::
The number of regions within the attachments to clear.
pname:pRects::
A pointer to an array of rectangles defining the regions to clear.
Description
-----------
fname:vkCmdClearAttachments clears regions within the attachments associated
with the current renderpass. pname:commandBuffer is a handle to the command
buffer into which to insert the command. A renderpass must be active on
pname:commandBuffer. pname:attachmentCount specifies the number of attachments
to clear and pname:pAttachments is a pointer to an array of pname:attachmentCount
slink:VkClearAttachment structures, each containing the aspect(s), attachment
index and the clear value for each attachment. The definition of
slink:VkClearAttachment is:
include::../structs/VkClearAttachment.txt[]
pname:aspectMask is a bitfield specifying the aspect or aspects to clear
on the referenced attachment. It is constructed from a bitwise combination
of the members of the elink:VkImageAspectFlagBits enumeration, the
definition of which is:
include::../enums/VkImageAspectFlagBits.txt[]
The pname:colorAttachment member of slink:VkClearAttachment specifies the
index of the color attachment within the current framebuffer. The pname:clearValue
member contains the value to which to clear the attachment. It is an instance
of the slink:VkClearValue union, the definition of which is:
include::../structs/VkClearValue.txt[]
If the attachment and aspect referenced by ptext:aspectMask and
Change log for April 22, 2016 Vulkan 1.0.11 spec update: * Bump API patch number and header version number to 11 for this update. Github Issues: * Clarify the WSI extension language by switching from the fuzzier "ownership" language to more-consistent "acquire" language (public issue 117). * Clarify that memory barriers apply to all commands in the dependency chains in the flink:vkGetRenderAreaGranularity command and the <<synchronization-execution-and-memory-dependencies,Execution And Memory Dependencies>> section (public issue 132). * Clarify that a queue family is a set of queues in the <<fundamentals-execmodel,Execution Model>> section (public issue 166). * Removed requirement from valid usage language that VkPresentInfoKHR::waitSemaphoreCount must be greater than 0 (public issue 171). * Fix broken internal links, describe structures consistently, use consistent style for SPIR-V codewords, and tag normative terms that were missing asciidoc tags (public issue 183 and ancillary markup/normative language fixes). * Fix typos for slink:VkPhysicalDeviceLimits member names in slink:VkImageCreateInfo validity language (public issue 184). Internal Issues: * Document that the requested patch version number specified as part of slink:VkApplicationInfo::pname:apiVersion is ignored when creating an instance (internal issue 176). * Clarify handling of extension structs in the <<fundamentals-validusageValid Usage>> section (internal issue 254). * Update required slink:VkImageFormatProperties::pname:maxMipLevels to be limited to the maximum allowed mipmap pyramid size corresponding to the actual maximum supported size for the format (internal issue 256). * Modify the <<features-extentperimagetype,Allowed Extent Values Based On Image Type>> section so the allowed maximum extent is the maximum image dimension supported for each dimension of the type of texture being queried (internal issue 257). * Clarify in the <<spirvenv-module-validation,Validation Rules within a Module>> section that at least one of the code:LocalSize execution mode or code:WorkgroupSize decoration is required for each compute shader entry point in a shader module (internal issue 279). * Add validity rules for formats in flink:vkCmdClearColorImage and flink:vkCmdClearDepthStencilImage (internal issue 283). * Clarify that slink:VkImageFormatProperties::pname:maxResourceSize is an upper bound, and that it may not be possible to create an image anywhere near that size (internal issue 284). Other Commits: * Fix various minor markup errors reported by validation scripts. * Change copyright from Khronos Free Use License to Apache 2.0 license on relevant script/XML/header files. This does not affect the specification source copyright.
2016-04-21 01:08:38 -07:00
ptext:colorAttachment is a color attachment, the values contained in the
2016-02-16 01:53:44 -08:00
pname:color field of slink:VkClearValue is used to clear the attachment
regions. If the attachment and aspect referenced by ptext:aspectMask and
ptext:colorAttachment is a depth, stencil or depth-stencil attachment, then
the pname:depthStencil field of slink:VkClearValue is used to clear the
attachment.
The pname:rectCount parameter to fname:vkCmdClearAttachments specifies the
number of regions of the attachments to clear. pname:pRects is a pointer
to an array of pname:rectCount slink:VkClearRect structures defining
those regions. The definition of slink:VkClearRect is:
include::../structs/VkClearRect.txt[]
The pname:rect member of slink:VkClearRect specifies the rectangle, measured
in pixels, of the rectangle to clear. pname:baseArrayLayer and
pname:layerCount specify the first layer and number of layers to clear
and should be used to clear multiple layers in layered attachments.
include::../validity/protos/vkCmdClearAttachments.txt[]
See Also
--------
slink:VkClearAttachment, flink:vkCmdBeginRenderPass
include::footer.txt[]