- #DOES THE XENIA EMULATOR WORK WITH AN A10 PROCESSOR DRIVERS#
- #DOES THE XENIA EMULATOR WORK WITH AN A10 PROCESSOR DRIVER#
- #DOES THE XENIA EMULATOR WORK WITH AN A10 PROCESSOR TRIAL#
#DOES THE XENIA EMULATOR WORK WITH AN A10 PROCESSOR DRIVER#
(VK_KHR_surface and VK_KHR_win32_surface did and do exist), pure compute queues 1Īdditionally, on both systems all my three queue families report VK_QUEUE_TRANSFER_BIT (previously with driver 16.4.2 only on one queue family) On Win 10: VK_KHR_swapchain is missing as well. On Win 8.1 VK_KHR_surface and VK_KHR_win32_surface are back, but VK_KHR_swapchain is missing, pure compute queues 7 I installed driver Crimson Edition 16.5.1 Hotfix and the problems have shifted: 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). 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.
#DOES THE XENIA EMULATOR WORK WITH AN A10 PROCESSOR TRIAL#
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.Īnd the solution to the VK_LAYER_GOOGLE_unique_objects issue is: The implementation lists it as available layer, but using it leads to the mentioned VK_ERROR. The issue stems from VK_LAYER_GOOGLE_unique_objects. I thought for a long time that even this driver is wrong, as calling vkCreateSwapchainKHR returned VK_ERROR_INITIALIZATION_FAILED. That is because now it is device extension and works just fine. 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.Īs mentioned above about this driver, instance extension Extension: VK_KHR_swapchain is missing. Update: After some experiments and a lot of web searching I figured that Crimson 16.5.1 Driver Version. Now, on Win 10 the implementation IS still listing 3 Families, but the compute queue exposes only 1 queue.Īctually I rather post a summary of two correct answers: The problem does not exist on there, all four extensions are listed.īUT (!!!) on Win 8 the implementation WAS listing 3 Queue Families, one of them a compute queue family with 4 queues.
#DOES THE XENIA EMULATOR WORK WITH AN A10 PROCESSOR DRIVERS#
Meanwhile I installed Win 10 圆4 as dual boot on the system and updated the drivers to Crimson Edition 16.4.2 Hotfix Win 10 圆4.
I tried that as well, didn't solve the problem either. I must admit that I am not sure if this is a driver bug at all, but what else could it be ?Īs 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. Installing this driver over the current one does not solve the problem.
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. I had four extensions available on my system, VK_KHR_swapchain and VK_EXT_debug_report are still present. I confirmed within my own project that exactly the two mentioned extensions are missing. The LunarG Vulkan Samples exit with a Missing extension error code. Today I installed the Crimson Edition 16.4.2 Hotfix, but the problem remains. I doubt the later one is responsible, I tried all the other SDK versions without success, but who knows. I installed two things before I noticed the issue: The mentioned extensions have disappears suddenly, unfortunately I am not sure why and when.