Can't use vkGetSwapchainImagesKHR with OpenGL

[LouisClt]

Can't use vkGetSwapchainImagesKHR with OpenGL

[DragonJoker]

Hi
So, I've tried, and I haven't encountered that issue, did you make sure you had ashesGlRenderer.dll in the same folder as ashes-1.dll ?

[LouisClt]

Hello,

Thanks for your answer.

Yes I did make sure that I had the ashesGlRenderer.dll in the same folder.

I managed to make my code work (there are still OpenGL errors (glBlitFramebuffer) but it is another issue I think) by adding this code:

#if VK_KHR_swapchain
			VkExtensionProperties{ VK_KHR_SWAPCHAIN_EXTENSION_NAME, VK_KHR_SWAPCHAIN_SPEC_VERSION },
#endif

in ash_opengl.cpp line 4608 (which activated the extension VK_KHR_swapchain, else the plugin returned that this extension was not activated and we could not do the vkGetInstanceProcAddr correctly)

For the static linking without vkGetInstanceProcAddr I had to add :

GlRenderer_API VkResult VKAPI_CALL vkGetSwapchainImagesKHR(
		VkDevice device,
		VkSwapchainKHR swapchain,
		uint32_t* pSwapchainImageCount,
		VkImage* pSwapchainImages)
	{
		return ashes::gl::vkGetSwapchainImagesKHR(device, swapchain, pSwapchainImageCount, pSwapchainImages);
	}

line 4750 of the same file (and the corresponding declaration in the hpp file).

What I do not understand is how it can work for you. Maybe the test you've done was from the library itself that does not care about the API that is exposed ?

[DragonJoker]

The idiomatic way for Ashes loading is using ICD mode (setting the environment var VK_ICD_FILENAMES to the appropriate json file), and if not, I strongly advise against static linking, which is a convenient but bad way of using Vulkan.
Also, VK_KHR_swapchain being a device extension, its function pointers should be loaded using vkGetDeviceProcAddr (even though Vulkan loader may accept loading them through vkGetProcAddr or vkGetInstanceProcAddr, I don't allow it in Ashes' renderers).

[LouisClt]

My bad, with vkGetDeviceProcAddr, I have no more issues. I was not aware that the correct way for loading functions was dependant on the type of the extension, having only worked with Vulkan SDK.
I will look into ICD.
Thanks for your answers,