1// Copyright 2017-2021 The Khronos Group Inc. 2// 3// SPDX-License-Identifier: CC-BY-4.0 4 5include::{generated}/meta/{refprefix}VK_EXT_depth_range_unrestricted.txt[] 6 7=== Other Extension Metadata 8 9*Last Modified Date*:: 10 2017-06-22 11*Contributors*:: 12 - Daniel Koch, NVIDIA 13 - Jeff Bolz, NVIDIA 14 15=== Description 16 17This extension removes the slink:VkViewport pname:minDepth and 18pname:maxDepth restrictions that the values must be between `0.0` and `1.0`, 19inclusive. 20It also removes the same restriction on 21slink:VkPipelineDepthStencilStateCreateInfo pname:minDepthBounds and 22pname:maxDepthBounds. 23Finally it removes the restriction on the pname:depth value in 24slink:VkClearDepthStencilValue. 25 26include::{generated}/interfaces/VK_EXT_depth_range_unrestricted.txt[] 27 28=== Issues 29 301) How do slink:VkViewport pname:minDepth and pname:maxDepth values outside 31of the `0.0` to `1.0` range interact with 32<<vertexpostproc-clipping,Primitive Clipping>>? 33 34*RESOLVED*: The behavior described in <<vertexpostproc-clipping,Primitive 35Clipping>> still applies. 36If depth clamping is disabled the depth values are still clipped to [eq]#0 37{leq} z~c~ {leq} w~c~# before the viewport transform. 38If depth clamping is enabled the above equation is ignored and the depth 39values are instead clamped to the slink:VkViewport pname:minDepth and 40pname:maxDepth values, which in the case of this extension can be outside of 41the `0.0` to `1.0` range. 42 432) What happens if a resulting depth fragment is outside of the `0.0` to 44`1.0` range and the depth buffer is fixed-point rather than floating-point? 45 46*RESOLVED*: The supported range of a fixed-point depth buffer is `0.0` to 47`1.0` and depth fragments are clamped to this range. 48 49=== Version History 50 51 * Revision 1, 2017-06-22 (Piers Daniell) 52 - Internal revisions 53