KhronosGroup / KhronosGroup/Vulkan-Docs
[question] Vague surface support vkCreateSwapchainKHR VU
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
VkSwapchainCreateInfoKHR VU says:
surfacemust be a surface that is supported by the device as determined usingvkGetPhysicalDeviceSurfaceSupportKHR
For the purposes of validation layers (KhronosGroup/Vulkan-LoaderAndValidationLayers#1727
) I wondered what is the exact interpretation of this.
Considering vkGetPhysicalDeviceSurfaceSupportKHR takes only a VkPhysicalDevice, queue family and a VkSurface, is my interpretation correct? My interpretation:
surfacemust be supported in at least one queue family of thedevice. Where "queue families of adevice" is such a subset ofdevice'sVkPhysicalDevicequeue families that was supplied atvkCreateDevicetime asVkDeviceQueueCreateInfo::queueFamilyIndex
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the VkSwapchainCreateInfoKHR VU and vkGetPhysicalDeviceSurfaceSupportKHR wording cited in the issue, along with the linked validation-layer discussion. Done means the interpretation is resolved and the relevant Vulkan specification text is clarified.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100