Resolve "Resizing-Event"

added 👍 Feature 💻 Doing 🖥️ I/O labels

added 1 commit

df58bf24 - [#34 (closed)] add initial for recreation of swapchain

Compare with previous version

added 1 commit

a10fd28d - [#34 (closed)] add recreation for swapchain and imageViews

Compare with previous version

added 3 commits

a10fd28d...ff713793 - 2 commits from branch develop
25c4b97e - Merge branch 'develop' into 34-resizing-event

Compare with previous version

added 1 commit

8f3645df - [#34 (closed)][Fix] fix MSVC compilation

Compare with previous version

added 5 commits

8f3645df...20bd1dda - 4 commits from branch develop
c83c082f - Merge branch 'develop' of gitlab.uni-koblenz.de:vulkan2021/vkcv-framework into 34-resizing-event

Compare with previous version

added 1 commit

2b83be1a - Add proper resizing with dynamic pipeline configs. Refactor swapchain slightly.

Compare with previous version

added 1 commit

0943c295 - minor beautifications.

Compare with previous version

added 2 commits

55f9c51c - [#34 (closed)] Correct camera aspect ratio on resize
07a8d7b8 - Merge branch '34-resizing-event' of...

Compare with previous version

Crashes on resizing with black screen causing a GPU reset!

added 1 commit

2406d39c - [#34 (closed)] added resizing event to camera

Compare with previous version

VUID-VkFramebufferCreateInfo-flags-04533(ERROR / SPEC): msgNum: -26532824 - Validation Error: [ VUID-VkFramebufferCreateInfo-flags-04533 ] Object 0: handle = 0x555555d5c680, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xfe6b2428 | vkCreateFramebuffer(): VkFramebufferCreateInfo attachment #0 mip level 800 has width smaller than the corresponding framebuffer width (802). The Vulkan spec states: If flags does not include VK_FRAMEBUFFER_CREATE_IMAGELESS_BIT, each element of pAttachments that is used as an input, color, resolve, or depth/stencil attachment by renderPass must have been created with a VkImageCreateInfo::width greater than or equal to width (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-VkFramebufferCreateInfo-flags-04533)
    Objects: 1
        [0] 0x555555d5c680, type: 3, name: NULL

Neuer Fehler ^-^

VUID-vkQueuePresentKHR-pWaitSemaphores-03268(ERROR / SPEC): msgNum: 622825338 - Validation Error: [ VUID-vkQueuePresentKHR-pWaitSemaphores-03268 ] Object 0: handle = 0x555555d4c8e0, type = VK_OBJECT_TYPE_QUEUE; Object 1: handle = 0x100000000010, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x251f8f7a | vkQueuePresentKHR: Queue VkQueue 0x555555d4c8e0[] is waiting on pWaitSemaphores[1] (VkSemaphore 0x100000000010[]) that has no way to be signaled. The Vulkan spec states: All elements of the pWaitSemaphores member of pPresentInfo must reference a semaphore signal operation that has been submitted for execution and any semaphore signal operations on which it depends (if any) must have also been submitted for execution (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkQueuePresentKHR-pWaitSemaphores-03268)
    Objects: 2
        [0] 0x555555d4c8e0, type: 4, name: NULL
        [1] 0x100000000010, type: 5, name: NULL
VUID-VkPresentInfoKHR-pImageIndices-01296(ERROR / SPEC): msgNum: -945112042 - Validation Error: [ VUID-VkPresentInfoKHR-pImageIndices-01296 ] Object 0: handle = 0x173650000017365, type = VK_OBJECT_TYPE_SWAPCHAIN_KHR; | MessageID = 0xc7aabc16 | vkQueuePresentKHR: pSwapchains[0] image index 0 has not been acquired. The Vulkan spec states: Each element of pImageIndices must be the index of a presentable image acquired from the swapchain specified by the corresponding element of the pSwapchains array, and the presented image subresource must be in the VK_IMAGE_LAYOUT_PRESENT_SRC_KHR layout at the time the operation is executed on a VkDevice (https://github.com/KhronosGroup/Vulkan-Docs/search?q=)VUID-VkPresentInfoKHR-pImageIndices-01296)
    Objects: 1
        [0] 0x173650000017365, type: 1000001000, name: NULL
terminate called after throwing an instance of 'vk::OutOfDateKHRError'
  what():  vk::Queue::presentKHR: ErrorOutOfDateKHR
Signal: SIGABRT (Aborted)

added 2 commits

38098a4a - [#34 (closed)] Fixed the problems of inconsistent frame-buffer size related to window
fec73717 - Merge branch '34-resizing-event' of...

Compare with previous version

VUID-vkCmdDrawIndexed-None-02859(ERROR / SPEC): msgNum: -1813603574 - Validation Error: [ VUID-vkCmdDrawIndexed-None-02859 ] Object 0: handle = 0x5637d6ae3650, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0x200000000020, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x93e69b0a | vkCmdDrawIndexed(): VkPipeline 0x200000000020[] doesn't set up VK_DYNAMIC_STATE_VIEWPORT|VK_DYNAMIC_STATE_SCISSOR, but it calls the related dynamic state setting commands The Vulkan spec states: There must not have been any calls to dynamic state setting commands for any state not specified as dynamic in the VkPipeline object bound to the pipeline bind point used by this command, since that pipeline was bound (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkCmdDrawIndexed-None-02859)
    Objects: 2
        [0] 0x5637d6ae3650, type: 6, name: NULL
        [1] 0x200000000020, type: 19, name: NULL

added 1 commit

fcf7cd40 - [#34 (closed)] Corrected triangle application

Compare with previous version

added 1 commit

89bc0fea - [#34 (closed)] Fixed random crash during resizing!

Compare with previous version

Jetzt schmiert es nurnoch weg, wenn die Breite oder Höhe gleich 0 ist... und es wird noch nicht der DynamicState beim Recorden gecheckt... ^^'

added 1 commit

58cc9203 - save pipeline config and check against pipeline's dimensions when dynamically...

Compare with previous version

added 1 commit

973d1da2 - [#34 (closed)] Fix minimize crash

Compare with previous version

Now it says:

terminate called after throwing an instance of 'vk::FormatNotSupportedError'
  what():  vk::PhysicalDevice::getImageFormatProperties: ErrorFormatNotSupported

Process finished with exit code 134 (interrupted by signal 6: SIGABRT)

approved this merge request

Wenn ich besonders wild resize crasht's mit folgendem:

terminate called after throwing an instance of 'vk::OutOfDateKHRError'
  what():  vk::Queue::presentKHR: ErrorOutOfDateKHR

Und wenn ich das Fenster auf unter 2x2 pixel resize gibt's:

terminate called after throwing an instance of 'vk::FormatNotSupportedError'
  what():  vk::PhysicalDevice::getImageFormatProperties: ErrorFormatNotSupported

requested review from @thollmann

approved this merge request

marked this merge request as ready

merged

mentioned in commit c5ea5767

Resolve "Resizing-Event"

Merge request reports

Activity