Vulkan-Docs/appendices/VK_NV_scissor_exclusive.txt

72 lines
1.8 KiB
Plaintext

include::meta/VK_NV_scissor_exclusive.txt[]
*Last Modified Date*::
2018-07-31
*IP Status*::
No known IP claims.
*Interactions and External Dependencies*::
None
*Contributors*::
- Pat Brown, NVIDIA
- Jeff Bolz, NVIDIA
- Piers Daniell, NVIDIA
- Daniel Koch, NVIDIA
This extension adds support for an exclusive scissor test to Vulkan.
The exclusive scissor test behaves like the scissor test, except that the
exclusive scissor test fails for pixels inside the corresponding rectangle
and passes for pixels outside the rectangle.
If the same rectangle is used for both the scissor and exclusive scissor
tests, the exclusive scissor test will pass if and only if the scissor test
fails.
=== New Object Types
None.
=== New Enum Constants
* Extending elink:VkStructureType
** ename:VK_STRUCTURE_TYPE_PIPELINE_EXCLUSIVE_SCISSOR_STATE_CREATE_INFO_NV
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXCLUSIVE_SCISSOR_FEATURES_NV
* Extending elink:VkDynamicState
** ename:VK_DYNAMIC_STATE_EXCLUSIVE_SCISSOR_NV
=== New Enums
None.
=== New Structures
* slink:VkPhysicalDeviceExclusiveScissorFeaturesNV
* slink:VkPipelineExclusiveScissorStateCreateInfoNV
=== New Functions
* flink:vkCmdSetExclusiveScissorNV
=== New Built-In Variables
None.
=== New SPIR-V Capabilities
None.
=== Issues
1) For the scissor test, the viewport state must be created with a matching
number of scissor and viewport rectangles.
Should we have the same requirement for exclusive scissors?
*RESOLVED*: For exclusive scissors, we relax this requirement and allow an
exclusive scissor rectangle count that is either zero or equal to the number
of viewport rectangles.
If you pass in an exclusive scissor count of zero, the exclusive scissor
test is treated as disabled.
=== Version History
* Revision 1, 2018-07-31 (Pat Brown)
- Internal revisions