KhronosGroup / KhronosGroup/Vulkan-ValidationLayers

Move RT validation to GPU-AV

Open
#12,635 1 comment 0 reactions 1 assignee View on GitHub

@arno-lunarg is already working on this.

Since Jul 7, 2026.

GPU-AV RT
Dominant language
C++
Stars
1k
Forks
505
Avg merge
11h 25m
Merged PRs (30d)
229

Description

I got some RT validation wrong, some VUs need to be moved to GPU-AV (anything needing last build info):

VUID-vkCmdBuildAccelerationStructuresKHR-primitiveCount-03769
VUID-VkAccelerationStructureTrianglesOpacityMicromapKHR-geometry-11576
vl::BuildASError::IsBuilt_03667
vvl::BuildASError::SameFlags_03759
vvl::BuildASError::SameType_03760
vvl::BuildASError::SameCount_03758
vl::BuildASError::SameType_03761
vvl::BuildASError::SameFlags_03762
vl::BuildASError::TriangleVertexFormat_03763
vvl::BuildASError::TriangleMaxVertex_03764
vl::BuildASError::TriangleIndexType_03765
vvl::BuildASError::TriangleTransformData_03766
vvl::BuildASError::TriangleTransformData_03767
VUID-vkCmdBuildAccelerationStructuresKHR-primitiveCount-03769
VUID-VkAccelerationStructureInstanceKHR-flags-11581
VUID-vkWriteAccelerationStructuresPropertiesKHR-accelerationStructures-03431
VUID-VkCopyAccelerationStructureInfoKHR-src-03411

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.