#vkGetQueryPoolResults returns VK_NOT_READY

8 messages · Page 1 of 1 (latest)

high thistle
#

Hi, I am using a query pool to get the compacted size of a BLAS. The fence for the command buffer has status VK_SUCCESS but very rarely (around 1 in 1000 meshes) calling vkGetQueryPoolResults returns VK_NOT_READY. Do I need to wait on the query pool result as well or does this mean my fence sync code must be incorrect?

sweet bane
#

because under sync2 the fence and semaphore signal from a given stage

#

btw think I asked this question some time ago, whether a barrier is needed between a query and the thing (stage) its querying, IIRC I got told no

high thistle
high thistle
#

I can’t find anywhere on the docs which specifies whether the query state is guaranteed to be set to available immediately after the command is completed