forked from KhronosGroup/Vulkan-Docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Change log for March 29, 2022 Vulkan 1.3.210 spec update:
* Update release number to 210 for this update. Public Issues: * Clarify that descriptors are not referenced for unused ename:VK_DESCRIPTOR_BINDING_PARTIALLY_BOUND_BIT descriptors unless dynamically used (public issue 1794). * Remove "`If renderpass is NULL`" from slink:VkFramebufferCreateInfo valid usage statements (public issue 1800). Internal Issues: * Add valid usage statements to slink:VkAttachmentDescription and slink:VkAttachmentDescription2 for the cases when pname:loadOp is or pname:stencilLoadOp is ename:VK_ATTACHMENT_LOAD_OP_LOAD and pname:initialLayout is ename:VK_IMAGE_LAYOUT_UNDEFINED, and when pname:format is ename:VK_FORMAT_UNDEFINED (internal issue 2349). * Add valid usage statements to slink:VkRenderPassMultiviewCreateInfo and slink:VkSubpassDescription2 to respect <<limits-maxMultiviewViewCount, pname:maxMultiviewViewCount>> (internal issue 2511). * Clarify definition of <<shaders-staticuse, static use instructions>> (internal issue 2639). * Fix typo pname:pRanges -> pname:pRegions in common validity statements for copy image commands (internal issue 3052). * Update valid usage statement for build acceleration structure common VUs to allow inactive instances (internal merge request 5116). * Require <<features-colorWriteEnable, pname:colorWriteEnable>> for apiext:VK_EXT_color_write_enable in the <<features-requirements, Feature Requirements>> section. * Better specify when depth/stencil must be written in slink:VkPipelineShaderStageCreateInfo valid usage statements. New Extensions: * apiext:VK_EXT_graphics_pipeline_library * apiext:VK_EXT_primitives_generated_query
- Loading branch information
Showing
31 changed files
with
2,554 additions
and
397 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
// Copyright 2021-2022 The Khronos Group Inc. | ||
// | ||
// SPDX-License-Identifier: CC-BY-4.0 | ||
|
||
include::{generated}/meta/{refprefix}VK_EXT_graphics_pipeline_library.txt[] | ||
|
||
=== Other Extension Metadata | ||
|
||
*Last Modified Date*:: | ||
2021-08-17 | ||
*Contributors*:: | ||
- Tobias Hector, AMD | ||
- Chris Glover, Google | ||
- Jeff Leger, Qualcomm | ||
- Jan-Harald Fredriksen, Arm | ||
- Piers Daniell, NVidia | ||
- Boris Zanin, Mobica | ||
- Krzysztof Niski, NVidia | ||
- Dan Ginsburg, Valve | ||
- Sebastian Aaltonen, Unity | ||
- Arseny Kapoulkine, Roblox | ||
- Calle Lejdfors, Ubisoft | ||
- Tiago Rodrigues, Ubisoft | ||
- Francois Duranleau, Gameloft | ||
|
||
|
||
=== Description | ||
|
||
This extension allows the separate compilation of four distinct parts of | ||
graphics pipelines, with the intent of allowing faster pipeline loading for | ||
applications reusing the same shaders or state in multiple pipelines. | ||
Each part can be independently compiled into a graphics pipeline library, | ||
with a final link step required to create an executable pipeline that can be | ||
bound to a command buffer. | ||
|
||
include::{generated}/interfaces/VK_EXT_graphics_pipeline_library.txt[] | ||
|
||
=== Version History | ||
|
||
* Revision 1, 2021-08-17 (Tobias Hector) | ||
- Initial draft. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,77 @@ | ||
// Copyright (c) 2021 The Khronos Group Inc. | ||
// | ||
// SPDX-License-Identifier: CC-BY-4.0 | ||
|
||
include::{generated}/meta/{refprefix}VK_EXT_primitives_generated_query.txt[] | ||
|
||
=== Other Extension Metadata | ||
|
||
*Last Modified Date*:: | ||
2022-01-24 | ||
*Contributors*:: | ||
- Shahbaz Youssefi, Google | ||
- Piers Daniell, NVIDIA | ||
- Jason Ekstrand, Collabora | ||
- Jan-Harald Fredriksen, Arm | ||
|
||
=== Description | ||
|
||
This extension adds support for a new query type to match OpenGL's | ||
`GL_PRIMITIVES_GENERATED` to support layering. | ||
|
||
include::{generated}/interfaces/VK_EXT_primitives_generated_query.txt[] | ||
|
||
=== Version History | ||
|
||
* Revision 1, 2021-06-23 (Shahbaz Youssefi) | ||
- Internal revisions | ||
|
||
=== Issues | ||
|
||
1) Can the query from `VK_EXT_transform_feedback` be used instead? | ||
|
||
*RESOLVED*: No. | ||
While the query from VK_EXT_transform_feedback can produce the same results | ||
as in this extension, it is only available while transform feedback is | ||
active. | ||
The OpenGL `GL_PRIMITIVES_GENERATED` query is independent from transform | ||
feedback. | ||
Emulation through artificial transform feedback is unnecessarily | ||
inefficient. | ||
|
||
2) Can `VK_QUERY_PIPELINE_STATISTIC_CLIPPING_INVOCATIONS_BIT` be used | ||
instead? | ||
|
||
*RESOLVED*: It could, but we prefer the extension for simplicity. | ||
Vulkan requires that only one query be active at a time. | ||
If both the `GL_PRIMITIVES_GENERATED` and the | ||
`GL_CLIPPING_INPUT_PRIMITIVES_ARB` queries need to be simultaneously | ||
enabled, emulation of both through | ||
`VK_QUERY_PIPELINE_STATISTIC_CLIPPING_INVOCATIONS_BIT` is inconvenient. | ||
|
||
3) On some hardware, this query cannot be implemented if | ||
sname:VkPipelineRasterizationStateCreateInfo::pname:rasterizerDiscardEnable | ||
is enabled. | ||
How will this be handled? | ||
|
||
*RESOLVED*: A feature flag is exposed by this extension for this. | ||
On said hardware, the GL implementation disables rasterizer-discard and | ||
achieves the same effect through other means. | ||
It will not be able to do the same in Vulkan due to lack of state | ||
information. | ||
A feature flag is exposed by this extension so the OpenGL implementation on | ||
top of Vulkan would be able to implement a similar workaround. | ||
|
||
4) On some hardware, this query cannot be implemented for non-zero query | ||
indices. | ||
How will this be handled? | ||
|
||
*RESOLVED*: A feature flag is exposed by this extension for this. | ||
If this feature is not present, the query from `VK_EXT_transform_feedback` | ||
can be used to the same effect. | ||
|
||
5) How is the interaction of this extension with | ||
`transformFeedbackRasterizationStreamSelect` handled? | ||
|
||
*RESOLVED*: Disallowed for non-zero streams. | ||
In OpenGL, the rasterization stream is always stream zero. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.