• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1include::meta/VK_EXT_direct_mode_display.txt[]
2
3*Last Modified Date*::
4    2016-12-13
5*IP Status*::
6    No known IP claims.
7*Contributors*::
8  - Pierre Boudier, NVIDIA
9  - James Jones, NVIDIA
10  - Damien Leone, NVIDIA
11  - Pierre-Loup Griffais, Valve
12  - Liam Middlebrook, NVIDIA
13
14This is extension, along with related platform exentions, allows
15applications to take exclusive control of displays associated with a native
16windowing system.
17This is especially useful for virtual reality applications that wish to hide
18HMDs (head mounted displays) from the native platform's display management
19system, desktop, and/or other applications.
20
21=== New Enum Constants
22
23None.
24
25=== New Enums
26
27None.
28
29=== New Structures
30
31None.
32
33=== New Functions
34
35  * flink:vkReleaseDisplayEXT
36
37=== Issues
38
391) Should this extension and its related platform-specific extensions
40leverage `<<VK_KHR_display>>`, or provide separate equivalent interfaces.
41
42*RESOLVED*: Use `<<VK_KHR_display>>` concepts and objects.
43`<<VK_KHR_display>>` can be used to enumerate all displays on the system,
44including those attached to/in use by a window system or native platform,
45but `<<VK_KHR_display_swapchain>>` will fail to create a swapchain on in-use
46displays.
47This extension and its platform-specific children will allow applications to
48grab in-use displays away from window systems and/or native platforms,
49allowing them to be used with `<<VK_KHR_display_swapchain>>`.
50
512) Are separate calls needed to acquire displays and enable direct mode?
52
53*RESOLVED*: No, these operations happen in one combined command.
54Acquiring a display puts it into direct mode.
55
56=== Version History
57
58 * Revision 1, 2016-12-13 (James Jones)
59   - Initial draft
60