cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

particlepeter
Adept II
‎04-29-2016 08:55 AM

Extensions VK_KHR_surface and VK_KHR_win32_surface have disappeared

The mentioned extensions have disappears suddenly, unfortunately I am not sure why and when. I installed two things before I noticed the issue:

- Driver Crimson Edition 16.3.2

- LunarG Vulkan SDK 1.0.11.0

I doubt the later one is responsible, I tried all the other SDK versions without success, but who knows. Today I installed the Crimson Edition 16.4.2 Hotfix, but the problem remains.

The LunarG Vulkan Samples exit with a Missing extension error code. I confirmed within my own project that exactly the two mentioned extensions are missing. I had four extensions available on my system, VK_KHR_swapchain and VK_EXT_debug_report are still present.

I think the last driver which exposed all extensions was the beta driver Non-WHQL-64Bit-Radeon-Software-Crimson-16.4.2-Win10-Win8.1-Win7 from April the 20th.

Installing this driver over the current one does not solve the problem. I must admit that I am not sure if this is a driver bug at all, but what else could it be ?

As a side Note (some more fishiness): Even though yesterdays hotfix (16.4.2) is installed, the radeon settings window is convinced that Driver 16.3.2 (WHQL) is newer than the hotfix and suggest it to be installed. I tried that as well, didn't solve the problem either.

My System: APU: A10-7800, OS : Win 8.1 x64

Edit:

Meanwhile I installed Win 10 x64 as dual boot on the system and updated the drivers to Crimson Edition 16.4.2 Hotfix Win 10 x64. The problem does not exist on there, all four extensions are listed.

BUT (!!!) on Win 8 the implementation WAS listing 3 Queue Families, one of them a compute queue family with 4 queues.

Now, on Win 10 the implementation IS still listing 3 Families, but the compute queue exposes only 1 queue.

What's going on dear AMD engineers?

Message was edited by: Peter Particle

0 Likes
1 Solution
particlepeter
In response to dwitczak
Adept II
‎06-02-2016 07:26 AM

Actually I rather post a summary of two correct answers:

Update: After some experiments and a lot of web searching I figured that Crimson 16.5.1 Driver Version 16.15.2401.1002 is the latest for APUs and the right one for me in conjunction with LunarG VulkanSDK 1.0.8.0 and LunarG Vulkan Run Time Libraries 1.0.8.0.

As mentioned above about this driver, instance extension Extension: VK_KHR_swapchain is missing. That is because now it is device extension and works just fine.

I thought for a long time that even this driver is wrong, as calling vkCreateSwapchainKHR returned VK_ERROR_INITIALIZATION_FAILED.

The issue stems from  VK_LAYER_GOOGLE_unique_objects. The implementation lists it as available layer, but using it leads to the mentioned VK_ERROR. Without the layer everything is fine.

Is there any place where I get the information which Driver Version works with which LunarG Vulkan SDK? It was quite painful to figure this out with trial and error.

And the solution to the VK_LAYER_GOOGLE_unique_objects issue is:

Jon from LunarG did. While I was commenting on that issue I found additional references where people had also difficulties with that layer and the solution is that VK_LAYER_GOOGLE_unique_objects must be enabled as instance AND device layer. This might be the case for the other layers as well, but VK_LAYER_GOOGLE_unique_objects was the first one that complained in my case (I didn't enable any device layer).

View solution in original post

0 Likes
12 Replies