| commit | 54587dc9ccc739b1b2649d71de20583c3e12ddcb | [log] [tgz] |
|---|---|---|
| author | Danylo Piliaiev <[email protected]> | Mon Dec 08 13:22:19 2025 |
| committer | Charles Giessen <[email protected]> | Mon Dec 08 20:17:40 2025 |
| tree | 9160cb5bf9e2e614c5da77aa419d13e3da8c3c82 | |
| parent | 8542e6dcfc6daef20d561220f1d91a02c25d95b2 [diff] |
vulkaninfo: Fix running under RenderDoc RenderDoc allows only one simultaneously existing logical device, and vulkaninfo doesn't have a real need to keep them simultaneously alive. Running vulkaninfo under RenderDoc is useful to get a Vulkan profile that will represent the RenderDoc capabilities on the current GPU, which can be useful to, e.g., make a gfxreconstruct trace that will be later capturable by RenderDoc. Signed-off-by: Danylo Piliaiev <[email protected]>
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 this repository which correspond to a new Vulkan specification release are tagged using the following format: v<version> (e.g., v1.3.266).
Note: Marked version releases have undergone thorough testing but do not imply the same quality level as SDK tags. SDK tags follow the vulkan-sdk-<version>.<patch> format (e.g., vulkan-sdk-1.3.266.0).
This scheme was adopted following the 1.3.266 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.