mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-23 03:28:19 +00:00
75bbb5f4d5
* Bump API patch number and header version number to 12 for this
update.
Github Issues:
* Change valid usage statements intended to be "sub-points" to
be actual sub-points (public issue 66).
* Replace double negation in description of
slink:VkRenderPassBeginInfo::pname:pClearValues (based on public
merge 142).
* Cleanup minor typos in spec, ref pages and XML, including those
proposed in public pull requests 144, 150, 151, 167, 168, 181, and
186.
* Use *strict subset* in describing the partial order of memory
property types for slink:VkMemoryType, and update the style guide
accordingly (public issue 190).
* Fix various "a image" -> "an image" typos (public issue 191).
* Note in the <<fundamentals-validusage,Valid Usage>> and
<<extensions-interactions,Extension Interactions>> sections that
structures defined by extensions which may be passed in structure
chains using the ptext:pNext member must: include initial
ptext:sType and ptext:pNext members (public issue 192).
Internal Issues:
* Remove duplicate language from the description of the pname:fence
parameter to flink:vkQueueSubmit and improve validity language
(internal issue 91).
* Added documentation for "optional" attribute to XML readme.tex/pdf
(internal issue 149).
* Clarify the host-side data validity rules and behavior of
flink:vkFlushMappedMemoryRanges and
flink:vkInvalidateMappedMemoryRanges (internal issue 266).
Other Commits:
* Added clarification to flink:vkCmdFillBuffer regarding the use of
ename:VK_WHOLE_SIZE.
* Fixed and documented implementation of "validextensionstructs"
attribute. in XML processing scripts and readme.tex/pdf.
* Add missing validity statements to flink:vkResetEvent and
flink:vkCmdResetEvent.
* Fix validity for the
ename:VK_FORMAT_FEATURE_SAMPLED_IMAGE_FILTER_LINEAR_BIT flag.
Correct all the draw/dispatch commands to mention optimally tiled
images as well as linear tiled images, and say image VIEWS instead
of images. Add validity statement to flink:vkCmdBlitImage
* Replace the {apiname} macro with hardcoded "Vulkan", now that we've
committed to that name.
* Add the VK_AMD_rasterization_order extension to vk.xml.
56 lines
1.4 KiB
Plaintext
56 lines
1.4 KiB
Plaintext
vkCmdResolveImage(3)
|
|
=====================
|
|
|
|
Name
|
|
----
|
|
vkCmdResolveImage - Resolve regions of an image.
|
|
|
|
C Specification
|
|
---------------
|
|
|
|
include::../protos/vkCmdResolveImage.txt[]
|
|
|
|
Parameters
|
|
----------
|
|
|
|
pname:commandBuffer::
|
|
The command buffer into which the command is to be placed.
|
|
|
|
pname:srcImage::
|
|
The image that is the source of the resolve operation.
|
|
|
|
pname:srcImageLayout::
|
|
The layout of the source image at the time of the resolve.
|
|
|
|
pname:dstImage::
|
|
The image into which image data is to be resolved.
|
|
|
|
pname:dstImageLayout::
|
|
The layout of the destination image at the time of the resolve.
|
|
|
|
pname:regionCount::
|
|
The number of regions to resolve.
|
|
|
|
pname:pRegions::
|
|
An array of image regions to resolve.
|
|
|
|
Description
|
|
-----------
|
|
|
|
fname:vkCmdResolveImage resolves regions of a source image into a destination image.
|
|
The source and destination images are specified in pname:srcImage and pname:dstImage, respectively.
|
|
The layout of the source and destination images must be provided in pname:srcImageLayout and
|
|
pname:dstImageLayout, respectively. pname:pRegions is a pointer to an array of pname:regionCount slink:VkImageResolve
|
|
structures, the definition of each is:
|
|
|
|
include::../structs/VkImageResolve.txt[]
|
|
|
|
include::../validity/protos/vkCmdResolveImage.txt[]
|
|
|
|
See Also
|
|
--------
|
|
|
|
flink:vkCmdBlitImage, flink:vkCmdClearColorImage, flink:vkCmdClearDepthStencilImage
|
|
|
|
include::footer.txt[]
|