Host usage of the VkCommandPool that commandBuffer was allotted from needs to be externally synchronized
Just about every pNext member of any composition (such as this one particular) from the pNext chain has to be both NULL or simply a pointer to a sound occasion of VkRenderPassFragmentDensityMapCreateInfoEXT, VkRenderPassInputAttachmentAspectCreateInfo, or VkRenderPassMultiviewCreateInfo
Host access to the VkCommandPool that commandBuffer was allotted from has to be externally synchronized
If releaseCount is not 0, pReleaseKeys needs to be a valid pointer to an variety of releaseCount uint64_t values
with a fragment shader that both allows sample shading or decorates any variable inside the Enter storage
If deviceIndexCount isn't 0, pDeviceIndices must be a sound pointer to an array of deviceIndexCount uint32_t values
If pAllocator isn't NULL, pAllocator must be a valid pointer to a legitimate VkAllocationCallbacks framework
Host access to the VkCommandPool that commandBuffer was allocated from needs to be externally synchronized
If postSubpassSampleLocationsCount is just not 0, pPostSubpassSampleLocations has to be a legitimate pointer to an variety of postSubpassSampleLocationsCount valid VkSubpassSampleLocationsEXT constructions
If signalSemaphoreInfoCount is not really 0, pSignalSemaphoreInfos must be a browse around this site sound pointer to an variety of signalSemaphoreInfoCount valid VkSemaphoreSubmitInfo buildings
If pAllocator just isn't NULL, pAllocator needs to be a sound pointer to a legitimate VkAllocationCallbacks construction
The two of imageView, and sampler which might be valid handles of non-overlooked parameters should happen to be made, allocated, or retrieved from your very same VkDevice
If groupCount will not be 0, pGroups have to be a valid pointer to an assortment of groupCount valid VkRayTracingShaderGroupCreateInfoKHR structures
The VkCommandPool that commandBuffer was allocated from have to support transfer, graphics, or compute functions