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
However, this is an improper assumption. For instance, if vkWaitForFences times out, VK_TIMEOUT(2) is returned. Similarly, vkGetFenceStatus will return a VK_NOT_READY(1) if the fence is still being used in a queue submission. This means that I am unable to actually use fence synchronization properly through the high level wrapper.
This check should be changed to be more robust and not report Ok when these cases are hit. I'm uncertain, however, if these responses should be considered errors or not. My guess is they probably should be for ease of use of the API, but technically they aren't really errors.
The text was updated successfully, but these errors were encountered:
The current error check code returns
Ok
as long as the return code from vulkan is greater than or equal to 0. https://github.com/cogciprocate/voodoo/blob/master/src/error.rs#L206.However, this is an improper assumption. For instance, if
vkWaitForFences
times out,VK_TIMEOUT(2)
is returned. Similarly,vkGetFenceStatus
will return aVK_NOT_READY(1)
if the fence is still being used in a queue submission. This means that I am unable to actually use fence synchronization properly through the high level wrapper.This check should be changed to be more robust and not report
Ok
when these cases are hit. I'm uncertain, however, if these responses should be considered errors or not. My guess is they probably should be for ease of use of the API, but technically they aren't really errors.The text was updated successfully, but these errors were encountered: