Add Section For Buffer Device Address and Vertex Pulling

Open
#356 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp
Domain
computer-graphics, documentation

Research direction

Start by reviewing the existing tutorial’s traditional vertex-buffer and descriptor path, then determine the scope and teaching sequence for a vertex-pulling and buffer-device-address section. Done means a complete, integrated tutorial chapter that explains the alternative workflow and its relationship to the existing path.

Written by the indexing model from the issue text.

Description

documentation

Maybe it would make sense to add an additional chapter that introduces vertex pulling + buffer device address as an alternative to the traditional vertex buffer + descriptor path?

The motivation being:

closer to modern engine architectures (GPU-driven, bindless-style data)

aligns with patterns used in ray tracing and mesh/task workflows

gives a more “direct memory access” model (somewhat CUDA-like)

useful for large-scale transform / vertex data handling

The existing path is great for teaching core Vulkan concepts — but adding a “Vertex Pulling with Device Address” section could be really valuable?

Dominant language
C++
Stars
424
Forks
127
Avg merge
2d 22h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

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.