search

SaschaWillems / VulkanCapsViewer

Vulkan hardware capability viewer
GNU Lesser General Public License v3.0
316 stars 69 forks source link

Format flags 2 #194

Open nanokatze opened 1 year ago

nanokatze commented 1 year ago

I feel like listing storage read/write without format ones would be useful. I expect the video people might be interested in video flags as well, at some point in the future, so that would require the same preliminary work in my understanding.

SaschaWillems commented 1 year ago

I've been taking a look at both of these. FormatFlags2 will probably land in the database, but not sure about the video ones. Last time I looked at the api for getting support video format flags it looked pretty complex and seemed like a lot of work.

nanokatze commented 1 year ago

I'm not after video flags myself, just mentioned those as a possible extra justification for format flags 2 in general

teoxoy commented 1 year ago

+1 for VkFormatProperties3/VkFormatFeatureFlagBits2

We are looking forward to using those to analyze the landscape (via https://github.com/kainino0x/gpuinfo-vulkan-query) for the WebGPU spec (https://github.com/gpuweb/gpuweb).

As far as I can tell, the DB already uses a bigint but the reporting tool (https://github.com/SaschaWillems/VulkanCapsViewer) doesn't query those extended format properties.

SaschaWillems commented 1 year ago

As far as I can tell, the DB already uses a bigint

This was an oversight by me. MySQL's bigint is a signed type, that's why the database has some negative values. I'll change that to unsigned. I also did a conversion to int at the client side, as JSON doesn't really has support for large integer types.

Both things that need fixing before adding in the new feature flags ;)