Change log for June 24, 2017 Vulkan 1.0.53 spec update:
* Bump API patch number and header version number to 53 for this update.
Github Issues:
Internal Issues:
* Clarify mappings of coordinates for mutable, compatible image views in
slink:VkImageViewCreateInfo (internal issue 815).
* Make ename:VK_BIND_SFR_BIT require a logical device with multiple
physical devices, so that standard sparse image block dimensions are
only required on systems that support multi-GPU (internal issue 835).
* Convert all files from use of // refBegin .. // refEnd comments to
delimit ref pages, to use of open blocks, and update style guide
accordingly (internal issue 839).
* Add valid usage for slink:VkWriteDescriptorSet when performing updates
to a ename:VK_STORAGE_IMAGE descriptor with layout
ename:VK_IMAGE_LAYOUT_GENERAL.
* Add a hack to the validity generator script to support an odd
interaction between flink:vkCmdFillBuffer and an extension (internal
issue 853).
* Remove redundant text describing slink:VkBufferCreateInfo::pname:usage,
which was already covered by implicit valid usage (internal issue 854).
* Update implicit validity generator script to properly handle the
pname:sType and pname:pNext members of "returnedonly" structures
(internal issue 874).
* Note that slink:VkApplicationInfo::pname:pApplicationName &
slink:VkApplicationInfo::pname:pEngineName are optional, and add missing
implicit valid usage statements for flink:vkDestroyInstance.
* Added missing valid usage for flink:vkCmdWriteTimestamp to require a
timestamp query pool.
* Simplify and/or split "`non-atomic`" valid usage statements.
New Extensions:
* `VK_AMD_gpu_shader_int16`
* `VK_EXT_blend_operation_advanced`
* `VK_EXT_sampler_filter_minmax`
* `VK_NV_framebuffer_mixed_samples`
-----------------------------------------------------
Note: the 1.0.52 spec wasn't published on github, so the 1.0.53 release
combines both change sets.
-----------------------------------------------------
Change log for June 13, 2017 Vulkan 1.0.52 spec update:
* Bump API patch number and header version number to 52 for this update.
Github Issues:
Internal Issues:
* Clarify behavior when non-coherent memory has
<<memory-device-unmap-does-not-flush, not been flushed before being
unmapped>> (internal issue 819).
* Fix description of code:WorkgroupSize builtin to note it decorates an
object, not a variable (internal issue 836).
* Fix asciidoc attributes so that trailing '{plus}' symbols in [eq] style
equations are rendered properly (internal issue 845).
* Add language to the "`Extension Handles, Objects, Enums, and Typedefs`"
section of the Procedures and Conventions document stating that any new
handle type requires a corresponding entry in the elink:VkObjectType
enumerated type (internal issue 856).
* Update style guide to use slink macro for Vulkan handle type names, and
define narrow conditions under which to use the *name and *text macros
instead of *link (internal issue 886).
* Add a dependency of the <<VK_KHX_device_group,VK_KHX_device_group>>
extension on VK_KHX_device_group_creation to +vk.xml+ and the extension
appendix.
* Change the copyright on Vulkan specification asciidoc *source* files to
CC-BY 4.0, and update the proprietary Khronos copyright applied to the
generated *output* formats (internal issue 327). This enables broader
re-use and modification of the Vulkan specification sources, while not
affecting the Reciprocal IP License between Vulkan Adopters and Working
Group Members.
New Extensions:
* `VK_NV_fill_rectangle`
* `VK_NV_fragment_coverage_to_color`
2017-06-27 02:32:10 +00:00
|
|
|
// Copyright (c) 2014-2017 Khronos Group. This work is licensed under a
|
|
|
|
|
// Creative Commons Attribution 4.0 International License; see
|
|
|
|
|
// http://creativecommons.org/licenses/by/4.0/
|
2016-09-17 04:22:17 +00:00
|
|
|
|
Change log for September 5, 2017 Vulkan 1.0.60 spec update:
* 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`
2017-09-04 10:06:55 +00:00
|
|
|
include::meta/VK_KHR_win32_surface.txt[]
|
2016-08-28 10:47:19 +00:00
|
|
|
|
2016-09-17 04:22:17 +00:00
|
|
|
*Last Modified Date*::
|
2017-06-05 03:48:43 +00:00
|
|
|
2017-04-24
|
2016-08-28 10:47:19 +00:00
|
|
|
*IP Status*::
|
2016-09-17 04:22:17 +00:00
|
|
|
No known IP claims.
|
2016-08-28 10:47:19 +00:00
|
|
|
*Contributors*::
|
|
|
|
|
- Patrick Doane, Blizzard
|
|
|
|
|
- Jason Ekstrand, Intel
|
|
|
|
|
- Ian Elliott, LunarG
|
|
|
|
|
- Courtney Goeltzenleuchter, LunarG
|
|
|
|
|
- Jesse Hall, Google
|
|
|
|
|
- James Jones, NVIDIA
|
|
|
|
|
- Antoine Labour, Google
|
|
|
|
|
- Jon Leech, Khronos
|
|
|
|
|
- David Mao, AMD
|
|
|
|
|
- Norbert Nopper, Freescale
|
|
|
|
|
- Alon Or-bach, Samsung
|
|
|
|
|
- Daniel Rakos, AMD
|
|
|
|
|
- Graham Sellers, AMD
|
|
|
|
|
- Ray Smith, ARM
|
|
|
|
|
- Jeff Vigil, Qualcomm
|
|
|
|
|
- Chia-I Wu, LunarG
|
|
|
|
|
|
2017-12-20 17:00:32 +00:00
|
|
|
The `VK_KHR_win32_surface` extension is an instance extension.
|
Change log for January 23, 2017 Vulkan 1.0.39 spec update:
* Bump API patch number and header version number to 39 for this update.
Github Issues:
* Clarified that only accesses via the specified buffer/image subresource
ranges are included in the access scopes (public issue 306).
* Add missing valid usage statements for flink:vkCreateComputePipelines
and flink:vkCreateGraphicsPipelines (public issue 427).
Internal Issues:
* Add a Note to the <<invariance,Invariance>> appendix about a difference
between OpenGL and Vulkan with regards to how primitives derived from
offsets are handled (internal issue 355).
* Add the +<<VK_KHR_get_physical_device_properties2>>+,
+<<VK_KHR_maintenance1>>+, and +<<VK_KHR_shader_draw_parameters>>+
extensions (internal issue 448).
* Add the +<<VK_EXT_shader_subgroup_vote>>+ and
+<<VK_EXT_shader_subgroup_ballot>>+ extensions (internal issue 449).
* Update the texture level-of-detail equation in the
<<textures-scale-factor,Scale Factor Operation>> section to better
approximate the ellipse major and minor axes (internal issue 547).
* Forbid non-explicitly allowed uses of interface decorations in the
introduction to the <<interfaces,Shader Interfaces>> chapter (internal
issue 607).
* Replace use of MathJax with KaTeX, for improved load-time performance as
well as avoiding the scrolling-and-scrolling behavior due to MathJax
asynchronous rendering when loading at an anchor inside the spec. This
change also requires moving to HTML5 output for the spec instead of
XHTML, and there is a visible difference in that the chapter navigation
index is now in a scrollable sidebar instead of at the top of the
document. We may or may not retain the nav sidebar based on feedback
(internal issue 613).
* Improve consistency of markup and formatting in extension appendices
(internal issue 631).
Other Issues:
* Add explicit valid usage statements to slink:VkImageCopy requiring that
the source and destination layer ranges be contained in their respective
source and destination images.
* Add valid usage language for swapchain of flink:vkAcquireNextImage. If
the swapchain has been replaced, then it should not be passed to
flink:vkAcquireNextImage.
* Add a valid usage statement to flink:vkCreateImageView, that the image
must have been created with an appropriate usage bit set.
* Noted that slink:VkDisplayPresentInfoKHR is a valid extension of
slink:VkPresentInfoKHR in the <<wsi_swapchain,WSI Swapchain>> section.
* Update valid usage for flink:vkCmdSetViewport and flink:vkCmdSetScissor
to account for the multiple viewport feature. If the feature is not
enabled, the parameters for these functions have required values that
are defined in the <<features-features-multiViewport,multiple
viewports>> section of the spec but were not reflected in the valid
usage text for these functions.
* Add the +<<VK_EXT_swapchain_colorspace>>+ extension defining common
color spaces.
2017-01-18 04:11:25 +00:00
|
|
|
It provides a mechanism to create a slink:VkSurfaceKHR object (defined by
|
2017-12-20 17:00:32 +00:00
|
|
|
the <<VK_KHR_surface>> extension) that refers to a Win32 code:HWND, as well
|
|
|
|
|
as a query to determine support for rendering to the windows desktop.
|
2016-08-28 10:47:19 +00:00
|
|
|
|
|
|
|
|
=== New Object Types
|
|
|
|
|
|
|
|
|
|
None
|
|
|
|
|
|
|
|
|
|
=== New Enum Constants
|
|
|
|
|
|
2017-06-05 03:48:43 +00:00
|
|
|
* Extending elink:VkStructureType:
|
2016-08-28 10:47:19 +00:00
|
|
|
** ename:VK_STRUCTURE_TYPE_WIN32_SURFACE_CREATE_INFO_KHR
|
|
|
|
|
|
|
|
|
|
=== New Enums
|
|
|
|
|
|
|
|
|
|
None
|
|
|
|
|
|
|
|
|
|
=== New Structures
|
|
|
|
|
|
|
|
|
|
* slink:VkWin32SurfaceCreateInfoKHR
|
|
|
|
|
|
|
|
|
|
=== New Functions
|
|
|
|
|
|
|
|
|
|
* flink:vkCreateWin32SurfaceKHR
|
|
|
|
|
* flink:vkGetPhysicalDeviceWin32PresentationSupportKHR
|
|
|
|
|
|
|
|
|
|
=== Issues
|
|
|
|
|
|
|
|
|
|
1) Does Win32 need a way to query for compatibility between a particular
|
Change log for January 23, 2017 Vulkan 1.0.39 spec update:
* Bump API patch number and header version number to 39 for this update.
Github Issues:
* Clarified that only accesses via the specified buffer/image subresource
ranges are included in the access scopes (public issue 306).
* Add missing valid usage statements for flink:vkCreateComputePipelines
and flink:vkCreateGraphicsPipelines (public issue 427).
Internal Issues:
* Add a Note to the <<invariance,Invariance>> appendix about a difference
between OpenGL and Vulkan with regards to how primitives derived from
offsets are handled (internal issue 355).
* Add the +<<VK_KHR_get_physical_device_properties2>>+,
+<<VK_KHR_maintenance1>>+, and +<<VK_KHR_shader_draw_parameters>>+
extensions (internal issue 448).
* Add the +<<VK_EXT_shader_subgroup_vote>>+ and
+<<VK_EXT_shader_subgroup_ballot>>+ extensions (internal issue 449).
* Update the texture level-of-detail equation in the
<<textures-scale-factor,Scale Factor Operation>> section to better
approximate the ellipse major and minor axes (internal issue 547).
* Forbid non-explicitly allowed uses of interface decorations in the
introduction to the <<interfaces,Shader Interfaces>> chapter (internal
issue 607).
* Replace use of MathJax with KaTeX, for improved load-time performance as
well as avoiding the scrolling-and-scrolling behavior due to MathJax
asynchronous rendering when loading at an anchor inside the spec. This
change also requires moving to HTML5 output for the spec instead of
XHTML, and there is a visible difference in that the chapter navigation
index is now in a scrollable sidebar instead of at the top of the
document. We may or may not retain the nav sidebar based on feedback
(internal issue 613).
* Improve consistency of markup and formatting in extension appendices
(internal issue 631).
Other Issues:
* Add explicit valid usage statements to slink:VkImageCopy requiring that
the source and destination layer ranges be contained in their respective
source and destination images.
* Add valid usage language for swapchain of flink:vkAcquireNextImage. If
the swapchain has been replaced, then it should not be passed to
flink:vkAcquireNextImage.
* Add a valid usage statement to flink:vkCreateImageView, that the image
must have been created with an appropriate usage bit set.
* Noted that slink:VkDisplayPresentInfoKHR is a valid extension of
slink:VkPresentInfoKHR in the <<wsi_swapchain,WSI Swapchain>> section.
* Update valid usage for flink:vkCmdSetViewport and flink:vkCmdSetScissor
to account for the multiple viewport feature. If the feature is not
enabled, the parameters for these functions have required values that
are defined in the <<features-features-multiViewport,multiple
viewports>> section of the spec but were not reflected in the valid
usage text for these functions.
* Add the +<<VK_EXT_swapchain_colorspace>>+ extension defining common
color spaces.
2017-01-18 04:11:25 +00:00
|
|
|
physical device and a specific screen? Compatibility between a physical
|
|
|
|
|
device and a window generally only depends on what screen the window is on.
|
|
|
|
|
However, there is not an obvious way to identify a screen without already
|
|
|
|
|
having a window on the screen.
|
|
|
|
|
|
|
|
|
|
*RESOLVED*: No.
|
|
|
|
|
While it may be useful, there is not a clear way to do this on Win32.
|
|
|
|
|
However, a method was added to query support for presenting to the windows
|
|
|
|
|
desktop as a whole.
|
2016-08-28 10:47:19 +00:00
|
|
|
|
2017-11-08 23:09:27 +00:00
|
|
|
2) If a native window object (code:HWND) is used by one graphics API, and
|
|
|
|
|
then is later used by a different graphics API (one of which is Vulkan), can
|
|
|
|
|
these uses interfere with each other?
|
2017-06-05 03:48:43 +00:00
|
|
|
|
|
|
|
|
*RESOLVED*: Yes.
|
|
|
|
|
|
|
|
|
|
Uses of a window object by multiple graphics APIs results in undefined
|
|
|
|
|
behavior.
|
|
|
|
|
Such behavior may succeed when using one Vulkan implementation but fail when
|
|
|
|
|
using a different Vulkan implementation.
|
|
|
|
|
Potential failures include:
|
|
|
|
|
|
|
|
|
|
* Creating then destroying a flip presentation model DXGI swapchain on a
|
|
|
|
|
window object can prevent flink:vkCreateSwapchainKHR from succeeding on
|
|
|
|
|
the same window object.
|
|
|
|
|
|
|
|
|
|
* Creating then destroying a slink:VkSwapchainKHR on a window object can
|
|
|
|
|
prevent creation of a bitblt model DXGI swapchain on the same window
|
|
|
|
|
object.
|
|
|
|
|
|
|
|
|
|
* Creating then destroying a slink:VkSwapchainKHR on a window object can
|
2017-11-08 23:09:27 +00:00
|
|
|
effectively code:SetPixelFormat to a different format than the format
|
|
|
|
|
chosen by an OpenGL application.
|
2017-06-05 03:48:43 +00:00
|
|
|
|
|
|
|
|
* Creating then destroying a slink:VkSwapchainKHR on a window object on one
|
2017-11-08 23:09:27 +00:00
|
|
|
slink:VkPhysicalDevice can prevent flink:vkCreateSwapchainKHR from
|
|
|
|
|
succeeding on the same window object, but on a different
|
|
|
|
|
slink:VkPhysicalDevice that is associated with a different Vulkan ICD.
|
2017-06-05 03:48:43 +00:00
|
|
|
|
|
|
|
|
In all cases the problem can be worked around by creating a new window
|
|
|
|
|
object.
|
|
|
|
|
|
|
|
|
|
Technical details include:
|
|
|
|
|
|
|
|
|
|
* Creating a DXGI swapchain over a window object can alter the object for
|
|
|
|
|
the remainder of its lifetime.
|
|
|
|
|
The alteration persists even after the DXGI swapchain has been destroyed.
|
|
|
|
|
This alteration can make it impossible for a conformant Vulkan
|
|
|
|
|
implementation to create a slink:VkSwapchainKHR over the same window
|
|
|
|
|
object.
|
|
|
|
|
Mention of this alteration can be found in the remarks section of the
|
2017-11-08 23:09:27 +00:00
|
|
|
MSDN documentation for code:DXGI_SWAP_EFFECT.
|
2017-06-05 03:48:43 +00:00
|
|
|
|
2017-11-08 23:09:27 +00:00
|
|
|
* Calling GDI's code:SetPixelFormat (needed by OpenGL's WGL layer) on a
|
|
|
|
|
window object alters the object for the remainder of its lifetime.
|
|
|
|
|
The MSDN documentation for code:SetPixelFormat explains that a window
|
|
|
|
|
object's pixel format can be set only one time.
|
2017-06-05 03:48:43 +00:00
|
|
|
|
|
|
|
|
* Creating a slink:VkSwapchainKHR over a window object can alter the object
|
|
|
|
|
for the remaining life of its lifetime.
|
|
|
|
|
Either of the above alterations may occur as a side-effect of
|
|
|
|
|
slink:VkSwapchainKHR.
|
|
|
|
|
|
2016-08-28 10:47:19 +00:00
|
|
|
=== Version History
|
|
|
|
|
|
|
|
|
|
* Revision 1, 2015-09-23 (Jesse Hall)
|
|
|
|
|
- Initial draft, based on the previous contents of VK_EXT_KHR_swapchain
|
|
|
|
|
(later renamed VK_EXT_KHR_surface).
|
|
|
|
|
|
|
|
|
|
* Revision 2, 2015-10-02 (James Jones)
|
Change log for September 6, 2016 Vulkan 1.0.26 spec update:
* Bump API patch number and header version number to 26 for this update.
Github Issues:
* Bring sample code in the +VK_KHR_surface+ and +VK_KHR_swapchain+
extension summary appendices up to date, and note they will be replaced
with pointers to the LunarG SDK examples in the future (public issue
279).
* Add a new <<fundamentals-commandsyntax-results-lifetime,Lifetime of
Retrieved Results>> section specifying that ftext:vkGet* and
ftext:VkEnumerate* results are invariant unless otherwise specified, and
specify behavior for individual commands which are not invariant (public
issue 280).
* Remove conflicting definition of
slink:VkDisplayPlaneCapabilitiesKHR::pname:maxSrcPosition and clean up
language of the remaining definition (public issue 351).
* Fix many minor spelling errors and add rules to the style guide to
prevent recurrences (public issue 352).
Internal Issues:
* Remove redundant descriptions of the etext:VK_USE_PLATFORM_* macros from
the <<wsi,Window System Integration>> chapter in favor of the
description in the <<boilerplate-wsi-header,Window System-Specific
Header Control>> appendix (internal issue 6).
* Replace misleading 'can: be destroyed when not X' with more correct
'must: not be destroyed while X' in the
<<fundamentals-objectmodel-lifetime,Object Lifetime>> section. Disallow
destroying a pipeline layout while a command buffer using it is
recording (internal issue 241).
* Clarify that ename:VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT is valid for
all images used as attachments in elink:VkImageUsageFlagBits and the
slink:VkImageLayout validity language (internal issue 320).
* Note that <<extended-functionality-layers,Layers>> may wrap object
handles, but that this is a generally discouraged. A link to additional
information in the documentation for layer authors is provided (issue
398)
* Replace the mustnot: and shouldnot: macros with equivalent must: not and
should: not to get rid of non-English words while still highlighting
normative language (internal issue 407).
* Disallow creating multisampled images with
ename:VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT in the slink:VkImageLayout
validity language and the <<features-supported-sample-counts,Supported
Sample Counts>> section (internal issue 445).
* Fix typo so that flink:vkCmdDrawIndexedIndirect is defined in terms of
flink:vkCmdDrawIndexed rather than flink:vkCmdDrawIndirect (internal
issue 446).
* Reorganize the per-extension information sections to all be in the
<<extensions,Layers & Extensions>> appendix. Also fix a typo in
+VK_IMG_filter_cubic+ which incorrectly identified it as a +KHR+
extension (internal issue 461).
Other Issues:
* Use asciidoc markup instead of latexmath to simplify diagrams in the
<<features-formats-non-packed,byte mapping tables>> for color formats.
* Fix a markup problem with the wildcarded enumerant names in a NOTE in
the <<textures-texel-replacement,Texel Replacement>> section.
* Fix missing attributes in the XML interface for
elink:VkExternalMemoryHandleTypeFlagBitsNV and
elink:VkExternalMemoryFeatureFlagBitsNV (KhronosGroup/Vulkan-Hpp issue
#25)
* Cleanup reference page builds so only core pages are built for releases.
2016-09-06 13:17:27 +00:00
|
|
|
- Added presentation support query for win32 desktops.
|
2016-08-28 10:47:19 +00:00
|
|
|
|
|
|
|
|
* Revision 3, 2015-10-26 (Ian Elliott)
|
|
|
|
|
- Renamed from VK_EXT_KHR_win32_surface to VK_KHR_win32_surface.
|
|
|
|
|
|
|
|
|
|
* Revision 4, 2015-11-03 (Daniel Rakos)
|
|
|
|
|
- Added allocation callbacks to vkCreateWin32SurfaceKHR.
|
|
|
|
|
|
|
|
|
|
* Revision 5, 2015-11-28 (Daniel Rakos)
|
|
|
|
|
- Updated the surface create function to take a pCreateInfo structure.
|
2017-06-05 03:48:43 +00:00
|
|
|
|
|
|
|
|
* Revision 6, 2017-04-24 (Jeff Juliano)
|
|
|
|
|
- Add issue 2 addressing reuse of a native window object in a different
|
|
|
|
|
Graphics API, or by a different Vulkan ICD.
|
