In Vulkan 1.0, developers relied on vkGetPhysicalDeviceFeatures . While functional, it returned a fixed VkPhysicalDeviceFeatures struct. As the Khronos Group introduced new hardware features—like ray tracing, mesh shaders, or variable rate shading—this fixed structure became a bottleneck. There was no clean way to append new features without breaking the existing API.
Because it uses a linked list of structures, the API can support any number of future hardware features without changing the function signature. vkgetphysicaldevicefeatures2
: Always ensure every struct in your chain has the correct sType initialized. Forgetting this is a leading cause of driver crashes and "garbage" data returns. Conclusion In Vulkan 1
Furthermore, enabling features at device creation was similarly fragmented. VkDeviceCreateInfo had a pEnabledFeatures pointer, but it only pointed to the original VkPhysicalDeviceFeatures . To enable newer features, you had to chain structures into the pNext chain of VkDeviceCreateInfo . This created a disconnect: querying and enabling features used different mechanisms, and there was no guarantee that queried features matched the enabling structures. There was no clean way to append new