-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explicit 'count' field in AccelerationStructureBuildGeometryInfoKHR #239
Comments
This is a deficiency in the bindings. The cause is: Lengths are elided if they can be uniquely determined by the lengths of This means that (according to just the XML spec) one could pass a length and NULL for both vectors. The XML spec lacks the language to say that only one of these arrays can be NULL. Usually there's a 1-1 mapping between arrays and The easiest solution would be to assign it vulkan/generate-new/src/Bespoke.hs Lines 612 to 618 in 8ba913e
For now it's safe to set it to zero and it'll be inferred: vulkan/src/Vulkan/Extensions/VK_KHR_acceleration_structure.hs Lines 5386 to 5387 in 8ba913e
|
This obviously isn't causing me any trouble at all so you don't need to worry about it. |
Fixed with #251 |
I'm wondering why
AccelerationStructureBuildGeometryInfoKHR
has an explicitgeometryCount
field, as this is just supposed to be the size of thegeometries
vector. In other places in this library, this field is usually elided.I assume that this ended up being a special case, because the original Vulkan function can work with either a pointer to an array of geometries or a pointer to an array of pointers to geometries?
The text was updated successfully, but these errors were encountered: