mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-01-30 08:05:44 +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`
96 lines
3.1 KiB
Plaintext
96 lines
3.1 KiB
Plaintext
// Copyright (c) 2016-2017 Khronos Group. This work is licensed under a
|
|
// Creative Commons Attribution 4.0 International License; see
|
|
// http://creativecommons.org/licenses/by/4.0/
|
|
|
|
include::meta/VK_KHR_maintenance1.txt[]
|
|
|
|
*Status*::
|
|
Draft
|
|
*Last Modified Date*::
|
|
2016-10-26
|
|
*Contributors*::
|
|
- Dan Ginsburg, Valve
|
|
- Daniel Koch, NVIDIA
|
|
- Daniel Rakos, AMD
|
|
- Jan-Harald Fredriksen, ARM
|
|
- Jason Ekstrand, Intel
|
|
- Jeff Bolz, NVIDIA
|
|
- Jesse Hall, Google
|
|
- John Kessenich, Google
|
|
- Michael Worcester, Imagination Technologies
|
|
- Neil Henning, Codeplay Software Ltd.
|
|
- Piers Daniell, NVIDIA
|
|
- Slawomir Grajewski, Intel
|
|
- Tobias Hector, Imagination Technologies
|
|
- Tom Olson, ARM
|
|
|
|
+VK_KHR_maintenance1+ adds a collection of minor features that were
|
|
intentionally left out or overlooked from the original Vulkan 1.0 release.
|
|
|
|
The new features are as follows:
|
|
|
|
* Allow 2D and 2D array image views to be created from 3D images, which
|
|
can then be used as color framebuffer attachments.
|
|
This allows applications to render to slices of a 3D image.
|
|
* Support flink:vkCmdCopyImage between 2D array layers and 3D slices.
|
|
This extension allows copying from layers of a 2D array image to slices
|
|
of a 3D image and vice versa.
|
|
* Allow negative height to be specified in the
|
|
slink::VkViewport::pname:height field to perform y-inversion of the
|
|
clip-space to framebuffer-space transform.
|
|
This allows apps to avoid having to use gl_Position.y = -gl_Position.y
|
|
in shaders also targeting other APIs.
|
|
* Allow implementations to express support for doing just transfers and
|
|
clears of image formats that they otherwise support no other format
|
|
features for.
|
|
This is done by adding new format feature flags
|
|
ename:VK_FORMAT_FEATURE_TRANSFER_SRC_BIT_KHR and
|
|
ename:VK_FORMAT_FEATURE_TRANSFER_DST_BIT_KHR.
|
|
* Support flink:vkCmdFillBuffer on transfer-only queues.
|
|
Previously flink:vkCmdFillBuffer was defined to only work on command
|
|
buffers allocated from command pools which support graphics or compute
|
|
queues.
|
|
It is now allowed on queues that just support transfer operations.
|
|
* Fix the inconsistency of how error conditions are returned between the
|
|
flink:vkCreateGraphicsPipelines and flink:vkCreateComputePipelines
|
|
functions and the flink:vkAllocateDescriptorSets and
|
|
flink:vkAllocateCommandBuffers functions.
|
|
* Add new ename:VK_ERROR_OUT_OF_POOL_MEMORY_KHR error so implementations
|
|
can give a more precise reason for flink:vkAllocateDescriptorSets
|
|
failures.
|
|
* Add a new command flink:vkTrimCommandPoolKHR which gives the
|
|
implementation an opportunity to release any unused command pool memory
|
|
back to the system.
|
|
|
|
=== New Object Types
|
|
|
|
None.
|
|
|
|
=== New Enum Constants
|
|
|
|
* ename:VK_ERROR_OUT_OF_POOL_MEMORY_KHR
|
|
* ename:VK_FORMAT_FEATURE_TRANSFER_SRC_BIT_KHR
|
|
* ename:VK_FORMAT_FEATURE_TRANSFER_DST_BIT_KHR
|
|
* ename:VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT_KHR
|
|
|
|
=== New Enums
|
|
|
|
None.
|
|
|
|
=== New Structures
|
|
|
|
None.
|
|
|
|
=== New Functions
|
|
|
|
* flink:vkTrimCommandPoolKHR
|
|
|
|
=== Issues
|
|
|
|
None.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2016-10-26 (Piers Daniell)
|
|
- Internal revisions
|