'What is the first synchronization scope of vkCmdWaitEvents?

In 7.5, the Vulkan spec says about vkCmdWaitEvents

The first synchronization scope only includes event signal operations that operate on members of pEvents, and the operations that happened-before the event signal operations. Event signal operations performed by vkCmdSetEvent that occur earlier in submission order are included in the first synchronization scope, if the logically latest pipeline stage in their stageMask parameter is logically earlier than or equal to the logically latest pipeline stage in srcStageMask.

I'm confused by this phrasing. Does this mean the first synchronization scope is the signalling of events that are passed in to pEvents, plus any events that are submitted earlier and meet the stage mask and submission order requirement, or is it event signals are both passed in and meet the requirement?

In either case, since you can just pass in events with pEvents, what is srcStageMask is useful for?

vulkan


Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source

Related Questions

In Vulkan, is it beneficial for the graphics queue family to be separate from the present queue family?

Why is a single depth buffer sufficient for this vulkan swapchain render loop?

vkQueuePresentKHR image has invalid layout if no command buffers are submitted

Vulkan: Errors when adding 3rd descriptor

Xamarin Android: Calling Invalidate() inside overridden OnDraw method

How to render Vulkan's scene to ImGui window

Vulkan right handed coordinate system become Left handed

Refreshing a Variable multiple times a frame(for a texture array in a shader)

Validation warning about SPIR-V Capability

using vkEnumerateInstanceVersion to get exact Vulkan API version

Handle multiply cameras in Vulkan

Aliasing a SSBO by binding it multiple times in the same shader

Is there any reason to use descriptor instead of device buffer address?