This project provides the Khronos offical Vulkan SC validation layers.
Vulkan is an Explicit API, enabling direct control over how GPUs actually work. By design, minimal error checking is done inside a Vulkan driver. Applications have full control and responsibility for correct operation. Any errors in how Vulkan is used can result in a crash. This project provides Vulkan validation layers that can be enabled to assist development by enabling developers to verify their applications correct use of the Vulkan API.
For those who don't want to build from source, there are few ways to get working binaries to use
- The Vulkan SDK will have the most well tested versions of the layer
- For Android, each SDK tag will have binaries to download (example: vulkan-sdk-1.3.280.0 tag)
- Every change applied to the main branch runs through GitHub action and will produce artifacts of the latest commit.
Before submitting an issue to the validation layers or reaching out to the developers it may be prudent to reach out to the community first. These resources can be helpful to refine your issue, work out an application/driver bug, etc.
- Discord: https://discord.com/invite/vulkan
- Reddit: https://www.reddit.com/r/vulkan
- Stackoverflow: https://stackoverflow.com/questions/tagged/vulkan
- Slack: https://khr.io/slack
Vulkan SC is an API derived from Vulkan with various changes applied to fulfill the special requirements of safety critical applications. The Vulkan SC API has a large overlap with Vulkan. As such, we endeavor to leverage as many of the Vulkan Ecosystem components as possible.
This repository contains the Vulkan SC Validation Layers which is intended for development environments, and is not expected to be used in production (safety) environments.
NOTE: This repository is a downstream fork of KhronosGroup/Vulkan-ValidationLayers which is periodically rebased.
This repository continues to have functioning Vulkan validation layers with equivalent functionality to the upstream branch point.
The choice of Vulkan or Vulkan SC support is determined at build time.
- @KhronosGroup/VVL-CODEOWNERS
- VVL-CODEOWNERS can also be found on aforementioned Slack channel for direct contact.
- BUILD.md - Instructions for building the Validation Layers
- KHRONOS_VALIDATION_LAYER.md - Instructions for configuring the Validation Layers
- CONTRIBUTING.md - Information needed to make a contribution.
- ./docs - Details of the Validation Layer source code. For those wanting to make contributions
- ./tests - Information about testing the Validation Layers.
- GOVERNANCE.md - Repository management details.
The Validation Layers are broken up as many smaller internal "Validation Objects" each tasked with their own job. Core Checks is what is enabled by default, but there are other validation objects that can be additionally enabled, such as Synchronization Validation, GPU Assisted Validation, and more. There are also a few limitations stemming from the Validation layers being a Vulkan layer.
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.
Weekly automated (and untested) tags are generated with the following format: snapshot-<year>wk<week-number>, eg. snapshot-2024wk06.
For Vulkan SC, updates to a new API version will be tagged using the following format vksc<version>.<patch> (e.g., vksc1.0.12).
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.