You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently get_query_pool_results assumes a stride of mem::size_of::<T>() as _, however, when using vk::QueryResultFlags::WITH_AVAILABILITY the stride should I think be double that to account for the availability bit.
The text was updated successfully, but these errors were encountered:
This also holds for the VK_QUERY_RESULT_WITH_STATUS_BIT_KHR flag.
See note from the specification:
Note: If VK_QUERY_RESULT_WITH_AVAILABILITY_BIT or VK_QUERY_RESULT_WITH_STATUS_BIT_KHR is set, the layout of data in the buffer is a (result,availability) or (result,status) pair for each query returned, and stride is the stride between each pair.
@YouSafe we've covered this in #100 (comment), #639 (comment) and #644: use a tuple (or likewise repr(C) type) to receive the boolean. The advantage is that the T type immediately incorporates the status or availability bit (how else would you receive that with this function, otherwise?).
Currently
get_query_pool_results
assumes a stride ofmem::size_of::<T>() as _
, however, when usingvk::QueryResultFlags::WITH_AVAILABILITY
the stride should I think be double that to account for the availability bit.The text was updated successfully, but these errors were encountered: