mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-10 13:26:32 +00:00
eaea7d2709
* Bump API patch number and header version number to 26 for this update.
Github Issues:
* Bring sample code in the +VK_KHR_surface+ and +VK_KHR_swapchain+
extension summary appendices up to date, and note they will be replaced
with pointers to the LunarG SDK examples in the future (public issue
279).
* Add a new <<fundamentals-commandsyntax-results-lifetime,Lifetime of
Retrieved Results>> section specifying that ftext:vkGet* and
ftext:VkEnumerate* results are invariant unless otherwise specified, and
specify behavior for individual commands which are not invariant (public
issue 280).
* Remove conflicting definition of
slink:VkDisplayPlaneCapabilitiesKHR::pname:maxSrcPosition and clean up
language of the remaining definition (public issue 351).
* Fix many minor spelling errors and add rules to the style guide to
prevent recurrences (public issue 352).
Internal Issues:
* Remove redundant descriptions of the etext:VK_USE_PLATFORM_* macros from
the <<wsi,Window System Integration>> chapter in favor of the
description in the <<boilerplate-wsi-header,Window System-Specific
Header Control>> appendix (internal issue 6).
* Replace misleading 'can: be destroyed when not X' with more correct
'must: not be destroyed while X' in the
<<fundamentals-objectmodel-lifetime,Object Lifetime>> section. Disallow
destroying a pipeline layout while a command buffer using it is
recording (internal issue 241).
* Clarify that ename:VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT is valid for
all images used as attachments in elink:VkImageUsageFlagBits and the
slink:VkImageLayout validity language (internal issue 320).
* Note that <<extended-functionality-layers,Layers>> may wrap object
handles, but that this is a generally discouraged. A link to additional
information in the documentation for layer authors is provided (issue
398)
* Replace the mustnot: and shouldnot: macros with equivalent must: not and
should: not to get rid of non-English words while still highlighting
normative language (internal issue 407).
* Disallow creating multisampled images with
ename:VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT in the slink:VkImageLayout
validity language and the <<features-supported-sample-counts,Supported
Sample Counts>> section (internal issue 445).
* Fix typo so that flink:vkCmdDrawIndexedIndirect is defined in terms of
flink:vkCmdDrawIndexed rather than flink:vkCmdDrawIndirect (internal
issue 446).
* Reorganize the per-extension information sections to all be in the
<<extensions,Layers & Extensions>> appendix. Also fix a typo in
+VK_IMG_filter_cubic+ which incorrectly identified it as a +KHR+
extension (internal issue 461).
Other Issues:
* Use asciidoc markup instead of latexmath to simplify diagrams in the
<<features-formats-non-packed,byte mapping tables>> for color formats.
* Fix a markup problem with the wildcarded enumerant names in a NOTE in
the <<textures-texel-replacement,Texel Replacement>> section.
* Fix missing attributes in the XML interface for
elink:VkExternalMemoryHandleTypeFlagBitsNV and
elink:VkExternalMemoryFeatureFlagBitsNV (KhronosGroup/Vulkan-Hpp issue
#25)
* Cleanup reference page builds so only core pages are built for releases.
113 lines
3.7 KiB
Plaintext
113 lines
3.7 KiB
Plaintext
== VK_AMD_rasterization_order
|
|
|
|
*Name String*:: VK_AMD_rasterization_order
|
|
*Extension Type*:: Device extension
|
|
*Registered Extension Number*:: 19
|
|
*Last Modified Date*:: 04/25/2016
|
|
*Revision*:: 1
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Dependencies*::
|
|
- This extension is written against version 1.0.11 of the Vulkan API.
|
|
*Contributors*::
|
|
- Matthaeus G. Chajdas, AMD
|
|
- Jaakko Konttinen, AMD
|
|
- Daniel Rakos, AMD
|
|
- Graham Sellers, AMD
|
|
- Dominik Witczak, AMD
|
|
*Contacts*::
|
|
- Daniel Rakos, AMD
|
|
|
|
This extension introduces the possibility for the application to control the
|
|
order of primitive rasterization. In unextended Vulkan, the following
|
|
stages are guaranteed to execute in _API order_:
|
|
|
|
* depth bounds test
|
|
* stencil test, stencil op, and stencil write
|
|
* depth test and depth write
|
|
* occlusion queries
|
|
* blending, logic op, and color write
|
|
|
|
This extension enables applications to opt into a relaxed, implementation
|
|
defined primitive rasterization order that may allow better parallel processing
|
|
of primitives and thus enabling higher primitive throughput. It is applicable in
|
|
cases where the primitive rasterization order is known to not affect the output
|
|
of the rendering or any differences caused by a different rasterization order
|
|
are not a concern from the point of view of the application's purpose.
|
|
|
|
A few examples of cases when using the relaxed primitive rasterization order
|
|
would not have an effect on the final rendering:
|
|
|
|
* If the primitives rendered are known to not overlap in framebuffer space.
|
|
* If depth testing is used with a comparison operator of
|
|
ename:VK_COMPARE_OP_LESS, ename:VK_COMPARE_OP_LESS_OR_EQUAL,
|
|
ename:VK_COMPARE_OP_GREATER, or ename:VK_COMPARE_OP_GREATER_OR_EQUAL,
|
|
and the primitives rendered are known to not overlap in clip space.
|
|
* If depth testing is not used and blending is enabled for all attachments
|
|
with a commutative blend operator.
|
|
|
|
=== New Object Types
|
|
|
|
None
|
|
|
|
=== New Enum Constants
|
|
|
|
* Extending elink:VkStructureType:
|
|
** ename:VK_STRUCTURE_TYPE_PIPELINE_RASTERIZATION_STATE_RASTERIZATION_ORDER_AMD
|
|
|
|
=== New Enums
|
|
|
|
* elink:VkRasterizationOrderAMD
|
|
|
|
=== New Structures
|
|
|
|
* slink:VkPipelineRasterizationStateRasterizationOrderAMD
|
|
|
|
=== New Functions
|
|
|
|
None
|
|
|
|
=== Issues
|
|
|
|
1) How is this extension useful to application developers?
|
|
|
|
RESOLVED: Allows them to increase primitive throughput for cases when
|
|
strict API order rasterization is not important due to the nature of the
|
|
content, the configuration used, or the requirements towards the output of
|
|
the rendering.
|
|
|
|
2) How does this extension interact with content optimizations aiming to
|
|
reduce overdraw by appropriately ordering the input primitives?
|
|
|
|
RESOLVED: While the relaxed rasterization order might somewhat limit the
|
|
effectiveness of such content optimizations, most of the benefits of it
|
|
are expected to be retained even when the relaxed rasterization order is
|
|
used so applications are still recommended to apply these optimizations
|
|
even if they intend to use the extension.
|
|
|
|
3) Are there any guarantees about the primitive rasterization order when
|
|
using the new relaxed mode?
|
|
|
|
RESOLVED: No. The rasterization order is completely implementation
|
|
dependent in this case but in practice it is expected to partially still
|
|
follow the order of incoming primitives.
|
|
|
|
4) Does the new relaxed rasterization order have any adverse effect on
|
|
repeatability and other invariance rules of the API?
|
|
|
|
RESOLVED: Yes, in the sense that it extends the list of exceptions when
|
|
the repeatability requirement doesn't apply.
|
|
|
|
=== Examples
|
|
|
|
None
|
|
|
|
=== Issues
|
|
|
|
None
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2016-04-25 (Daniel Rakos)
|
|
- Initial draft.
|