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