Developer knowledge network ยท moderated exchange

UnreliableCode Community

Developer Research, Reverse Engineering & Coding Community

Knowledge indexLive
4Categories
919Threads
2.8KPosts
Tutorial

Understanding Vulkan Descriptor Indexing (Bindless Textures) vs Classic Descriptor Sets [StackOverflow Architecture Guide]

graphics_pipeline_pro
DirectX / Vulkan Engineer
MEMBER
Rep: 172
Join Date: Sep 2018
Posts: 10
Thanks: 51
3 weeks ago ยท Jul 29, 2026 3:01 PM
#1

Why traditional descriptor set binding is a bottleneck in modern graphics engines:

In legacy Vulkan, drawing a mesh with 20 different materials required updating and rebinding descriptor sets (vkCmdBindDescriptorSets) between draw calls, stalling the CPU-GPU pipeline.

Bindless Descriptor Indexing:

  • Array of all 10,000 textures in the game bound to a single unbounded descriptor array: layout(binding = 0) uniform sampler2D textures[];.
  • Vertex / Material data passes an integer texture index (uint textureId).
  • Shaders sample dynamically: vec4 color = texture(textures[nonuniformEXT(mat.textureId)], uv);.

Reduces 1,000 draw call state changes down to a single batched multi-draw indirect command!

shader_magician
HLSL / GLSL Dev
MEMBER
Rep: 176
Join Date: Jan 2021
Posts: 8
Thanks: 32
3 weeks ago ยท Jul 29, 2026 7:40 PM
#2

Bindless rendering is the single biggest architectural shift in modern rendering engines (Unreal 5, Frostbite, id Tech).

dx12_render_dev
DX12 Master
MEMBER
Rep: 55
Join Date: Oct 2020
Posts: 9
Thanks: 65
3 weeks ago ยท Jul 30, 2026 2:21 AM
#3

Remember to enable the descriptorBindingPartiallyBound and runtimeDescriptorArray features in VkPhysicalDeviceVulkan12Features.