mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-01-10 14:05:45 +00:00
911a764694
* Update release number to 87.
Public Issues:
* Merge flink:vkCmdPipelineBarrier self-dependency barrier VUs referring
to the same subpass dependency (public pull request 756).
* Describe default value of `"optional"` attribute in the registry schema
document (public issue 769)
* Fix links in <<VK_NVX_raytracing>> extension (public pull request 805).
* Mark the <<VK_KHR_mir_surface>> extension obsolete (see public issue 814
- does not close this, however).
* Fix missing endif in Image Creation block (public issue 817).
Internal Issues:
* Clarify that the compressed texture formats corresponding to
<<features-features-textureCompressionETC2>>,
<<features-features-textureCompressionASTC_LDR>>, and
<<features-features-textureCompressionBC>> is not contingent on the
feature bits, and may be supported even if the features are not enabled
(internal issue 663).
* Clarify that code:FragStencilRefEXT is output only in the
<<interfaces-builtin-variables, Built-In Variables>> section (internal
issue 1173).
* Identify and correct many overly-aggressive uses of "`undefined`", and
narrow them down, where straightforward to do so. Mark such resolved
uses of "`undefined`" with the custom undefined: macro. Add a new
<<writing-undefined, Describing Undefined Behavior>> section (internal
issue 1267).
* Don't require code:inline_uniform_block descriptors to be populated
before use in the flink:vkAllocateDescriptorSets section (internal issue
1380).
* Allow suppressing inline SVG images by controlling this with an
attribute set in the Makefile, rather than the explicit [%inline]
directive (internal issue 1391).
* Mark 'Khronos' as a registered trademark in several places, now that it
is one.
* Fix typo in the <<VK_KHR_shader_atomic_int64>> appendix using the GLSL
naming of the compare exchange op when referring to the SPIR-V op.
* Specify in the flink:vkGetPhysicalDeviceQueueFamilyProperties section
that all implementations must support at least one queue family, and
that every queue family must contain at least one queue.
* Make slink:VkPipelineDynamicStateCreateInfo::pname:dynamicStateCount,
slink:VkSampleLocationsInfoEXT::pname:sampleLocationsPerPixel, and
slink:VkSampleLocationsInfoEXT::pname:sampleLocationsCount optional, to
fix bogus implicit valid usage checks that were causing failures in the
conformance tests.
* Fix vendor tag in reserved extension 237 constants. Does not affect
anything since it's just a placeholder, but this should avoid further
comments.
* Minor markup fixes in some extension appendices.
New Extensions:
* `<<VK_FUCHSIA_imagepipe_surface>>`
63 lines
1.7 KiB
Plaintext
63 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
|