C Specification
The VkPhysicalDeviceLayeredApiPropertiesListKHR structure is defined
as:
// Provided by VK_KHR_maintenance7
typedef struct VkPhysicalDeviceLayeredApiPropertiesListKHR {
VkStructureType sType;
void* pNext;
uint32_t layeredApiCount;
VkPhysicalDeviceLayeredApiPropertiesKHR* pLayeredApis;
} VkPhysicalDeviceLayeredApiPropertiesListKHR;
Members
-
sTypeis a VkStructureType value identifying this structure. -
pNextisNULLor a pointer to a structure extending this structure. -
layeredApiCountis an integer related to the number of layered implementations underneath the Vulkan physical device, as described below. -
pLayeredApisis a pointer to an array of VkPhysicalDeviceLayeredApiPropertiesKHR in which information regarding the layered implementations underneath the Vulkan physical device are returned.
Description
If pLayeredApis is NULL, then the number of layered implementations
that are underneath the top-most Vulkan physical device (i.e. the one
returned by vkGetPhysicalDeviceProperties2) is returned in
layeredApiCount.
Otherwise, layeredApiCount must be set by the application to the
number of elements in the pLayeredApis array, and on return the
variable is overwritten with the number of values actually written to
pLayeredApis.
If the value of layeredApiCount is less than the number of layered
implementations underneath the Vulkan physical device, at most
layeredApiCount values will be written to pLayeredApis.
An implementation that is not a layer will return 0 in
layeredApiCount.
In the presence of multiple layered implementations, each element of
pLayeredApis corresponds to an API implementation that is implemented
on top of the API at the previous index.
If there are layered implementations underneath a non-Vulkan implementation,
they may not be visible in this query as the corresponding APIs may lack
such a query.
If the VkPhysicalDeviceLayeredApiPropertiesListKHR structure is included in the pNext chain of the
VkPhysicalDeviceProperties2 structure passed to
vkGetPhysicalDeviceProperties2, it is filled in with each
corresponding implementation-dependent property.
Document Notes
For more information, see the Vulkan Specification
This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification, not directly.