Open AlexanderVeselov-arm opened 1 month ago
So we have zero tests for VK_EXT_opacity_micromap
currently and unfortunately has fallen back on our priority list. I am happy to at least not have things crash, but also not familiar with this extension and the what we really need is a "positive" test that uses the API correctly to make sure we aren't crashing on basic usage
Unfortunately on our side OMM is not a main focus today, just experimenting around with desktop gpu.
"positive" test that uses the API correctly to make sure we aren't crashing on basic usage
I'll put it in a backlog for now, to get back to it, once we have time.
Environment:
(Omitting rest of the stuff, as it is bug in C++ code and must be platform independent)
Describe the Issue
Hello!
Apparently validation layer has an unwrapping related bug in handling
.pNext
, that points toVkAccelerationStructureTrianglesOpacityMicromapEXT
.For example, when calling
vkGetAccelerationStructureBuildSizesKHR
with OMM, validation layer takes const-pointer toVkAccelerationStructureBuildGeometryInfoKHR
, with information about micromap available via pointer chain:The reason for is lack of deep-copy mechanism for
VkAccelerationStructureGeometryDataKHR
, followed by unwrapping of OMM handle.