Open vandench opened 9 months ago
Thanks for bringing this up. Doing this won't be easy as to how the database back-end works, but I'll be looking into it. For newer devices a workaround is to select VK1.1 (or newer) via the global version selector.
When looking at the list of supported operations for image formats, transfer source and destination never get above 85.77%, even when support for sampling is at 100%.
The root cause seems to be that the feature flags for transfer operations weren't added until Vulkan 1.1 (or with VK_KHR_maintenence1), but some drivers reported never got an update to the database past Vulkan 1.0. In the description for VK_FORMAT_FEATURE_TRANSFER_SRC_BIT and VK_FORMAT_FEATURE_TRANSFER_DST_BIT, it is mentioned that if a driver only supports Vulkan 1.0, then the transfer operations are implied when the feature flag is not 0 (i.e. when the driver supports any other operation on that format).
It would be a nice QoL feature, and reduce some confusion, if the implicit support for transfer operations from 1.0 drivers was included in the calculation of the optimal tiling support list.