KhronosGroup / KhronosGroup/Vulkan-Tutorial
Use of old `transitionImageLayout` in later chapters
- Dominant language
- C++
- Stars
- 418
- Forks
- 126
- Avg merge
- 11d 6h
- Merged PRs (30d)
- 31
Description
The Khronos Vulkan Tutorial introduces `vk::ImageMemoryBarrier2` "`Drawing a triangle/Drawing/Command Buffers`" , but in a later chapter : "`Texture Mapping/Images`" , it again tells us to create `transitionImageLayout` function with the old `vk::ImageMemoryBarrier`
Contributor guide
Research direction
Compare the transitionImageLayout guidance in “Drawing a triangle/Drawing/Command Buffers” with “Texture Mapping/Images,” focusing on the differing vk::ImageMemoryBarrier2 and vk::ImageMemoryBarrier APIs. Update the later chapter so its instructions are consistent with the newer approach, then verify that the tutorial no longer directs readers to the old barrier type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100