public Class EXTDebugUtils

VkDebugUtilsMessageSeverityFlagBitsEXT - Bitmask specifying which severities of events cause a debug messenger callback

Description

• DEBUG_UTILS_MESSAGE_SEVERITY_VERBOSE_BIT_EXT specifies the most verbose output indicating all diagnostic messages from the Vulkan loader, layers, and drivers should be captured.
• DEBUG_UTILS_MESSAGE_SEVERITY_INFO_BIT_EXT specifies an informational message such as resource details that may be handy when debugging an application.
• DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT specifies use of Vulkan that may expose an app bug. Such cases may not be immediately harmful, such as a fragment shader outputting to a location with no attachment. Other cases may point to behavior that is almost certainly bad when unintended such as using an image whose memory has not been filled. In general if you see a warning but you know that the behavior is intended/desired, then simply ignore the warning.
• DEBUG_UTILS_MESSAGE_SEVERITY_ERROR_BIT_EXT specifies that the application has violated a valid usage condition of the specification.

    if (messageSeverity >= VK_DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT) {
        // Do something for warnings and errors
    }

See Also

SubmitDebugUtilsMessageEXT

VkDebugUtilsMessageSeverityFlagBitsEXT - Bitmask specifying which severities of events cause a debug messenger callback

Description

• DEBUG_UTILS_MESSAGE_SEVERITY_VERBOSE_BIT_EXT specifies the most verbose output indicating all diagnostic messages from the Vulkan loader, layers, and drivers should be captured.
• DEBUG_UTILS_MESSAGE_SEVERITY_INFO_BIT_EXT specifies an informational message such as resource details that may be handy when debugging an application.
• DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT specifies use of Vulkan that may expose an app bug. Such cases may not be immediately harmful, such as a fragment shader outputting to a location with no attachment. Other cases may point to behavior that is almost certainly bad when unintended such as using an image whose memory has not been filled. In general if you see a warning but you know that the behavior is intended/desired, then simply ignore the warning.
• DEBUG_UTILS_MESSAGE_SEVERITY_ERROR_BIT_EXT specifies that the application has violated a valid usage condition of the specification.

    if (messageSeverity >= VK_DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT) {
        // Do something for warnings and errors
    }

See Also

SubmitDebugUtilsMessageEXT

VkDebugUtilsMessageSeverityFlagBitsEXT - Bitmask specifying which severities of events cause a debug messenger callback

Description

• DEBUG_UTILS_MESSAGE_SEVERITY_VERBOSE_BIT_EXT specifies the most verbose output indicating all diagnostic messages from the Vulkan loader, layers, and drivers should be captured.
• DEBUG_UTILS_MESSAGE_SEVERITY_INFO_BIT_EXT specifies an informational message such as resource details that may be handy when debugging an application.
• DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT specifies use of Vulkan that may expose an app bug. Such cases may not be immediately harmful, such as a fragment shader outputting to a location with no attachment. Other cases may point to behavior that is almost certainly bad when unintended such as using an image whose memory has not been filled. In general if you see a warning but you know that the behavior is intended/desired, then simply ignore the warning.
• DEBUG_UTILS_MESSAGE_SEVERITY_ERROR_BIT_EXT specifies that the application has violated a valid usage condition of the specification.

    if (messageSeverity >= VK_DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT) {
        // Do something for warnings and errors
    }

See Also

SubmitDebugUtilsMessageEXT

VkDebugUtilsMessageSeverityFlagBitsEXT - Bitmask specifying which severities of events cause a debug messenger callback

Description

• DEBUG_UTILS_MESSAGE_SEVERITY_VERBOSE_BIT_EXT specifies the most verbose output indicating all diagnostic messages from the Vulkan loader, layers, and drivers should be captured.
• DEBUG_UTILS_MESSAGE_SEVERITY_INFO_BIT_EXT specifies an informational message such as resource details that may be handy when debugging an application.
• DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT specifies use of Vulkan that may expose an app bug. Such cases may not be immediately harmful, such as a fragment shader outputting to a location with no attachment. Other cases may point to behavior that is almost certainly bad when unintended such as using an image whose memory has not been filled. In general if you see a warning but you know that the behavior is intended/desired, then simply ignore the warning.
• DEBUG_UTILS_MESSAGE_SEVERITY_ERROR_BIT_EXT specifies that the application has violated a valid usage condition of the specification.

    if (messageSeverity >= VK_DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT) {
        // Do something for warnings and errors
    }

See Also

SubmitDebugUtilsMessageEXT

VkDebugUtilsMessageTypeFlagBitsEXT - Bitmask specifying which types of events cause a debug messenger callback

Description

• DEBUG_UTILS_MESSAGE_TYPE_GENERAL_BIT_EXT specifies that some general event has occurred. This is typically a non-specification, non-performance event.
• DEBUG_UTILS_MESSAGE_TYPE_VALIDATION_BIT_EXT specifies that something has occurred during validation against the Vulkan specification that may indicate invalid behavior.
• DEBUG_UTILS_MESSAGE_TYPE_PERFORMANCE_BIT_EXT specifies a potentially non-optimal use of Vulkan, e.g. using CmdClearColorImage when setting VkAttachmentDescription::loadOp to ATTACHMENT_LOAD_OP_CLEAR would have worked.
• DEBUG_UTILS_MESSAGE_TYPE_DEVICE_ADDRESS_BINDING_BIT_EXT specifies that the implementation has modified the set of GPU-visible virtual addresses associated with a Vulkan object.

VkDebugUtilsMessageTypeFlagBitsEXT - Bitmask specifying which types of events cause a debug messenger callback

Description

• DEBUG_UTILS_MESSAGE_TYPE_GENERAL_BIT_EXT specifies that some general event has occurred. This is typically a non-specification, non-performance event.
• DEBUG_UTILS_MESSAGE_TYPE_VALIDATION_BIT_EXT specifies that something has occurred during validation against the Vulkan specification that may indicate invalid behavior.
• DEBUG_UTILS_MESSAGE_TYPE_PERFORMANCE_BIT_EXT specifies a potentially non-optimal use of Vulkan, e.g. using CmdClearColorImage when setting VkAttachmentDescription::loadOp to ATTACHMENT_LOAD_OP_CLEAR would have worked.
• DEBUG_UTILS_MESSAGE_TYPE_DEVICE_ADDRESS_BINDING_BIT_EXT specifies that the implementation has modified the set of GPU-visible virtual addresses associated with a Vulkan object.

VkDebugUtilsMessageTypeFlagBitsEXT - Bitmask specifying which types of events cause a debug messenger callback

Description

• DEBUG_UTILS_MESSAGE_TYPE_GENERAL_BIT_EXT specifies that some general event has occurred. This is typically a non-specification, non-performance event.
• DEBUG_UTILS_MESSAGE_TYPE_VALIDATION_BIT_EXT specifies that something has occurred during validation against the Vulkan specification that may indicate invalid behavior.
• DEBUG_UTILS_MESSAGE_TYPE_PERFORMANCE_BIT_EXT specifies a potentially non-optimal use of Vulkan, e.g. using CmdClearColorImage when setting VkAttachmentDescription::loadOp to ATTACHMENT_LOAD_OP_CLEAR would have worked.
• DEBUG_UTILS_MESSAGE_TYPE_DEVICE_ADDRESS_BINDING_BIT_EXT specifies that the implementation has modified the set of GPU-visible virtual addresses associated with a Vulkan object.

The extension name.

The extension specification version.

Extends VkObjectType.

Extends VkStructureType.

Enum values:

• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_NAME_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_TAG_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_LABEL_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CALLBACK_DATA_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT

Extends VkStructureType.

Enum values:

• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_NAME_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_TAG_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_LABEL_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CALLBACK_DATA_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT

Extends VkStructureType.

Enum values:

• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_NAME_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_TAG_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_LABEL_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CALLBACK_DATA_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT

Extends VkStructureType.

Enum values:

• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_NAME_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_TAG_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_LABEL_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CALLBACK_DATA_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT

Extends VkStructureType.

Enum values:

• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_NAME_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_TAG_INFO_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_LABEL_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CALLBACK_DATA_EXT
• STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT

Unsafe version of: CmdBeginDebugUtilsLabelEXT

Unsafe version of: CmdInsertDebugUtilsLabelEXT

Unsafe version of: CreateDebugUtilsMessengerEXT

Unsafe version of: DestroyDebugUtilsMessengerEXT

Unsafe version of: QueueBeginDebugUtilsLabelEXT

Unsafe version of: QueueInsertDebugUtilsLabelEXT

Unsafe version of: SetDebugUtilsObjectNameEXT

Unsafe version of: SetDebugUtilsObjectTagEXT

Unsafe version of: SubmitDebugUtilsMessageEXT

Open a command buffer debug label region.

C Specification

A command buffer debug label region can be opened by calling:

void vkCmdBeginDebugUtilsLabelEXT(
    VkCommandBuffer                             commandBuffer,
    const VkDebugUtilsLabelEXT*                 pLabelInfo);

Valid Usage (Implicit)

• commandBuffer must be a valid VkCommandBuffer handle
• pLabelInfo must be a valid pointer to a valid VkDebugUtilsLabelEXT structure
• commandBuffer must be in the recording state
• The VkCommandPool that commandBuffer was allocated from must support graphics, or compute operations
• This command must only be called outside of a video coding scope

Host Synchronization

• Host access to commandBuffer must be externally synchronized
• Host access to the VkCommandPool that commandBuffer was allocated from must be externally synchronized

Command Properties

See Also

VkDebugUtilsLabelEXT

Parameters

commandBuffer:VkCommandBuffer

the command buffer into which the command is recorded.

pLabelInfo:VkDebugUtilsLabelEXT

a pointer to a VkDebugUtilsLabelEXT structure specifying parameters of the label region to open.

Close a command buffer label region.

C Specification

A command buffer label region can be closed by calling:

void vkCmdEndDebugUtilsLabelEXT(
    VkCommandBuffer                             commandBuffer);

Description

An application may open a debug label region in one command buffer and close it in another, or otherwise split debug label regions across multiple command buffers or multiple queue submissions. When viewed from the linear series of submissions to a single queue, the calls to CmdBeginDebugUtilsLabelEXT and CmdEndDebugUtilsLabelEXT must be matched and balanced.

There can be problems reporting command buffer debug labels during the recording process because command buffers may be recorded out of sequence with the resulting execution order. Since the recording order may be different, a solitary command buffer may have an inconsistent view of the debug label regions by itself. Therefore, if an issue occurs during the recording of a command buffer, and the environment requires returning debug labels, the implementation may return only those labels it is aware of. This is true even if the implementation is aware of only the debug labels within the command buffer being actively recorded.

Valid Usage

• There must be an outstanding vkCmdBeginDebugUtilsLabelEXT command prior to the vkCmdEndDebugUtilsLabelEXT on the queue that commandBuffer is submitted to
• If commandBuffer is a secondary command buffer, there must be an outstanding vkCmdBeginDebugUtilsLabelEXT command recorded to commandBuffer that has not previously been ended by a call to vkCmdEndDebugUtilsLabelEXT

Valid Usage (Implicit)

• commandBuffer must be a valid VkCommandBuffer handle
• commandBuffer must be in the recording state
• The VkCommandPool that commandBuffer was allocated from must support graphics, or compute operations
• This command must only be called outside of a video coding scope

Host Synchronization

• Host access to commandBuffer must be externally synchronized
• Host access to the VkCommandPool that commandBuffer was allocated from must be externally synchronized

Command Properties

Parameters

commandBuffer:VkCommandBuffer

the command buffer into which the command is recorded.

Insert a label into a command buffer.

C Specification

A single debug label can be inserted into a command buffer by calling:

void vkCmdInsertDebugUtilsLabelEXT(
    VkCommandBuffer                             commandBuffer,
    const VkDebugUtilsLabelEXT*                 pLabelInfo);

Valid Usage (Implicit)

• commandBuffer must be a valid VkCommandBuffer handle
• pLabelInfo must be a valid pointer to a valid VkDebugUtilsLabelEXT structure
• commandBuffer must be in the recording state
• The VkCommandPool that commandBuffer was allocated from must support graphics, or compute operations
• This command must only be called outside of a video coding scope

Host Synchronization

• Host access to commandBuffer must be externally synchronized
• Host access to the VkCommandPool that commandBuffer was allocated from must be externally synchronized

Command Properties

See Also

VkDebugUtilsLabelEXT

Parameters

commandBuffer:VkCommandBuffer

the command buffer into which the command is recorded.

Create a debug messenger object.

C Specification

A debug messenger triggers a debug callback with a debug message when an event of interest occurs. To create a debug messenger which will trigger a debug callback, call:

VkResult vkCreateDebugUtilsMessengerEXT(
    VkInstance                                  instance,
    const VkDebugUtilsMessengerCreateInfoEXT*   pCreateInfo,
    const VkAllocationCallbacks*                pAllocator,
    VkDebugUtilsMessengerEXT*                   pMessenger);

Valid Usage (Implicit)

• instance must be a valid VkInstance handle
• pCreateInfo must be a valid pointer to a valid VkDebugUtilsMessengerCreateInfoEXT structure
• If pAllocator is not NULL, pAllocator must be a valid pointer to a valid VkAllocationCallbacks structure
• pMessenger must be a valid pointer to a VkDebugUtilsMessengerEXT handle

Return Codes

On success, this command returns

• SUCCESS

On failure, this command returns

• ERROR_OUT_OF_HOST_MEMORY

The application must ensure that CreateDebugUtilsMessengerEXT is not executed in parallel with any Vulkan command that is also called with instance or child of instance as the dispatchable argument.

See Also

VkAllocationCallbacks, VkDebugUtilsMessengerCreateInfoEXT

Parameters

instance:VkInstance

the instance the messenger will be used with.

pCreateInfo:VkDebugUtilsMessengerCreateInfoEXT

a pointer to a VkDebugUtilsMessengerCreateInfoEXT structure containing the callback pointer, as well as defining conditions under which this messenger will trigger the callback.

pAllocator:VkAllocationCallbacks

controls host memory allocation as described in the Memory Allocation chapter.

pMessenger:LongBuffer

a pointer to a VkDebugUtilsMessengerEXT handle in which the created object is returned.

Annotations

@NativeType:VkResult

Array version of: CreateDebugUtilsMessengerEXT

Annotations

@NativeType:VkResult

Destroy a debug messenger object.

C Specification

To destroy a VkDebugUtilsMessengerEXT object, call:

void vkDestroyDebugUtilsMessengerEXT(
    VkInstance                                  instance,
    VkDebugUtilsMessengerEXT                    messenger,
    const VkAllocationCallbacks*                pAllocator);

Valid Usage

• If VkAllocationCallbacks were provided when messenger was created, a compatible set of callbacks must be provided here
• If no VkAllocationCallbacks were provided when messenger was created, pAllocator must be NULL

Valid Usage (Implicit)

• instance must be a valid VkInstance handle
• If messenger is not NULL_HANDLE, messenger must be a valid VkDebugUtilsMessengerEXT handle
• If pAllocator is not NULL, pAllocator must be a valid pointer to a valid VkAllocationCallbacks structure
• If messenger is a valid handle, it must have been created, allocated, or retrieved from instance

Host Synchronization

• Host access to messenger must be externally synchronized

The application must ensure that DestroyDebugUtilsMessengerEXT is not executed in parallel with any Vulkan command that is also called with instance or child of instance as the dispatchable argument.

See Also

VkAllocationCallbacks

Parameters

instance:VkInstance

the instance where the callback was created.

messenger:long

the VkDebugUtilsMessengerEXT object to destroy. messenger is an externally synchronized object and must not be used on more than one thread at a time. This means that vkDestroyDebugUtilsMessengerEXT must not be called when a callback is active.

pAllocator:VkAllocationCallbacks

controls host memory allocation as described in the Memory Allocation chapter.

Open a queue debug label region.

C Specification

A queue debug label region is opened by calling:

void vkQueueBeginDebugUtilsLabelEXT(
    VkQueue                                     queue,
    const VkDebugUtilsLabelEXT*                 pLabelInfo);

Valid Usage (Implicit)

• queue must be a valid VkQueue handle
• pLabelInfo must be a valid pointer to a valid VkDebugUtilsLabelEXT structure

Command Properties

See Also

VkDebugUtilsLabelEXT

Parameters

queue:VkQueue

the queue in which to start a debug label region.

pLabelInfo:VkDebugUtilsLabelEXT

a pointer to a VkDebugUtilsLabelEXT structure specifying parameters of the label region to open.

Close a queue debug label region.

C Specification

A queue debug label region is closed by calling:

void vkQueueEndDebugUtilsLabelEXT(
    VkQueue                                     queue);

Description

The calls to QueueBeginDebugUtilsLabelEXT and QueueEndDebugUtilsLabelEXT must be matched and balanced.

Valid Usage

• There must be an outstanding vkQueueBeginDebugUtilsLabelEXT command prior to the vkQueueEndDebugUtilsLabelEXT on the queue

Valid Usage (Implicit)

• queue must be a valid VkQueue handle

Command Properties

Parameters

queue:VkQueue

the queue in which a debug label region should be closed.

Insert a label into a queue.

C Specification

A single label can be inserted into a queue by calling:

void vkQueueInsertDebugUtilsLabelEXT(
    VkQueue                                     queue,
    const VkDebugUtilsLabelEXT*                 pLabelInfo);

Valid Usage (Implicit)

• queue must be a valid VkQueue handle
• pLabelInfo must be a valid pointer to a valid VkDebugUtilsLabelEXT structure

Command Properties

See Also

VkDebugUtilsLabelEXT

Parameters

queue:VkQueue

the queue into which a debug label will be inserted.

pLabelInfo:VkDebugUtilsLabelEXT

a pointer to a VkDebugUtilsLabelEXT structure specifying parameters of the label to insert.

Give a user-friendly name to an object.

C Specification

VkResult vkSetDebugUtilsObjectNameEXT(
    VkDevice                                    device,
    const VkDebugUtilsObjectNameInfoEXT*        pNameInfo);

Valid Usage

• pNameInfo→objectType must not be OBJECT_TYPE_UNKNOWN
• pNameInfo→objectHandle must not be NULL_HANDLE
• If pNameInfo→objectHandle is the valid handle of an instance-level object, the VkDevice identified by device must be a descendent of the same VkInstance as the object identified by pNameInfo→objectHandle
• If pNameInfo→objectHandle is the valid handle of a physical-device-level object, the VkDevice identified by device must be a descendant of the same VkPhysicalDevice as the object identified by pNameInfo→objectHandle
• If pNameInfo→objectHandle is the valid handle of a device-level object, that object must be a descendent of the VkDevice identified by device

Valid Usage (Implicit)

• device must be a valid VkDevice handle
• pNameInfo must be a valid pointer to a valid VkDebugUtilsObjectNameInfoEXT structure

Host Synchronization

• Host access to pNameInfo→objectHandle must be externally synchronized

Return Codes

On success, this command returns

• SUCCESS

On failure, this command returns

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

VkDebugUtilsObjectNameInfoEXT

Parameters

device:VkDevice

the device that is associated with the named object passed in via objectHandle.

pNameInfo:VkDebugUtilsObjectNameInfoEXT

a pointer to a VkDebugUtilsObjectNameInfoEXT structure specifying parameters of the name to set on the object.

Annotations

@NativeType:VkResult

Attach arbitrary data to an object.

C Specification

VkResult vkSetDebugUtilsObjectTagEXT(
    VkDevice                                    device,
    const VkDebugUtilsObjectTagInfoEXT*         pTagInfo);

Valid Usage

• If pNameInfo→objectHandle is the valid handle of an instance-level object, the VkDevice identified by device must be a descendent of the same VkInstance as the object identified by pNameInfo→objectHandle
• If pNameInfo→objectHandle is the valid handle of a physical-device-level object, the VkDevice identified by device must be a descendant of the same VkPhysicalDevice as the object identified by pNameInfo→objectHandle
• If pNameInfo→objectHandle is the valid handle of a device-level object, that object must be a descendent of the VkDevice identified by device

Valid Usage (Implicit)

• device must be a valid VkDevice handle
• pTagInfo must be a valid pointer to a valid VkDebugUtilsObjectTagInfoEXT structure

Host Synchronization

• Host access to pTagInfo→objectHandle must be externally synchronized

Return Codes

On success, this command returns

• SUCCESS

On failure, this command returns

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

VkDebugUtilsObjectTagInfoEXT

Parameters

device:VkDevice

the device that created the object.

pTagInfo:VkDebugUtilsObjectTagInfoEXT

a pointer to a VkDebugUtilsObjectTagInfoEXT structure specifying parameters of the tag to attach to the object.

Annotations

@NativeType:VkResult

Inject a message into a debug stream.

C Specification

There may be times that a user wishes to intentionally submit a debug message. To do this, call:

void vkSubmitDebugUtilsMessageEXT(
    VkInstance                                  instance,
    VkDebugUtilsMessageSeverityFlagBitsEXT      messageSeverity,
    VkDebugUtilsMessageTypeFlagsEXT             messageTypes,
    const VkDebugUtilsMessengerCallbackDataEXT* pCallbackData);

Description

The call will propagate through the layers and generate callback(s) as indicated by the message’s flags. The parameters are passed on to the callback in addition to the pUserData value that was defined at the time the messenger was registered.

Valid Usage

• The objectType member of each element of pCallbackData→pObjects must not be OBJECT_TYPE_UNKNOWN

Valid Usage (Implicit)

• instance must be a valid VkInstance handle
• messageSeverity must be a valid VkDebugUtilsMessageSeverityFlagBitsEXT value
• messageTypes must be a valid combination of VkDebugUtilsMessageTypeFlagBitsEXT values
• messageTypes must not be 0
• pCallbackData must be a valid pointer to a valid VkDebugUtilsMessengerCallbackDataEXT structure

See Also

VkDebugUtilsMessengerCallbackDataEXT

Parameters

instance:VkInstance

the debug stream’s VkInstance.

messageSeverity:int

a VkDebugUtilsMessageSeverityFlagBitsEXT value specifying the severity of this event/message.

messageTypes:int

a bitmask of VkDebugUtilsMessageTypeFlagBitsEXT specifying which type of event(s) to identify with this message.

pCallbackData:VkDebugUtilsMessengerCallbackDataEXT

contains all the callback related data in the VkDebugUtilsMessengerCallbackDataEXT structure.