#vkGetQueryPoolResults returns VK_NOT_READY
8 messages · Page 1 of 1 (latest)
are you using sync2 ?
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
No I’m not
Hmm, would adding the flag VK_QUERY_RESULT_WAIT_BIT to wait on the query pool get be a good solution then?
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