Open JuanDiegoMontoya opened 8 months ago
Thanks for bringing this up. The way format properties are stored in Vulkan is very inconvenient for relational databases, so I only add newer flags when requested. I'll take a look at this.
See https://github.com/SaschaWillems/vulkan.gpuinfo.org/pull/93
No ETA on a release-date, but hopefully soon.
Currently these pages only show support for 11 of the original 13 bits from VkFormatFeatureFlagBits. Also missing are the bits added in 1.1 and 1.2, as well as the new ones from VK_KHR_format_feature_flags2. Below is an image of the feature flags currently shown when I visit https://vulkan.gpuinfo.org/listoptimaltilingformats.php.
I would like to see all of the feature flags in core Vulkan show up on the table, but I could see that causing issues with the current formatting. I'm not afraid to scroll horizontally though 😄
For what it's worth, I'm particularly interested in seeing
VK_FORMAT_FEATURE_2_STORAGE_READ_WITHOUT_FORMAT_BIT
andVK_FORMAT_FEATURE_2_STORAGE_WRITE_WITHOUT_FORMAT_BIT
added to the table since I'm using these in a noncommercial project.