KhronosGroup / KhronosGroup/Vulkan-Docs

Mention that TRANSFER capability must be advertised on COMPUTE or GRAPHICS queues in 1.4

Open
#2,705 0 comments 0 reactions 1 assignee Claimed by @oddhack View on GitHub
Dominant language
JavaScript
Stars
3.3k
Forks
549
Avg merge
5d 5h
Merged PRs (30d)
2

Description

In the Vulkan 1.4 Core Revisions, a new requirement states:
> All queues supporting VK_QUEUE_GRAPHICS_BIT or VK_QUEUE_COMPUTE_BIT **must** also advertise VK_QUEUE_TRANSFER_BIT

However, a note in `chapters/devsandqueues.adoc` still states:
> All commands that are allowed on a queue that supports transfer operations are also allowed on a queue that supports either graphics or compute operations. Thus, if the capabilities of a queue family include VK_QUEUE_GRAPHICS_BIT or VK_QUEUE_COMPUTE_BIT, then reporting the VK_QUEUE_TRANSFER_BIT capability separately for that queue family is **optional**.

This note should be updated to reflect that reporting is optional in Vulkan 1.0 -> 1.3, but mandatory for implementations targeting Vulkan 1.4 or higher. Leaving it as-is is potentially misleading for developers.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.