KhronosGroup / KhronosGroup/Vulkan-Portability
Documenting unsupported "required features" in the spec
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 45
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Some portability implementations cannot support enabling all feature flags that are required for full Vulkan conformance (see Feature Requirements section of spec).
This is a list of features that we might potentially document as not required for portability subset implementations, in the Feature Requirements section of the spec (similar to how we documented robustBufferAccess).
(this list is to be edited)
VkPhysicalDeviceDescriptorIndexingFeatures:
-
runtimeDescriptorArrayif the implementation cannot support unsized arrays of resources in shaders -
shaderUniformBufferArrayNonUniformIndexingif the implementation cannot support arrays of buffers in shaders (Metal) -
shaderStorageBufferArrayNonUniformIndexingif the implementation cannot support arrays of buffers in shaders (Metal)
Contributor guide
No contributing guide indexed for this repository
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 with the spec's Feature Requirements section and compare its existing treatment of robustBufferAccess with the listed VkPhysicalDeviceDescriptorIndexingFeatures. Determine which listed features should be documented as non-required for portability subset implementations, then update that section so the final exceptions and their conditions are explicit.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100