vkd3d: Only put the mutable descriptor set once in the pipeline layout.
- Oct 23, 2024
-
-
Giovanni Mascellani authored
The computation is also written in the code now instead of in the comments.
-
Giovanni Mascellani authored
Currently the mutable descriptor set is repeated many times in the pipeline layout in order to cover the indices for all the descriptor types that would be present if mutable descriptors were not used. This is useless and wasteful, but was necessary before the descriptor sets backing the SRV-UAV-CBV heap were moved at the end of the allocation table because descriptor set indices are currently a compile-time constant in many places. Now this is not needed any more and we can just avoid putting many copies of the mutable descriptor set in the pipeline layout, making it easier to meet Vulkan implementation limits.
-
Giovanni Mascellani authored
So that when mutable descriptors are in use we can avoid putting the other descriptor sets backing the SRV-UAV-CBV descriptor heap in the pipeline layout altogether.
-
Giovanni Mascellani authored
So we avoid hardcoding that it is number zero. There are two goals here: first making the code easier to understand and second allow reshuffling the descriptor set allocation in a later commit.
-