Skip to content

Conversation

@spencer-lunarg
Copy link
Contributor

follow on for #11509 I have for the new extension as well

Adds a Buffer::Describe() to unify how we print out buffers

@spencer-lunarg spencer-lunarg requested a review from a team as a code owner January 21, 2026 20:03
@ci-tester-lunarg
Copy link
Collaborator

CI Vulkan-ValidationLayers build queued with queue ID 628985.

}
}

skip |= LogError("VUID-VkDescriptorGetInfoEXT-type-08028", device, descriptor_info_loc.dot(Field::type), "%s", ss.str().c_str());
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vkGetDescriptorEXT(): pDescriptorInfo->type is VK_DESCRIPTOR_TYPE_ACCELERATION_STRUCTURE_KHR, but accelerationStructure (0x%10000c00) is not an address obtained from a currently existing VkAccelerationStructureKHR.
The follow buffers were found at this address:
  VkBuffer 0x110000000011, size 4, range [0x10000c00, 0x10000c04) (This buffer is backing an AccelerationStructure, but is not the address to the VkAccelerationStructure handle)

new error message... will be helpful when people mix up which VkDeviceAddress to hand

@ci-tester-lunarg
Copy link
Collaborator

CI Vulkan-ValidationLayers build # 22239 running.

@ci-tester-lunarg
Copy link
Collaborator

CI Vulkan-ValidationLayers build # 22239 passed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants