mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-04 18:43:56 +00:00
5436521608
* Bump API patch number and header version number to 64 for this update.
Github Issues:
* Add chapter name to the PDF page footer (public pull request 458).
* Fix several mistaken references to the nonexistent etext:VK_DEVICE_LOST
status to etext:VK_ERROR_DEVICE_LOST (public pull request 502).
* Fix description of the tlink:PFN_vkDebugReportCallbackEXT debug report
callback function pointer to match the validation layer behavior (public
issue 534).
* Document experimental KHX extensions and alternate vendor author IDs
also ending in X in more detail in the <<extensions, Layers &
Extensions>> appendix, the extensions section of the style guide, and
the registry schema description document (public issues 536, 580).
* Fix references to ptext:pDepthStencil to properly refer to
pname:pDepthStencilState or pname:pRasterizationState as appropriate in
the slink:VkGraphicsPipelineCreateInfo description (public issue 542).
* Fix wrong parameter name in slink:VkPipelineMultisampleStateCreateInfo
valid usage (public pull request 571).
Internal Issues:
* Update the style guide to describe how to write LaTeX math expressions
in table cells (internal issue 908).
* Define how framebuffer-local dependencies work between subpasses with
the same or different numbers of samples, in the
slink:VkSubpassDescription and <<synchronization-framebuffer-regions,
Framebuffer Region Dependencies>> sections. This clarifies which samples
in an input attachment you are allowed to access after a
framebuffer-local dependency (internal issue 915).
* Specify which storage classes can have an initializer in the
<<spirvenv-module-validation, Validation Rules within a Module>> section
(internal issue 1023).
* Use "LOD" consistently for "level-of-detail", to eliminate spelling
inconsistencies. The term is already standardized in the Glossary
(internal issue 1027).
Other Issues:
* Fix false positives in Makefile dependencies when rules fail, by
deleting partially-made targets.
New Extensions:
* `VK_AMD_shader_info`
110 lines
3.4 KiB
Plaintext
110 lines
3.4 KiB
Plaintext
include::meta/VK_AMD_rasterization_order.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2016-04-25
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Contributors*::
|
|
- Matthaeus G. Chajdas, AMD
|
|
- Jaakko Konttinen, AMD
|
|
- Daniel Rakos, AMD
|
|
- Graham Sellers, AMD
|
|
- Dominik Witczak, 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 should: still 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 does not apply.
|
|
|
|
=== Examples
|
|
|
|
None
|
|
|
|
=== Issues
|
|
|
|
None
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2016-04-25 (Daniel Rakos)
|
|
- Initial draft.
|