mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-01-12 06:54:14 +00:00
b9e9296cd8
* 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`
159 lines
5.1 KiB
Plaintext
159 lines
5.1 KiB
Plaintext
// 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/
|
|
|
|
[[VK_KHR_win32_surface]]
|
|
== VK_KHR_win32_surface
|
|
|
|
*Name String*::
|
|
+VK_KHR_win32_surface+
|
|
*Extension Type*::
|
|
Instance extension
|
|
*Registered Extension Number*::
|
|
10
|
|
*Last Modified Date*::
|
|
2017-04-24
|
|
*Revision*::
|
|
6
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Dependencies*::
|
|
- This extension is written against version 1.0 of the Vulkan API.
|
|
- This extension requires +VK_KHR_surface+.
|
|
*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
|
|
*Contacts*::
|
|
- Jesse Hall, Google
|
|
- Ian Elliott, LunarG
|
|
|
|
|
|
The +VK_KHR_win32_surface+ extension is an instance extension.
|
|
It provides a mechanism to create a slink:VkSurfaceKHR object (defined by
|
|
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.
|
|
|
|
=== New Object Types
|
|
|
|
None
|
|
|
|
=== New Enum Constants
|
|
|
|
* Extending elink:VkStructureType:
|
|
** 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
|
|
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.
|
|
|
|
2) If a native window object (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?
|
|
|
|
*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
|
|
effectively SetPixelFormat to a different format than the format chosen
|
|
by an OpenGL application.
|
|
|
|
* Creating then destroying a slink:VkSwapchainKHR on a window object on one
|
|
VkPhysicalDevice can prevent flink:vkCreateSwapchainKHR from succeeding
|
|
on the same window object, but on a different VkPhysicalDevice that is
|
|
associated with a different Vulkan ICD.
|
|
|
|
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
|
|
MSDN documentation for DXGI_SWAP_EFFECT.
|
|
|
|
* Calling GDI's SetPixelFormat (needed by OpenGL's WGL layer) on a window
|
|
object alters the object for the remainder of its lifetime.
|
|
The MSDN documentation for SetPixelFormat explains that a window object's
|
|
pixel format can be set only one time.
|
|
|
|
* 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.
|
|
|
|
=== 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)
|
|
- Added presentation support query for win32 desktops.
|
|
|
|
* 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.
|
|
|
|
* 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.
|