Skip to content

swapchain_recreation missing swapchainMaintenance1 feature #1287

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

Open
spencer-lunarg opened this issue Mar 6, 2025 · 1 comment · May be fixed by #1319
Open

swapchain_recreation missing swapchainMaintenance1 feature #1287

spencer-lunarg opened this issue Mar 6, 2025 · 1 comment · May be fixed by #1319
Assignees

Comments

@spencer-lunarg
Copy link
Contributor

The latest Validation (future 1.4.309 SDK) I get

Validation Error: [ VUID-VkSwapchainCreateInfoKHR-swapchainMaintenance1-10157 ] | MessageID = 0xedce379e
vkCreateSwapchainKHR(): pCreateInfo->flags is VK_SWAPCHAIN_CREATE_DEFERRED_MEMORY_ALLOCATION_BIT_EXT, but swapchainMaintenance1 is not enabled.
The Vulkan spec states: If the swapchainMaintenance1 feature is not enabled, then flags must not include VK_SWAPCHAIN_CREATE_DEFERRED_MEMORY_ALLOCATION_BIT_EXT (https://docs.vulkan.org/spec/latest/chapters/VK_KHR_surface/wsi.html#VUID-VkSwapchainCreateInfoKHR-swapchainMaintenance1-10157)

for the swapchain_recreation example

Simple fix is to just enable the swapchainMaintenance1 feature along with the extension it already provides

@SaschaWillems SaschaWillems self-assigned this Mar 10, 2025
@SaschaWillems
Copy link
Collaborator

Will take some fundamental changes to the sample, as right now the gpu feature setup comes after the sample checking for extension support / enabling. Will try to take a stab at it.

@jeroenbakker-atmind jeroenbakker-atmind linked a pull request Apr 7, 2025 that will close this issue
20 tasks
@jeroenbakker-atmind jeroenbakker-atmind self-assigned this Apr 10, 2025
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

Successfully merging a pull request may close this issue.

3 participants