Skip to content
This repository has been archived by the owner on Jun 18, 2021. It is now read-only.

viewportCount set to 0 instead of 1, failing validation on Vulkan backend #665

Closed
infinitesnow opened this issue Dec 5, 2020 · 1 comment · Fixed by #663
Closed

viewportCount set to 0 instead of 1, failing validation on Vulkan backend #665

infinitesnow opened this issue Dec 5, 2020 · 1 comment · Fixed by #663
Labels
bug Something isn't working

Comments

@infinitesnow
Copy link
Contributor

I am not using multiview features, but it seems that the viewport count is incorrectly set at pipeline creation:

[0.110121 ERROR]()(no module): 
VALIDATION [VUID-VkPipelineViewportStateCreateInfo-viewportCount-01216 (-376016417)] : Validation Error: [ VUID-VkPipelineViewportStateCreateInfo-viewportCount-01216 ] Object 0: handle = 0x5628bad9a280, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xe99671df | vkCreateGraphicsPipelines: The VkPhysicalDeviceFeatures::multiViewport feature is disabled, but pCreateInfos[0].pViewportState->viewportCount (=0) is not 1. The Vulkan spec states: If the multiple viewports feature is not enabled, viewportCount must not be greater than 1 (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-VkPipelineViewportStateCreateInfo-viewportCount-01216)
object info: (type: DEVICE, hndl: 94732933505664)

Attaching vulkaninfo, vulkan trace and wgpu trace
vkinfo.txt
trace.tar.gz
vk_apidump.log

@kvark
Copy link
Member

kvark commented Dec 5, 2020

This is fixed in gfx-rs/gfx#3500, it's still bubbling up to wgpu-rs.

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

Successfully merging a pull request may close this issue.

2 participants