commit | d5d423254de16ae4ec923b5fbd1622b36edb26d5 | [log] [tgz] |
---|---|---|
author | John Zulauf <jzulauf@lunarg.com> | Fri Jan 27 06:41:27 2023 -0700 |
committer | Juan Ramos <juan@lunarg.com> | Fri Jan 27 11:17:01 2023 -0700 |
tree | c9959507f83eb8fd58a80e0fc408375a638092c6 | |
parent | efc0e5693abfef9ac7eff397240a194a3cd3b82b [diff] |
syncval Revert "Apply render pass final transitions always" The change as written causes CTS crashes, as it doesn't make changes to the consumers of the altered data structures. This reverts commit 41709ca1e50273aa7452fdb04f0c03cde0e53a01.
This project provides the Khronos official Vulkan validation layers for Windows, Linux, Android, and MacOS.
See https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/5084 for details.
Build Status |
---|
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.
This repository contains both the Validation Layers source as well as Tests for them.
Updates to the Vulkan-ValidationLayers
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.