-
Notifications
You must be signed in to change notification settings - Fork 194
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
AccelerationStructure and use of vk::Device #377
Comments
MarijnS95
added a commit
to Traverse-Research/ash
that referenced
this issue
Feb 27, 2021
This handle is already held onto when creating the safe wrapper object, but is inconsistently required again in some but not all functions. Remove it from every function and use the internal handle instead. Closes: ash-rs#377 Fixes: 05747b2 ("Update Vulkan-Headers to 1.2.162 with stable ray-tracing spec (ash-rs#341)")
That looks to have been yet another porting artifact when migrating to the stable headers. Same applies to |
MaikKlein
pushed a commit
that referenced
this issue
Feb 28, 2021
#378) This handle is already held onto when creating the safe wrapper object, but is inconsistently required again in some but not all functions. Remove it from every function and use the internal handle instead. Closes: #377 Fixes: 05747b2 ("Update Vulkan-Headers to 1.2.162 with stable ray-tracing spec (#341)")
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AccelerationStructure holds a vk::Device and some functions use it while other require the vk::Device as an argument.
Is there a reason for that ?
The text was updated successfully, but these errors were encountered: