mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-01-12 15:04:10 +00:00
0cc6bba634
* Bump API patch number and header version number to 61 for this update.
Github Issues:
* Provide alternate length attributes (altlen=) in the XML schema, for
those using length attributes to generate code instead of documentation
(public issue 555).
* Fix erroneous references to `latex:` being used for asciidoc math
markup, rather than `latexmath:` (public pull request 556).
* Add author ID to XML for Kazan software renderer (public pull request
557).
Internal Issues:
* Add the <<fundamentals-abi,Application Binary Interface>> section
describing platform ABI requirements and recommendations, add examples
of function and function pointer declarations to the
<<boilerplate-platform-specific-calling-conventions, Platform-Specific
Calling Conventions>> section, and remove related language that existed
elsewhere in the specification (internal issue 64).
* Describe where to document valid usage interactions of chained
structures in the style guide, and fix one case now appearing in
slink:VkBufferCreateInfo instead of the child
slink:VkDedicatedAllocationBufferCreateInfoNV structure (internal issue
715).
* Add example to the style guide of describing enumerated types which are
empty when the spec is built without relevant extensions enabled, and
apply it to existing examples for
elink:VkDescriptorSetLayoutCreateFlagBits and
elink:VkSubpassDescriptionFlagBits (internal issue 864).
* Add a note to the <<fundamentals-validusage-enums, Valid Usage for
Enumerated Types>> section that the special values suffixed with
etext:_BEGIN_RANGE, etext:_END_RANGE, etext:_RANGE_SIZE and
etext:_MAX_ENUM are not part of the API and should: not be used by
applications (internal issue 872).
* Added note to flink:vkCmdUpdateBuffers explaining the performance
penalty for copies done in this way, and why the upper copy limit is
what it is (internal issue 952).
* Update `VK_KHX_device_group` to split some functionality into the new
`VK_KHR_bind_memory2` extension, and rename that functionality (internal
issue 969).
* Remove *Status* fields from extension appendices, since they are by
definition published and complete by the time they reach the public
github repository (internal issue 973).
Other Issues:
* Update Data Format specification dependency to version 1.2 and change
references to DF sections accordingly.
* Update XML to make the pname:pAllocator parameter of
flink:vkRegisterDeviceEventEXT and flink:vkRegisterDisplayEventEXT in
the `VK_EXT_display_control` extension as optional.
New Extensions:
* `VK_KHR_bind_memory2`
* `VK_KHR_image_format_list`
* `VK_KHR_maintenance2`
* `VK_KHR_sampler_ycbcr_conversion`
56 lines
1.7 KiB
Plaintext
56 lines
1.7 KiB
Plaintext
include::meta/VK_EXT_depth_range_unrestricted.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2017-06-22
|
|
*Contributors*::
|
|
- Daniel Koch, NVIDIA
|
|
- Jeff Bolz, NVIDIA
|
|
|
|
This extension removes the slink:VkViewport pname:minDepth and
|
|
pname:maxDepth restrictions that the values must be between `0.0` and `1.0`,
|
|
inclusive.
|
|
It also removes the same restriction on
|
|
slink:VkPipelineDepthStencilStateCreateInfo pname:minDepthBounds and
|
|
pname:maxDepthBounds.
|
|
Finally it removes the restriction on the pname:depth value in
|
|
slink:VkClearDepthStencilValue.
|
|
|
|
=== New Object Types
|
|
None.
|
|
|
|
=== New Enum Constants
|
|
None.
|
|
|
|
=== New Enums
|
|
None.
|
|
|
|
=== New Structures
|
|
None.
|
|
|
|
=== New Functions
|
|
None.
|
|
|
|
=== Issues
|
|
1) How do slink:VkViewport pname:minDepth and pname:maxDepth values outside
|
|
of the `0.0` to `1.0` range interact with
|
|
<<vertexpostproc-clipping,Primitive Clipping>>?
|
|
|
|
**RESOLVED**: The behavior described in <<vertexpostproc-clipping,Primitive
|
|
Clipping>> still applies.
|
|
If depth clamping is disabled the depth values are still clipped to [eq]#0
|
|
{leq} z~c~ {leq} w~c~# before the viewport transform.
|
|
If depth clamping is enabled the above equation is ignored and the depth
|
|
values are instead clamped to the slink:VkViewport pname:minDepth and
|
|
pname:maxDepth values, which in the case of this extension can be outside of
|
|
the `0.0` to `1.0` range.
|
|
|
|
2) What happens if a resulting depth fragment is outside of the `0.0` to
|
|
`1.0` range and the depth buffer is fixed-point rather than floating-point?
|
|
|
|
**RESOLVED**: The supported range of a fixed-point depth buffer is `0.0` to
|
|
`1.0` and depth fragments are clamped to this range.
|
|
|
|
=== Version History
|
|
* Revision 1, 2017-06-22 (Piers Daniell)
|
|
- Internal revisions
|