Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VkRenderingAreaInfoKHR manual isn't clear #2270

Open
konstantinegorov opened this issue Nov 10, 2023 · 2 comments
Open

VkRenderingAreaInfoKHR manual isn't clear #2270

konstantinegorov opened this issue Nov 10, 2023 · 2 comments

Comments

@konstantinegorov
Copy link

From the VkRenderingAreaInfoKHR manual page:

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?

@konstantinegorov konstantinegorov changed the title VkRenderingAreaInfoKHR manual page isn't clear VkRenderingAreaInfoKHR manual isn't clear Nov 10, 2023
@gfxstrand
Copy link
Contributor

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.

@TomOlson
Copy link

Request for more useful spec language is tracked internally at https://gitlab.khronos.org/vulkan/vulkan/-/issues/3702

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants