[vk] Fix Vulkan Upload & Present Barriers for Spec Compliance #2681
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Ribbit/ribbitvulkanadditions:speccompliance"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The barrier before the CPU-upload copy was using VK_PIPELINE_STAGE_HOST_BIT. Validation rules only allow HOST as the source stage if you’re also specifying host-side access flags; inside a command buffer the GPU isn’t executing “host work,” so pairing that stage with the usual image layout transition is technically invalid.
Switching the source stage to VK_PIPELINE_STAGE_TOP_OF_PIPE_BIT keeps the ordering guarantee we need and satisfies the spec, while the actual host visibility is still handled correctly by the preceding vmaFlushAllocation.
a9b02e9eb1
to82f8ef2fe8
WIP: [vk] Fix Vulkan Upload & Present Barriers for Spec Complianceto [vk] Fix Vulkan Upload & Present Barriers for Spec Compliance[vk] Fix Vulkan Upload & Present Barriers for Spec Complianceto WIP: [vk] Fix Vulkan Upload & Present Barriers for Spec ComplianceWIP: [vk] Fix Vulkan Upload & Present Barriers for Spec Complianceto [vk] Fix Vulkan Upload & Present Barriers for Spec ComplianceTesters report that there are no issues and this change raises lows creating less stutter and a smoother experience.