Vulkan: Please consider adding another sample count to sampledImageIntegerSampleCounts
Hi, ANGLE developer here.
When implementing GLES3.1 on Vulkan, we have encountered a discrepancy between GLES and Vulkan where GLES allows creation of multisampled textures with a sample count of 1, while Vulkan disallows creating images with such a configuration. After many discussions, we decided it's highly impractical to try to emulate this, and we should not advertise sample count of 1 on multisampled textures. Presumably, some/many GL vendors already do this.
For integer formats, it looks like Mesa sets sampledImageIntegerSampleCounts
=1 on both AMD and Intel. That means we won't be able to support GLES3.1 on Mesa for such a trivial limitation. From gpuinfo.org, it looks like AMD/windows and Intel/windows both have more sample counts in sampledImageIntegerSampleCounts
, so there shouldn't be any hardware limitations.
This issue is a request to please consider adding more sample counts to sampledImageIntegerSampleCounts
to continue allowing ANGLE to run GLES3.1 (and GLES3.2) tests on mesa.