sdfteh
February 15, 2017, 3:23pm
1
Vulkan SDK cube example not working
I use GeForce GTX 760, Win 10 x64, 378.66 version of driver
chopper exe dont found physical device count
===========
VULKAN INFO
Vulkan API Version: 1.0.39
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_api_dump.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_core_validation.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_image.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_monitor.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_object_tracker.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_parameter_validation.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_screenshot.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_swapchain.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_threading.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_unique_objects.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_vktrace_layer.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\Windows\system32\nv-vk64.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\Program Files\RenderDoc\renderdoc.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file D:\Programs\Steam\SteamOverlayVulkanLayer64.json, version “1.0.0”
INFO: [loader] Code 0 : Found ICD manifest file C:\Windows\system32\nv-vk64.json, version “1.0.0”
INFO: [loader] Code 0 : Insert instance layer VK_LAYER_NV_optimus (C:\Windows\system32.\nvoglv64.dll)
Instance Extensions:
Instance Extensions count = 8
VK_KHR_surface : extension revision 25
VK_KHR_win32_surface : extension revision 5
VK_EXT_debug_report : extension revision 4
VK_NV_external_memory_capabilities : extension revision 1
VK_KHR_get_physical_device_properties2: extension revision 1
VK_KHX_external_memory_capabilities : extension revision 1
VK_KHX_external_semaphore_capabilities: extension revision 1
VK_EXT_display_surface_counter : extension revision 1
C:\doppelbuild\RuntimeLVL\demos\vulkaninfo.c:1492: failed with VK_ERROR_INITIALIZATION_FAILED
sdfteh
February 15, 2017, 3:47pm
2
after reinstal
===========
VULKAN INFO
Vulkan API Version: 1.0.39
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_api_dump.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_core_validation.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_image.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_monitor.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_object_tracker.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_parameter_validation.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_screenshot.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_swapchain.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_threading.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_unique_objects.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\VulkanSDK\1.0.39.1\Bin\VkLayer_vktrace_layer.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\Windows\system32\nv-vk64.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file C:\Program Files\RenderDoc\renderdoc.json, version “1.0.0”
INFO: [loader] Code 0 : Found manifest file D:\Programs\Steam\SteamOverlayVulkanLayer64.json, version “1.0.0”
INFO: [loader] Code 0 : Found ICD manifest file C:\Windows\system32\nv-vk64.json, version “1.0.0”
INFO: [loader] Code 0 : Insert instance layer VK_LAYER_NV_optimus (C:\Windows\system32.\nvoglv64.dll)
Instance Extensions:
Instance Extensions count = 5
VK_KHR_surface : extension revision 25
VK_KHR_win32_surface : extension revision 5
VK_EXT_debug_report : extension revision 3
VK_NV_external_memory_capabilities : extension revision 1
VK_KHR_get_physical_device_properties2: extension revision 1
C:\doppelbuild\RuntimeLVL\demos\vulkaninfo.c:1492: failed with VK_ERROR_INITIALIZATION_FAILED
qgu
February 17, 2017, 11:41pm
3
sdfteh,
We had also filed an internal bug to track this problem. Thanks for reporting the issue.
Did you get the same issue when running other Vulkan application?
sdfteh
February 18, 2017, 11:55am
4
qgu,
Other games not working at all.
They immediately turned off or saying that something wrong with vulkan support.
I tried other versions of driver but there is the same problem.
sdfteh
February 18, 2017, 12:07pm
5
qgu,
May be this can help you with additional information Dropbox - File Deleted
This is Vulkan Installation Analyzer (VIA) which comes in the LunarG SDK
qgu
February 21, 2017, 7:10pm
6
sdfteh,
Could you specify your OS location? is it installed on Drive C: or other non-default drive?
Also, in order to understand if this is a driver regression or system specific issue, we need to know how do you install the driver and if you ever get any previous driver working with Vulkan after a clean driver re-installation.
qgu
February 21, 2017, 7:20pm
7
sdfteh,
More details of your system hardware could also help us isolate the problem. thanks.
sdfteh
February 25, 2017, 8:06pm
8
qgu,
1)on C: clean install about 2 month ago
2)i try to install from site and from geforce experience
3)no
sdfteh
March 10, 2017, 2:14pm
9
qgu,
So what I need to do to fix this problem?
qgu
May 6, 2017, 12:52am
10
We had filed an internal bug since 2/127/2017 to track this issue but not be able to fully reproduce the problem so far.
Does it still happen to your system with the latest driver and system installation?