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
I'm writing an application that need access to external semaphore functionalities provided by these extensions VK_KHR_external_fence and VK_KHR_external_semaphore. These extensions are supported when querying the list of supported extensions, but when I query to get the properties of the semaphore using VK_KHR_external_fence_capabilities and VK_KHR_external_semaphore_capabilities, the handle types and semaphore features are all 0:
Based on my reading of the standard, it is legal for a Vulkan implementation to implement VK_KHR_external_semaphore without supporting any external handle types. Typically, supporting a handle type requires also supporting one of the handle-type extensions (e.g. VK_KHR_external_semaphore_fd).
Metal does support this functionality, but first we need to define extensions providing extension structures so you can, you know, actually import and export these objects, because none of the existing ones is adequate for Metal.
Hi,
I'm writing an application that need access to external semaphore functionalities provided by these extensions
VK_KHR_external_fence
andVK_KHR_external_semaphore
. These extensions are supported when querying the list of supported extensions, but when I query to get the properties of the semaphore usingVK_KHR_external_fence_capabilities
andVK_KHR_external_semaphore_capabilities
, the handle types and semaphore features are all 0:MoltenVK/MoltenVK/MoltenVK/GPUObjects/MVKDevice.mm
Line 1323 in e6b7806
Is this not implemented correctly in MoltenVK? Pardon my language if I made any mistake, I'm new to Vulkan & MoltenVK :).
The text was updated successfully, but these errors were encountered: