commit | a25449cc6b58a3aa09fcf2c2d7fd4bfa15a32602 | [log] [tgz] |
---|---|---|
author | Charles Giessen <charles@lunarg.com> | Fri May 26 17:34:43 2023 -0600 |
committer | Charles Giessen <46324611+charles-lunarg@users.noreply.github.com> | Mon May 29 15:46:53 2023 -0600 |
tree | 5ddd264c2006e803f3a43023df17c91dbba338c0 | |
parent | fedb3b8ed39899eeb7c549cd50a380132b9dc948 [diff] |
vulkaninfo: Only enable necessary instance extensions Previously, vulkaninfo would enable all instance extensions, which caused validation errors to be generated. Now, vulkaninfo only enables extensions it knows it needs to, such as: VK_EXT_debug_report VK_KHR_get_physical_device_properties2 VK_KHR_portability_enumeration VK_KHR_surface <platform specific surface extensions> VK_KHR_get_surface_capabilities2 VK_KHR_surface_protected_capabilities
This project provides Vulkan tools and utilities that can assist development by enabling developers to verify their applications correct use of the Vulkan API.
The following components are available in this repository:
Please see the CONTRIBUTING.md file in this repository for more details. Please see the GOVERNANCE.md file in this repository for repository management details.
BUILD.md includes directions for building all components as well as running the vkcube demo applications.
Updates to the Vulkan-Tools
repository which correspond to a new Vulkan specification release are tagged using the following format: v<
version
>
(e.g., v1.1.96
).
Note: Marked version releases have undergone thorough testing but do not imply the same quality level as SDK tags. SDK tags follow the sdk-<
version
>.<
patch
>
format (e.g., sdk-1.1.92.0
).
This scheme was adopted following the 1.1.96 Vulkan specification release.
This work is released as open source under a Apache-style license from Khronos including a Khronos copyright.
See LICENSE.txt for a full list of licenses used in this repository.
While this project has been developed primarily by LunarG, Inc., there are many other companies and individuals making this possible: Valve Corporation, funding project development; Google providing significant contributions to the validation layers; Khronos providing oversight and hosting of the project.