Hi,
Thanks for the awesome library!
I'm using ArchLinux, and it seems when using AMD Integrated Graphics + mesa radv vulkan + kwin (wayland) , the assertion under avk::window::construct_backbuffers() will fail for the initial window creation.
Looking into the problem, it seems at least for some of the mesa-implemented vulkan drivers, the driver reports surface capabilities with minImageCount=3, maxImageCount=0, but taking 3 into the SwapChainCreateInfo will result in a swapchain with 5 images.
It seems that the same issue is also addressed in issues in a fork of mesa. According to Vulkan spec, it seems that implementations are able to create a swapchain with more images than requested.
A quick walkaround would be setting mainWnd->set_number_of_presentable_images(5u); from user side. But I think this might be worth noted in case someone ran into the same problem.
Thanks!
Hi,
Thanks for the awesome library!
I'm using ArchLinux, and it seems when using AMD Integrated Graphics + mesa radv vulkan + kwin (wayland) , the assertion under
avk::window::construct_backbuffers()will fail for the initial window creation.Looking into the problem, it seems at least for some of the mesa-implemented vulkan drivers, the driver reports surface capabilities with
minImageCount=3,maxImageCount=0, but taking 3 into the SwapChainCreateInfo will result in a swapchain with 5 images.It seems that the same issue is also addressed in issues in a fork of mesa. According to Vulkan spec, it seems that implementations are able to create a swapchain with more images than requested.
A quick walkaround would be setting
mainWnd->set_number_of_presentable_images(5u);from user side. But I think this might be worth noted in case someone ran into the same problem.Thanks!