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

Unexpected validation warnings #1390

Closed
almarklein opened this issue May 17, 2021 · 6 comments · Fixed by #1391
Closed

Unexpected validation warnings #1390

almarklein opened this issue May 17, 2021 · 6 comments · Fixed by #1391
Assignees
Labels
type: bug Something isn't working

Comments

@almarklein
Copy link
Contributor

I keep getting these two validation warnings for even the simplest of shaders. The code does run (no crash or panic).

This is on Win10 with Intel Graphics (things crash if enable the NVida GPU, but that's a different issue). Using wgpu-native from master (naga 25). LunarSDK 1.2.176.1 (05-May-2021). Shaders are provided to wgpu in WGSL.

ImageMSArray capability:

VALIDATION [VUID-VkShaderModuleCreateInfo-pCode-01091 (0xa7bb8db6)] : Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-01091 ] Object 0: handle = 0x14f78a6dfe8, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xa7bb8db6 | vkCreateShaderModule(): The SPIR-V Capability (ImageMSArray) was declared, but none of the requirements were met to use it. The Vulkan spec states: If pCode declares any of the capabilities listed in the SPIR-V Environment appendix, one of the corresponding requirements must be satisfied (https://vulkan.lunarg.com/doc/view/1.2.176.1/windows/1.2-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-01091)
object info: (type: DEVICE, hndl: 0x14f78a6dfe8)

InterpolationFunction capability:

VALIDATION [VUID-VkShaderModuleCreateInfo-pCode-01091 (0xa7bb8db6)] : Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-01091 ] Object 0: handle = 0x14f78a6dfe8, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xa7bb8db6 | vkCreateShaderModule(): The SPIR-V Capability (InterpolationFunction) was declared, but none of the requirements were met to use it. The Vulkan spec states: If pCode declares any of the capabilities listed in the SPIR-V Environment appendix, one of the corresponding requirements must be satisfied (https://vulkan.lunarg.com/doc/view/1.2.176.1/windows/1.2-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-01091)
object info: (type: DEVICE, hndl: 0x14f78a6dfe8)

Also seeing this from time to time (poolSizeCount must be greater than 0):

VALIDATION [VUID-VkDescriptorPoolCreateInfo-poolSizeCount-arraylength (0x8e5726c)] : Validation Error: [ VUID-VkDescriptorPoolCreateInfo-poolSizeCount-arraylength ] Object 0: handle = 0x1fb7749e588, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x8e5726c | vkCreateDescriptorPool: parameter pCreateInfo->poolSizeCount must be greater than 0. The Vulkan spec states: poolSizeCount must be greater than 0 (https://vulkan.lunarg.com/doc/view/1.2.176.1/windows/1.2-extensions/vkspec.html#VUID-VkDescriptorPoolCreateInfo-poolSizeCount-arraylength)
object info: (type: DEVICE, hndl: 0x1fb7749e588)
@kvark kvark transferred this issue from gfx-rs/naga May 17, 2021
@kvark kvark transferred this issue from gfx-rs/gfx May 17, 2021
@kvark kvark added the type: bug Something isn't working label May 17, 2021
@kvark
Copy link
Member

kvark commented May 17, 2021

@almarklein thank you for filing! Could you record an API trace reproducing the last validation error?
I'm addressing the first two.

@almarklein
Copy link
Contributor Author

About the PoolSizeCount warning: it appeared in an example (in wgpu-py) that is basically a port of the hello triangle. It seems related to #240. I made the warning disappear by not creating empty bind groups (and layouts). Incidentally, that example started crashing after the recent changes to wgpu-native, and the applied fix also made it work again.

It could well be that the hello triangle in wgpu-native is also broken now. I'll have a look in a moment.

@kvark
Copy link
Member

kvark commented May 17, 2021

Filed zakarumych/gpu-descriptor#14 upstream.
The rest is addressed by #1391

@kvark kvark self-assigned this May 17, 2021
@bors bors bot closed this as completed in 13f2ca5 May 17, 2021
@almarklein
Copy link
Contributor Author

Following up on the triangle example in wgpu-native: gfx-rs/wgpu-native#97

@zakarumych
Copy link

Patch for gpu-descriptor has been released

@almarklein
Copy link
Contributor Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants