There are also some manual checks that can be done:
If you have some multi-GPU stuff enabled, disable that (preferrably in BIOS)
Registry HKLM\Software\Khronos\Vulkan\Drivers should have exactly one item. It is path to some json file.
That json file must exist. It is a textfile and should have path to some dll inside it.
That dll also has to exist.
I dont have NVIDIA, but I find the VK_LAYER_NV_optimus implicit layer suspicious. Especially (based on the log) that it seems to point to the OpenGL driver.
Might be worth a shot to try disabling it. You could temporarily remove it from the registry, or there is a special environment variable that disables it (it is listed in the json file).
[QUOTE=krOoze;41855]
I dont have NVIDIA, but I find the VK_LAYER_NV_optimus implicit layer suspicious. Especially (based on the log) that it seems to point to the OpenGL driver.
Might be worth a shot to try disabling it. You could temporarily remove it from the registry, or there is a special environment variable that disables it (it is listed in the json file).[/QUOTE]
all that layer does is switching the order of physical devices based on whether you are on battery or not. preferring the iGPU when on battery and the nvidia card when plugged in.
You should try running the Vulkan Installation Analyzer (VIA) which comes in the LunarG SDK. That will generate a command-line result and an HTML file. If you post both here, it should give us more information. You might have to build it. If you’ve downloaded 1.0.39.1 the information on building it should be in the “Getting Started” document.
[QUOTE=krOoze;41855]Well, you could try older driver.
There are also some manual checks that can be done:
If you have some multi-GPU stuff enabled, disable that (preferrably in BIOS)
Registry HKLM\Software\Khronos\Vulkan\Drivers should have exactly one item. It is path to some json file.
That json file must exist. It is a textfile and should have path to some dll inside it.
That dll also has to exist.
I dont have NVIDIA, but I find the VK_LAYER_NV_optimus implicit layer suspicious. Especially (based on the log) that it seems to point to the OpenGL driver.
Might be worth a shot to try disabling it. You could temporarily remove it from the registry, or there is a special environment variable that disables it (it is listed in the json file).[/QUOTE]
I try 376.80 and it not work
1)dont have
2)yes
3)this is complicated becouse i have 8 nv-vk64.json files but no one plases where regedit says(1 in System32 and regedit says in system32 or 1 in LastGood/system32 but regedit dont says about lastgood do they count?
4) look 3)
5) there is 9 and I dont no why in 1 folder 2 json and 3 dll
please say more specifically what i shoud delete in regedit or disable and whow
Updated - - -
Please say whow can i build becouse I cant find it even in getting started
ad 3) Shouldn’t matter. Windows paths should not be case sensitive.
I don’t understand what you mean by 5)
That was only to check. I did not ask you to delete anything.
Well, I am out of ideas. I suppose it is up to NVIDIA to fix their stuff.
Just for kicks you could also try vulkaninfo32 if it has the same problem.
We could try manual clean (nuke) reinstall, but I would not hold much hope…
Looking at your VIA.html, the loader is finding everything appropriately, but the vkEnumeratePhysicalDevices appears to be returning an error. The only other time I’ve seen this is when the driver (ICD) has an issue. The two cases I’ve seen are:
[ol]
[li]The ICD determines that the hardware really doesn’t support Vulkan[/li][li]There’s a bug in the ICD[/li][/ol]
You’re best bet is to work with Nvidia at this point. Pass along the VIA.html to whatever bug you file to help reduce the initial back and forth.
Based on the log you only have the SDK RT. Try to uninstall: driver, SDK, Renderdoc, any and all Vulkan RTs. Then install only the NVIDIA driver for now and test vulkaninfo. I think it should install 1.0.37 Vulkan RT as part of it.