You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
either the extent.width member in renderArea is a multiple of the horizontal granularity or offset.x+extent.width is equal to the width of the framebuffer in the VkRenderPassBeginInfo
What does framebuffer width mean in case of dynamic rendering?
The text was updated successfully, but these errors were encountered:
konstantinegorov
changed the title
VkRenderingAreaInfoKHR manual page isn't clear
VkRenderingAreaInfoKHR manual isn't clear
Nov 10, 2023
After a bit of internal discussion, the framebuffer size is a little misleading with or without dynamic rendering. The real edge condition is if offset.x + extent.width is equal to the width of all of the bound attachment image views. It's possible to make a framebuffer with a size smaller than one or more of the attachments and, in that case, the render area lining up with the edge of the framebuffer is insufficient, even with render passes.
From the VkRenderingAreaInfoKHR manual page:
What does framebuffer width mean in case of dynamic rendering?
The text was updated successfully, but these errors were encountered: