Stale GLSL-specific wording in the Vertex Input Description chapter

Open Beginner friendly
#528 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@gpx1000 is already working on this.

Since Oct 19, 2026.

  • #538 by @gpx1000 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
documentation

Research direction

Read the Vertex Input Description chapter, especially the Attribute Descriptions section, and compare its wording with the shown Slang VSInput and C++ VertexInputAttributeDescription locations. Confirm how the tutorial’s Slang example maps vertex inputs to locations, then clarify the text or make locations explicit with [[vk::location(N)]]. Done when the explanation matches the example and no longer implies absent GLSL annotations.

Written by the indexing model from the issue text.

Description

In the Vertex Input Description chapter, the following sentence appears:

The location parameter references the location directive of the input in the vertex shader.

However, the tutorial now uses Slang, and the vertex shader does not contain any explicit location annotations:

struct VSInput {
    float2 inPosition;
    float3 inColor;
};

Meanwhile, the C++ code explicitly uses locations 0 and 1 in VertexInputAttributeDescription.

The current wording seems to refer to GLSL's layout(location = N) syntax, which is not present in the Slang example.

It might be helpful to update this section to explain how Slang assigns vertex input locations implicitly, or alternatively, make the locations explicit using [[vk::location(N)]].

Dominant language
C++
Stars
444
Forks
145
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KhronosGroup/Vulkan-Tutorial

All issues in KhronosGroup/Vulkan-Tutorial

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.