Regarding the swapchain validation layer issue caused by multiple QWidgets in vsgQt. #1710
Unanswered
zhuzhiyong8679
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
question
When I use the vsgqtwindows and vsgqtmdi examples, everything works correctly. However, when I made some modifications to vsgqtwindows — using QStackedWidget to create three QWidgets stacked on top of vsgQt::Window and switching between them — a problem occurs.
The validation layer error is as follows:
error
VUID-vkAcquireNextImageKHR-surface-07783(ERROR / SPEC): msgNum: -1391585802 - Validation Error: [ VUID-vkAcquireNextImageKHR-surface-07783 ] Object 0: handle = 0x1bc00000001bc, type = VK_OBJECT_TYPE_SWAPCHAIN_KHR; | MessageID = 0xad0e15f6 | vkAcquireNextImageKHR(): Application has already previously acquired 2 images from swapchain. Only 2 are available to be acquired using a timeout of UINT64_MAX (given the swapchain has 3, and VkSurfaceCapabilitiesKHR::minImageCount is 2). The Vulkan spec states: If forward progress cannot be guaranteed for the surface used to create the swapchain member of pAcquireInfo, the timeout member of pAcquireInfo must not be UINT64_MAX (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-vkAcquireNextImageKHR-surface-07783) Objects: 1 [0] 0x1bc00000001bc, type: 1000001000, name: NULLcodes:
I modified the code of vsgqtwindows. When I switch to the third page, a validation layer error occurs. What should I do? Thank you again. Finally, I think different Qt components might produce different effects. For example, QStackedWidget hides non‑current pages. I suppose I should do something in the Window::hideEvent(QHideEvent* /e/) function.
Beta Was this translation helpful? Give feedback.
All reactions