Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error messages for descriptor mis-matches #16

Closed
karl-lunarg opened this issue May 14, 2018 · 3 comments
Closed

Improve error messages for descriptor mis-matches #16

karl-lunarg opened this issue May 14, 2018 · 3 comments
Assignees
Labels
Enhancement New feature or request
Milestone

Comments

@karl-lunarg
Copy link
Contributor

Issue by tobine (MIGRATED)
Tuesday Jan 24, 2017 at 23:36 GMT
Originally opened as KhronosGroup/Vulkan-LoaderAndValidationLayers#1404


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.

@karl-lunarg karl-lunarg added this to the P2 milestone May 14, 2018
@karl-lunarg karl-lunarg added the Enhancement New feature or request label May 14, 2018
@karl-lunarg
Copy link
Contributor Author

Comment by punkUser (MIGRATED)
Thursday Mar 23, 2017 at 16:57 GMT


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 :)

@karl-lunarg
Copy link
Contributor Author

Comment by tobine (MIGRATED)
Friday Jul 07, 2017 at 15:54 GMT


#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.

@tobine
Copy link
Contributor

tobine commented Dec 20, 2018

This is done including the follow-on request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants