mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-13 23:06:32 +00:00
df88ded281
* Bump API patch number and header version number to 60 for this update.
Github Issues:
* Document that <<queries-timestamps, Timestamp Queries>> can only be
meaningfully compared when they are written from the same queue (public
issue 216).
* Document that the `<extension>` tag `type` attribute is required for
non-disabled extensions (derived from, but does not close public issue
354).
* Clean up registry schema length attribute descriptions to be consistent
and correct (public issue 555).
Internal Issues:
* Replace as much of the hand-written extension appendix metadata as
possible with asciidoc includes generated from corresponding attributes
of +vk.xml+, and enhance the style guide to match. This avoids
inconsistencies between +vk.xml+ and the appendices, and produces a more
uniform style (internal issue 137).
* Remove the generated extDependency.{py,sh} files from the tree and
create them dynamically on demand instead, reducing merge conflicts
(internal issue 713).
* Add a prototype tool for generating in-place difference markup for
sections guarded by asciidoc conditionals, and new syntax for open
blocks to support it (internal issue 833).
* Remove unnecessary restriction of etext:*SYNC_FD_BIT_KHR external handle
types to the same physical device in the
slink:VkPhysicalDeviceIDPropertiesKHR,
flink:VkImportMemoryWin32HandleInfoKHR,
slink:VkImportFenceWin32HandleInfoKHR, slink:VkImportFenceFdInfoKHR,
slink:VkImportSemaphoreWin32HandleInfoKHR,
slink:VkImportSemaphoreFdInfoKHR
<<external-memory-handle-types-compatibility, External memory handle
types compatibility>>, <<external-semaphore-handle-types-compatibility,
External semaphore handle types compatibility>>, and
<<external-fence-handle-types-compatibility, External fence handle types
compatibility>> sections (internal issue 956).
Other Issues:
* Remove dependency of +VK_KHX_device_group+ on +VK_KHR_swapchain+ (there
is an interaction, but not a strict dependency), and add a new
`extension` attribute to the `<require` XML tag to allow classifying a
subset of interfaces of an extension as requiring another extension.
Update the registry schema and documentation accordingly.
New Extensions:
* `VK_AMD_shader_fragment_mask` (and related `GL_AMD_shader_fragment_mask`
GLSL extension)
* `VK_EXT_sample_locations`
* `VK_EXT_validation_cache`
58 lines
1.7 KiB
Plaintext
58 lines
1.7 KiB
Plaintext
include::meta/VK_EXT_depth_range_unrestricted.txt[]
|
|
|
|
*Status*::
|
|
Draft
|
|
*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
|