KhronosGroup / KhronosGroup/Vulkan-Docs
`vkCmdSetPrimitiveTopologyEXT` and `vkCmdSetPrimitiveRestartEnableEXT` restrictions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
The documentation of VkPipelineInputAssemblyStateCreateInfo mentions various restrictions on valid usage regarding the topology and primitiveRestartEnable values. However, none of this is mentioned in the documentation of vkCmdSetPrimitiveTopologyEXT and vkCmdSetPrimitiveRestartEnableEXT, even though I assume that they apply to dynamic state as much as they do to fixed state. An error of omission?
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
Compare the valid-usage documentation for VkPipelineInputAssemblyStateCreateInfo with the entries for vkCmdSetPrimitiveTopologyEXT and vkCmdSetPrimitiveRestartEnableEXT. Confirm whether the topology and primitiveRestartEnable restrictions apply to dynamic state, then document the applicable restrictions in both command entries if the omission is confirmed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100