You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2018. It is now read-only.
Received feedback that the error messages for incompatibility between descriptor layout and pipeline layout could be clearer. Need to make sure which components come from pipeline layout are clearly distinguished from the separate descriptor layout in the error message.
The text was updated successfully, but these errors were encountered:
Just want to add that we definitely would like to see improvements to these descriptor type error messages as well. In particular, the ones that say things like:
Type mismatch on descriptor slot 0.1 (used as type ptr to const uniform image(dim=5, sampled=2)) but descriptor of type VK_DESCRIPTOR_TYPE_UNIFORM_TEXEL_BUFFER
It would be super-useful to know what type of descriptor (enum) it is actually expecting here, as "ptr to const uniform image(dim=5, sampled=2))" is perhaps less useful than you would think :)
#1934 addresses my initial concern. I looked at the follow-on request from @punkUser which is a bit trickier. @chrisforbes can you take a look? One possibility I was looking at was to refactor descriptor_type_match() in shader_validation.cpp to use a utility function that would return a vector of acceptable VkDescriptorType values to compare descriptor_type against. The utility function could then also be used to print the acceptable VkDescriptorTypes in the error message. This was a bit messy, though, and I wanted to see if you had a better idea.
Received feedback that the error messages for incompatibility between descriptor layout and pipeline layout could be clearer. Need to make sure which components come from pipeline layout are clearly distinguished from the separate descriptor layout in the error message.
The text was updated successfully, but these errors were encountered: