Clarify vertex input bindings
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 78/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
调研方向
从教程中顶点输入描述章节的“Binding descriptions”小节开始，这是 issue 链接并引用的内容。issue 提议了替换文字：先将顶点输入绑定定义为带编号的插槽，然后介绍 stride 和 inputRate，最后说明 bindVertexBuffers() 将在下一章介绍。当该小节按此顺序阅读时即视为完成；图示为可选项。payload 没有给出源文件名，请根据小节标题找到它。
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- C++
- 星标
- 432
- 派生
- 133
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 4
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
KhronosGroup/Vulkan-Tutorial 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
KhronosGroup/Vulkan-Tutorial#528 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
KhronosGroup/Vulkan-Tutorial#525 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
KhronosGroup/Vulkan-Tutorial#524 ·
-
Multithreading chapter still talks about render passes可能已有人在做 @SaschaWillems 于 22 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
KhronosGroup/Vulkan-Tutorial#519 · 已指派 1 人 ·
-
Use of old `transitionImageLayout` in later chapters可能已有人在做 @gpx1000 于 22 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
KhronosGroup/Vulkan-Tutorial#508 · 已指派 1 人 ·
查看 KhronosGroup/Vulkan-Tutorial 的全部 Issue
相似的 Issue
-
1 type: problem 2 scope: firmware 3 good first issue
难度 2/5 1-3 小时 新手友好度 65/100
SpaceTeam/STS1_COBC_SW#511 ·
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 82/100
imaaiagent/fumi#3 ·
-
A bare port in --modelserver does not reach the model server可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug
难度 2/5 1-3 小时 新手友好度 76/100
rocketride-org/rocketride-server#2618 · 1 条评论 ·
维护者通常 1 天内回复
-
bug format I/O medium priority rt_lib
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
refactor
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复