Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-89765

Vulkan: view3d example occasionally(?) has broken indexed drawing

    XMLWordPrintable

    Details

    • Commits:
      0dbed05bbc16c37483bea90b3eff3db899a0bf07 (qt/qtbase/dev) 42e1abccd0d3d1a327a3a7b9d5e7fc5e4e296716 (qt/qtbase/6.2)
    • Story Points:
      3

      Description

      While the issue of the occasionally missing 'ground' in the top-right view was known for some time on Linux/Intel (Mesa 20.2.4), with the Vulkan SDK 1.2.154 we can finally see some relevant messages coming from the validation layer:

      vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-commandBuffer-02701 ] Object 0: handle = 0x7facc4bba550, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xa87d398e | VkCommandBuffer 0x7facc4bba550[]: Index buffer object not bound to this command buffer when Indexed Draw attempted.. The Vulkan spec states: If the VkPipeline object bound to the pipeline bind point used by this command requires any dynamic state, that state must have been set for commandBuffer, and done so after any previously bound pipeline with the corresponding state not specified as dynamic (https://vulkan.lunarg.com/doc/view/1.2.154.0/linux/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-commandBuffer-02701)
      
      vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-04007 ] Object 0: handle = 0x7facc4bba550, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x5e4491cd | vkCmdDrawIndexed(): VkPipeline 0x520000000052[] expects that this Command Buffer's vertex binding Index 0 should be set via vkCmdBindVertexBuffers. This is because VkVertexInputBindingDescription struct at index 0 of pVertexBindingDescriptions has a binding value of 0. The Vulkan spec states: All vertex input bindings accessed via vertex input variables declared in the vertex shader entry point's interface must have either valid or VK_NULL_HANDLE buffers bound (https://vulkan.lunarg.com/doc/view/1.2.154.0/linux/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-04007)
      

      Update 8/9/21: Not sure what changed on my Windows setup, but the warnings are now shown on Windows as well:

      [1144] qt.scenegraph.general: Using QRhi with backend Vulkan
      [1144]   Graphics API debug/validation layers: 1
      [1144]   QRhi profiling and debug markers: 0
      [1144]   Shader/pipeline cache collection: 0
      [1144] qt.scenegraph.general: threaded render loop
      [1144] qt.scenegraph.general: Using sg animation driver
      [1144] qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
      [1144] qt.scenegraph.general: Using sg animation driver
      [1144] qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
      [1144] qt.scenegraph.general: Requesting Vulkan API 1.2 Instance-level version was reported as 1.2.162
      [1144] qt.rhi.general: Physical device 0: 'NVIDIA GeForce RTX 2060' 465.356.0 (api 1.2.168 vendor 0x10DE device 0x1F08 type 2)
      [1144] qt.rhi.general:     using this physical device
      [1144] qt.rhi.general: queue family 0: flags=0xf count=16
      [1144] qt.rhi.general: queue family 1: flags=0xc count=2
      [1144] qt.rhi.general: queue family 2: flags=0xe count=8
      [1144] qt.rhi.general: 137 device extensions available
      [1144] qt.rhi.general: Enabling device extensions:
      [1144] qt.rhi.general:   VK_KHR_swapchain
      [1144] qt.rhi.general:   VK_EXT_vertex_attribute_divisor
      [1144] qt.scenegraph.general: MSAA sample count for the swapchain is 1. Alpha channel requested = no.
      [1144] qt.scenegraph.general: rhi texture atlas dimensions: 2048x1024
      [1144] qt.rhi.general: Creating new swapchain of 3 buffers, size 1280x720, presentation mode 2
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-commandBuffer-02701 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xa87d398e | VkCommandBuffer 0x2554257d0b8[]: Index buffer object not bound to this command buffer when Indexed Draw attempted.. The Vulkan spec states: If the VkPipeline object bound to the pipeline bind point used by this command requires any dynamic state, that state must have been set for commandBuffer, and done so after any previously bound pipeline with the corresponding state not specified as dynamic (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-commandBuffer-02701)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-04007 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x5e4491cd | vkCmdDrawIndexed(): VkPipeline 0xbff8570000000052[] expects that this Command Buffer's vertex binding Index 0 should be set via vkCmdBindVertexBuffers. This is because VkVertexInputBindingDescription struct at index 0 of pVertexBindingDescriptions has a binding value of 0. The Vulkan spec states: All vertex input bindings accessed via vertex input variables declared in the vertex shader entry point's interface must have either valid or VK_NULL_HANDLE buffers bound (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-04007)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x2554257d0b8[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x2554257d0b8[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-commandBuffer-02701 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xa87d398e | VkCommandBuffer 0x25548913668[]: Index buffer object not bound to this command buffer when Indexed Draw attempted.. The Vulkan spec states: If the VkPipeline object bound to the pipeline bind point used by this command requires any dynamic state, that state must have been set for commandBuffer, and done so after any previously bound pipeline with the corresponding state not specified as dynamic (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-commandBuffer-02701)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-04007 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x5e4491cd | vkCmdDrawIndexed(): VkPipeline 0xbff8570000000052[] expects that this Command Buffer's vertex binding Index 0 should be set via vkCmdBindVertexBuffers. This is because VkVertexInputBindingDescription struct at index 0 of pVertexBindingDescriptions has a binding value of 0. The Vulkan spec states: All vertex input bindings accessed via vertex input variables declared in the vertex shader entry point's interface must have either valid or VK_NULL_HANDLE buffers bound (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-04007)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x25548913668[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x25548913668[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-commandBuffer-02701 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xa87d398e | VkCommandBuffer 0x2554257d0b8[]: Index buffer object not bound to this command buffer when Indexed Draw attempted.. The Vulkan spec states: If the VkPipeline object bound to the pipeline bind point used by this command requires any dynamic state, that state must have been set for commandBuffer, and done so after any previously bound pipeline with the corresponding state not specified as dynamic (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-commandBuffer-02701)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-04007 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x5e4491cd | vkCmdDrawIndexed(): VkPipeline 0xbff8570000000052[] expects that this Command Buffer's vertex binding Index 0 should be set via vkCmdBindVertexBuffers. This is because VkVertexInputBindingDescription struct at index 0 of pVertexBindingDescriptions has a binding value of 0. The Vulkan spec states: All vertex input bindings accessed via vertex input variables declared in the vertex shader entry point's interface must have either valid or VK_NULL_HANDLE buffers bound (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-04007)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x2554257d0b8[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x2554257d0b8[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-commandBuffer-02701 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xa87d398e | VkCommandBuffer 0x25548913668[]: Index buffer object not bound to this command buffer when Indexed Draw attempted.. The Vulkan spec states: If the VkPipeline object bound to the pipeline bind point used by this command requires any dynamic state, that state must have been set for commandBuffer, and done so after any previously bound pipeline with the corresponding state not specified as dynamic (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-commandBuffer-02701)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-04007 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x5e4491cd | vkCmdDrawIndexed(): VkPipeline 0xbff8570000000052[] expects that this Command Buffer's vertex binding Index 0 should be set via vkCmdBindVertexBuffers. This is because VkVertexInputBindingDescription struct at index 0 of pVertexBindingDescriptions has a binding value of 0. The Vulkan spec states: All vertex input bindings accessed via vertex input variables declared in the vertex shader entry point's interface must have either valid or VK_NULL_HANDLE buffers bound (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-04007)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x25548913668[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x25548913668[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-commandBuffer-02701 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xa87d398e | VkCommandBuffer 0x2554257d0b8[]: Index buffer object not bound to this command buffer when Indexed Draw attempted.. The Vulkan spec states: If the VkPipeline object bound to the pipeline bind point used by this command requires any dynamic state, that state must have been set for commandBuffer, and done so after any previously bound pipeline with the corresponding state not specified as dynamic (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-commandBuffer-02701)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-04007 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x5e4491cd | vkCmdDrawIndexed(): VkPipeline 0xbff8570000000052[] expects that this Command Buffer's vertex binding Index 0 should be set via vkCmdBindVertexBuffers. This is because VkVertexInputBindingDescription struct at index 0 of pVertexBindingDescriptions has a binding value of 0. The Vulkan spec states: All vertex input bindings accessed via vertex input variables declared in the vertex shader entry point's interface must have either valid or VK_NULL_HANDLE buffers bound (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-04007)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x2554257d0b8[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x2554257d0b8, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x2554257d0b8[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-commandBuffer-02701 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xa87d398e | VkCommandBuffer 0x25548913668[]: Index buffer object not bound to this command buffer when Indexed Draw attempted.. The Vulkan spec states: If the VkPipeline object bound to the pipeline bind point used by this command requires any dynamic state, that state must have been set for commandBuffer, and done so after any previously bound pipeline with the corresponding state not specified as dynamic (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-commandBuffer-02701)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-04007 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x5e4491cd | vkCmdDrawIndexed(): VkPipeline 0xbff8570000000052[] expects that this Command Buffer's vertex binding Index 0 should be set via vkCmdBindVertexBuffers. This is because VkVertexInputBindingDescription struct at index 0 of pVertexBindingDescriptions has a binding value of 0. The Vulkan spec states: All vertex input bindings accessed via vertex input variables declared in the vertex shader entry point's interface must have either valid or VK_NULL_HANDLE buffers bound (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-04007)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x25548913668[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      [1144] vkDebug: Validation: 0: Validation Error: [ VUID-vkCmdDrawIndexed-None-02721 ] Object 0: handle = 0x25548913668, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0xbff8570000000052, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x24afafc5 | vkCmdDrawIndexed(): binding #0 in pVertexAttributeDescriptions of VkPipeline 0xbff8570000000052[] is invalid in vkCmdBindVertexBuffers of VkCommandBuffer 0x25548913668[]. The Vulkan spec states: For a given vertex buffer binding, any attribute data fetched must be entirely contained within the corresponding vertex buffer binding, as described in Vertex Input Description (https://vulkan.lunarg.com/doc/view/1.2.162.0/windows/1.2-extensions/vkspec.html#VUID-vkCmdDrawIndexed-None-02721)
      

      This has something to do with mixing View3Ds with different renderModes in the same scene. One has Underlay here, the others use the default Offscreen. Just reducing the number of View3Ds to two (one Underlay, one Offscreen), the warnings appear. With just one of the two present there are no warnings.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            lagocs Laszlo Agocs
            Reporter:
            lagocs Laszlo Agocs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes