mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-19 09:47:19 +00:00
e958791a01
* First public update for Vulkan 1.1.
Github Issues:
* Refer to standard sparse image block shape format tables explicitly in
the <<sparsememory-standard-shapes, Standard Sparse Image Block Shapes>>
section (public issue 93).
* Add the missing definition of the code:LocalInvocationIndex decoration
in the <<interfaces-builtin-variables, Built-In Variables>> section
(public issue 532).
* Clarify dynamic state definition in the introduction to the <<pipelines,
Pipelines>> section and the new <<pipelines-dynamic-state, Dynamic
State>> subsection (public issue 620).
* Clarified deprecation statement in the `VK_AMD_negative_viewport_height`
appendix (public issue 674).
* Fix parameter descriptions for flink:vkCreateIndirectCommandsLayoutNVX
(public issue 677).
Internal Issues:
* Remove description of <<primsrast-points, rasterization point size>>
being taken from the tessellation control shader, since there are no
circumstances under which you can have TCS without TES (internal issue
522).
* Define <<copies-images-format-size-compatibility, _size-compatible_
image formats>> for flink:vkCmdCopyImage, add it to the glossary, and
use that definition for slink:VkImageViewCreateInfo (internal issue
771).
* Change brief descriptions of enumerant names, and of parameters which
are enumerants, from "`enum *indicates*`" to "`enum *specifies*`" for
consistency, and add a markup style guide rule (internal issue 862).
* Clarify how execution dependencies interact with
<<synchronization-submission-order, submission order>> at numerous
places in the <<renderpass, Render Pass>> and <<synchronization,
Synchronization>> chapters (internal issue 1062).
* Clarify statement in the <<interfaces-resources-setandbinding,
DescriptorSet and Binding Assignment>> section that only interface
variables statically used by the entry point used in a pipeline must be
present in the descriptor set layout (internal issue 1172).
* Flip sparse image diagrams with partially full mip levels vertically, to
match graph origins of other image diagrams (internal issue 1176).
* Update new SVG diagrams to have consistent style and base font size,
increase consistency of primitive topology diagrams, and add a section
to the style guide on creating and editing images in a consistent style
(internal issue 1177).
* Resolve problems with valid usage statement extraction by fixing
existing VUID tags for interfaces promoted to version 1.1 and fixing
conditional directives around
VUID-VkMemoryDedicatedAllocateInfo-image-01797 (internal issue 1184).
* Strip `KHR` suffixes from a few interfaces promoted to Vulkan 1.1 that
were missed previously (internal issue 1185).
* Restrict code:OpImageQuerySizeLod and code:OpImageQueryLevels to only
work on code:Image operands with their code:Sampled operand set to 1. In
other words, these operations are not defined to work with storage
images (internal issue 1193).
* Recycle extension slot for extension #82 in `vk.xml`. This extension was
never published (internal issue 1195).
* Add an issue to the `VK_KHR_maintenance1` appendix noting that zero
height viewports are allowed when this extension is enabled (internal
issue 1202).
* Fix slink:VkDescriptorSetLayoutBinding description so that shader stages
always use descriptor bindings, not the other way around (internal issue
1206).
* Fix field name for
slink:VkInputAttachmentAspectReference::pname:inputAttachmentIndex
(internal issue 1210).
Other Issues:
* Fix a few broken links in the <<versions-1.1, Version 1.1>> appendix.
* Replace a few old refBegin/refEnd tags with open block markup around
interfaces, and remove old KHX VUID tags that were breaking the valid
usage statement extraction.
* Fix error codes accidentally tagged as success codes in `vk.xml` for
flink:vkGetSwapchainCounterEXT.
* Added valid usage statements for ftext:vkBind*Memory2 input structures
stext:VkBind*MemoryInfo, and fix a pname:image -> pname:buffer typo in a
couple of places.
* Fix swapped descriptions of elink:VkDescriptorType enums
ename:VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE and
ename:VK_DESCRIPTOR_TYPE_STORAGE_IMAGE (reported via tweet).
New Extensions:
* `VK_ANDROID_external_memory_android_hardware_buffer`
149 lines
4.9 KiB
Plaintext
149 lines
4.9 KiB
Plaintext
// Copyright (c) 2016-2018 Khronos Group. This work is licensed under a
|
|
// Creative Commons Attribution 4.0 International License; see
|
|
// http://creativecommons.org/licenses/by/4.0/
|
|
|
|
include::meta/VK_KHR_maintenance2.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2017-09-05
|
|
*Interactions and External Dependencies*::
|
|
- Promoted to Vulkan 1.1 Core
|
|
*Contributors*::
|
|
- Michael Worcester, Imagination Technologies
|
|
- Stuart Smith, Imagination Technologies
|
|
- Jeff Bolz, NVIDIA
|
|
- Daniel Koch, NVIDIA
|
|
- Jan-Harald Fredriksen, ARM
|
|
- Daniel Rakos, AMD
|
|
- Neil Henning, Codeplay
|
|
- Piers Daniell, NVIDIA
|
|
|
|
`VK_KHR_maintenance2` adds a collection of minor features that were
|
|
intentionally left out or overlooked from the original Vulkan 1.0 release.
|
|
|
|
The new features are as follows:
|
|
|
|
* Allow the application to specify which aspect of an input attachment
|
|
might be read for a given subpass.
|
|
* Allow implementations to express the clipping behavior of points.
|
|
* Allow creating images with usage flags that may not be supported for the
|
|
base image's format, but are supported for image views of the image that
|
|
have a different but compatible format.
|
|
* Allow creating uncompressed image views of compressed images.
|
|
* Allow the application to select between an upper-left and lower-left
|
|
origin for the tessellation domain space.
|
|
* Adds two new image layouts for depth stencil images to allow either the
|
|
depth or stencil aspect to be read-only while the other aspect is
|
|
writable.
|
|
|
|
=== Input Attachment Specification
|
|
|
|
Input attachment specification allows an application to specify which aspect
|
|
of a multi-aspect image (e.g. a combined depth stencil format) will be
|
|
accessed via a code:subpassLoad operation.
|
|
|
|
On some implementations there may: be a performance penalty if the
|
|
implementation does not know (at flink:vkCreateRenderPass time) which
|
|
aspect(s) of multi-aspect images can: be be accessed as input attachments.
|
|
|
|
|
|
|
|
=== New Object Types
|
|
|
|
None.
|
|
|
|
=== New Enum Constants
|
|
|
|
* Extending elink:VkStructureType:
|
|
** ename:VK_STRUCTURE_TYPE_RENDER_PASS_INPUT_ATTACHMENT_ASPECT_CREATE_INFO_KHR
|
|
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_POINT_CLIPPING_PROPERTIES_KHR
|
|
** ename:VK_STRUCTURE_TYPE_IMAGE_VIEW_USAGE_CREATE_INFO_KHR
|
|
** ename:VK_STRUCTURE_TYPE_PIPELINE_TESSELLATION_DOMAIN_ORIGIN_STATE_CREATE_INFO_KHR
|
|
|
|
* Extending elink:VkImageCreateFlagBits:
|
|
** ename:VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT_KHR
|
|
** ename:VK_IMAGE_CREATE_EXTENDED_USAGE_BIT_KHR
|
|
|
|
* Extending elink:VkImageLayout
|
|
** ename:VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL_KHR
|
|
** ename:VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL_KHR
|
|
|
|
* ename:VK_POINT_CLIPPING_BEHAVIOR_ALL_CLIP_PLANES_KHR
|
|
* ename:VK_POINT_CLIPPING_BEHAVIOR_USER_CLIP_PLANES_ONLY_KHR
|
|
|
|
=== New Enums
|
|
|
|
* slink:VkPointClippingBehaviorKHR
|
|
* slink:VkTessellationDomainOriginKHR
|
|
|
|
=== New Structures
|
|
|
|
* slink:VkPhysicalDevicePointClippingPropertiesKHR
|
|
* slink:VkRenderPassInputAttachmentAspectCreateInfoKHR
|
|
* slink:VkInputAttachmentAspectReferenceKHR
|
|
* slink:VkImageViewUsageCreateInfoKHR
|
|
* slink:VkPipelineTessellationDomainOriginStateCreateInfoKHR
|
|
|
|
=== New Functions
|
|
|
|
None.
|
|
|
|
=== Promotion to Vulkan 1.1
|
|
|
|
All functionality in this extension is included in core Vulkan 1.1, with the
|
|
KHR suffix omitted.
|
|
The original type, enum and command names are still available as aliases of
|
|
the core functionality.
|
|
|
|
=== Input Attachment Specification Example
|
|
|
|
Consider the case where a render pass has two subpasses and two attachments.
|
|
|
|
Attachment 0 has the format ename:VK_FORMAT_D24_UNORM_S8_UINT, attachment 1
|
|
has some color format.
|
|
|
|
Subpass 0 writes to attachment 0, subpass 1 reads only the depth information
|
|
from attachment 0 (using inputAttachmentRead) and writes to attachment 1.
|
|
|
|
[source,c++]
|
|
----------------------------------------
|
|
VkInputAttachmentAspectReferenceKHR references[] = {
|
|
{
|
|
.subpass = 1,
|
|
.inputAttachmentIndex = 0,
|
|
.aspectMask = VK_IMAGE_ASPECT_DEPTH_BIT
|
|
}
|
|
};
|
|
|
|
VkRenderPassInputAttachmentAspectCreateInfoKHR specifyAspects = {
|
|
.sType = VK_STRUCTURE_TYPE_RENDER_PASS_INPUT_ATTACHMENT_ASPECT_CREATE_INFO_KHR,
|
|
.pNext = NULL,
|
|
.aspectReferenceCount = 1,
|
|
.pAspectReferences = references
|
|
};
|
|
|
|
|
|
VkRenderPassCreateInfo createInfo = {
|
|
...
|
|
.pNext = &specifyAspects,
|
|
...
|
|
}
|
|
|
|
vkCreateRenderPass(...);
|
|
----------------------------------------
|
|
|
|
=== Issues
|
|
|
|
1) What is the default tessellation domain origin?
|
|
|
|
*RESOLVED*: Vulkan 1.0 originally inadvertently documented a lower-left
|
|
origin, but the conformance tests and all implementations implemented an
|
|
upper-left origin.
|
|
This extension adds a control to select between lower-left (for
|
|
compatibility with OpenGL) and upper-left, and we retroactively fix
|
|
unextended Vulkan to have a default of an upper-left origin.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2017-04-28
|