Clarify vertex input bindings
Maintainers usually reply within 1 day
@SaschaWillems is already working on this.
Since Oct 19, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Start with the 'Binding descriptions' section of the vertex input description chapter in the tutorial, which the issue links and quotes. The issue proposes replacement wording that first defines a vertex input binding as a numbered slot, then covers stride and inputRate, then notes that bindVertexBuffers() comes in the next chapter. Done means the section reads in that order, and a diagram is optional. The payload does not name the source file, so find it from the section heading.
Written by the indexing model from the issue text.
Description
In the Binding descriptions section, the tutorial introduces vertex input bindings with the following explanation:
A vertex binding describes at which rate to load data from memory throughout the vertices. It specifies the number of bytes between data entries and whether to move to the next data entry after each vertex or after each instance.
I found this explanation confusing because it describes the properties of a vertex input binding, particularly stride and inputRate, without first explaining what a vertex input binding actually represents.
My understanding is that a vertex input binding is a numbered input slot that can be associated with a vertex buffer. The binding description specifies how data from that slot should be accessed, while vertex attribute descriptions specify which binding supplies each attribute.
The actual vertex buffer is associated with the slot separately, using bindVertexBuffers(), which is introduced in the next chapter
I think the section would be easier to follow if it first introduced the concept of a vertex input binding before explaining its properties.
For example, the explanation could be revised to:
A vertex input binding is a numbered slot used to supply vertex attribute data. Multiple vertex attributes can reference the same binding.
Each binding has a description that specifies the stride between consecutive data entries and whether the data is accessed per vertex or per instance.
At this point, we're only describing how the data should be accessed. In the next chapter, we'll use
bindVertexBuffers()to associate an actual vertex buffer with this binding.
This would clarify the distinction between a binding itself, its description, and the actual buffer associated with it. Even better, we can use a diagram to illustrate this.
- Dominant language
- C++
- Stars
- 444
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from KhronosGroup/Vulkan-Tutorial
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
KhronosGroup/Vulkan-Tutorial#551 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
KhronosGroup/Vulkan-Tutorial#545 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
KhronosGroup/Vulkan-Tutorial#544 ·
Maintainers usually reply within 1 day
-
Clarify front-face culling when using a negative viewport heightPossibly taken @1sgtpepper claimed this 18 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
KhronosGroup/Vulkan-Tutorial#534 ·
Maintainers usually reply within 1 day
-
Stale GLSL-specific wording in the Vertex Input Description chapterPossibly taken @gpx1000 claimed this 27 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
KhronosGroup/Vulkan-Tutorial#528 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in KhronosGroup/Vulkan-Tutorial
Similar issues
-
Documentation: Fix parameter markup, legacy branch link, and phrasing in Detachable Joints and Model Command tutorialsPossibly taken @patelshivani2283-lab claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Niko1221/Strata#6071 · 2 comments ·
Maintainers usually reply within 4 days
-
pumpOpen
Difficulty 1/5 Under an hour Newbie friendliness 68/100
dewenni/ESP_Buderus_KM271#191 ·