RPCS3 Forums

Full Version: Vulkan Renderer missing on NVIDIA driver version 390.65 [Fix found]
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4
Hi I just currently downloaded the Rpcs3 emulator. I cant seem to find the Vulkan option no matter what I try. I have downloaded the drivers and everything and still nothing.
Hi,

I have downloaded the new Version and saw that Vulkan as Option is missing.

What happened?

Greetings
(01-12-2018, 04:08 PM)RPCS3_FAN Wrote: [ -> ]Hi,

I have downloaded the new Version and saw that Vulkan as Option is missing.

What happened?

Greetings

I just downloaded the latest version and I have it, so chance are, you need to apply this "fix":

https://forums.rpcs3.net/thread-197673-p...#pid294435

If you have Intel, follow my instructions, if you Nvidia, follow Ani's instructions.

If by some chance you have AMD, then you need to apply the same procedure, but you need to find the folder where the json file for AMD is stored.
This is exactly worked for me. Thanks.
GeForce 390.65 installed, followed Ani's instructions with Regedit and also the vulkaninfo.exe.
Doesn't work, while Dolphin still offers Vulkan.
Any idea???
(01-13-2018, 11:30 AM)albundy Wrote: [ -> ]GeForce 390.65 installed, followed Ani's instructions with Regedit and also the vulkaninfo.exe.
Doesn't work, while Dolphin still offers Vulkan.
Any idea???

Did you follow Ani's steps to the letter, or did you use your own path?

If you followed Ani's, then it could be the path to the file is wrong.
When you run vulkaninfo.exe, does it says "loaderGetDeviceRegistryEntry: Located json file..." at one of the lines at the start?
(01-13-2018, 01:27 PM)Otakon7 Wrote: [ -> ]
(01-13-2018, 11:30 AM)albundy Wrote: [ -> ]GeForce 390.65 installed, followed Ani's instructions with Regedit and also the vulkaninfo.exe.
Doesn't work, while Dolphin still offers Vulkan.
Any idea???

Did you follow Ani's steps to the letter, or did you use your own path?

If you followed Ani's, then it could be the path to the file is wrong.
When you run vulkaninfo.exe, does it says "loaderGetDeviceRegistryEntry: Located json file..." at one of the lines at the start?

Thanks for your advice! Yes i used the letter version.
Now I found that i have 2 versions of Vulkan.
One is 1.0.3.0 with the first 29 lines of vulkaninfo:
===========
VULKAN INFO
===========

Vulkan API Version: 1.0.3

INFO: [loader] Code 0 : loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1292&SUBSYS_380917AA&REV_A1\4&22495785&0&0008
INFO: [loader] Code 0 : loaderGetDeviceRegistryEntry: Device ID(1) Does not contain a value for "VulkanExplicitLayers"
INFO: [loader] Code 0 : loaderGetRegistryFiles: unable to open child-device error:13
INFO: [loader] Code 0 : loaderGetRegistryFiles: opening device PCI\VEN_8086&DEV_0416&SUBSYS_380917AA&REV_06\3&11583659&0&10
INFO: [loader] Code 0 : loaderGetDeviceRegistryEntry: Device ID(2) Does not contain a value for "VulkanExplicitLayers"
INFO: [loader] Code 0 : loaderGetRegistryFiles: Opening child device 3 - DISPLAY\CMO1726\4&399B6406&0&UID265988
WARNING: [loader] Code 0 : loader_get_manifest_files: Registry lookup failed to get layer manifest files.
INFO: [loader] Code 0 : loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1292&SUBSYS_380917AA&REV_A1\4&22495785&0&0008
INFO: [loader] Code 0 : loaderGetDeviceRegistryEntry: Located json file "C:\WINDOWS\System32\DriverStore\FileRepository\nvlti.inf_amd64_3e0ccd5eb9f5a1e6\nv-vk64.json" from PnP registry: VulkanImplicitLayers
INFO: [loader] Code 0 : loaderGetRegistryFiles: opening device PCI\VEN_8086&DEV_0416&SUBSYS_380917AA&REV_06\3&11583659&0&10
INFO: [loader] Code 0 : loaderGetDeviceRegistryEntry: Device ID(2) Does not contain a value for "VulkanImplicitLayers"
INFO: [loader] Code 0 : loaderGetRegistryFiles: Opening child device 3 - DISPLAY\CMO1726\4&399B6406&0&UID265988
INFO: [loader] Code 0 : Found manifest file C:\WINDOWS\System32\DriverStore\FileRepository\nvlti.inf_amd64_3e0ccd5eb9f5a1e6\nv-vk64.json, version "1.0.0"
INFO: [loader] Code 0 : Meta-layer VK_LAYER_LUNARG_standard_validation all 0 component layers appear to be valid.
INFO: [loader] Code 0 : loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1292&SUBSYS_380917AA&REV_A1\4&22495785&0&0008
INFO: [loader] Code 0 : loaderGetDeviceRegistryEntry: Located json file "C:\WINDOWS\System32\DriverStore\FileRepository\nvlti.inf_amd64_3e0ccd5eb9f5a1e6\nv-vk64.json" from PnP registry: VulkanDriverName
INFO: [loader] Code 0 : loaderGetRegistryFiles: opening device PCI\VEN_8086&DEV_0416&SUBSYS_380917AA&REV_06\3&11583659&0&10
INFO: [loader] Code 0 : loaderGetDeviceRegistryEntry: Device ID(2) Does not contain a value for "VulkanDriverName"
INFO: [loader] Code 0 : loaderGetRegistryFiles: Opening child device 3 - DISPLAY\CMO1726\4&399B6406&0&UID265988
INFO: [loader] Code 0 : Located json file "C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nv-vk64.json" from registry "HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\Drivers"
INFO: [loader] Code 0 : Found ICD manifest file C:\WINDOWS\System32\DriverStore\FileRepository\nvlti.inf_amd64_3e0ccd5eb9f5a1e6\nv-vk64.json, version "1.0.0"
ERROR: [loader] Code 0 : loader_get_json: Failed to open JSON file C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nv-vk64.json
INFO: [loader] Code 0 : Insert instance layer VK_LAYER_NV_optimus (C:\WINDOWS\System32\DriverStore\FileRepository\nvlti.inf_amd64_3e0ccd5eb9f5a1e6\.\nvoglv64.dll)


The other version is 10.0.65.0 and the first 23 lines of vulkaninfo are:
===========
VULKAN INFO
===========

Vulkan API Version: 1.0.65

WARNING: [loader] Code 0 : loader_get_manifest_files: Registry lookup failed to get layer manifest files.
ERROR: [loader] Code 0 : loader_get_json: Failed to open JSON file C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nv-vk64.json

Instance Extensions:
====================
Instance Extensions count = 11
VK_EXT_debug_report                 : extension revision  9
VK_EXT_display_surface_counter      : extension revision  1
VK_KHR_get_physical_device_properties2: extension revision  1
VK_KHR_get_surface_capabilities2    : extension revision  1
VK_KHR_surface                      : extension revision 25
VK_KHR_win32_surface                : extension revision  6
VK_KHX_device_group_creation        : extension revision  1
VK_KHR_external_fence_capabilities  : extension revision  1
VK_KHR_external_memory_capabilities : extension revision  1
VK_KHR_external_semaphore_capabilities: extension revision  1
VK_NV_external_memory_capabilities  : extension revision  1

I'll try to understand what you mean and will search on.
But i'm always full of thanks for other ideas.

(Sorry for my post, its my first membership  in a forum and english is my second foreign language) :-(
@"albundy" Ah, I see, I will try to keep it simple then.

So here are the steps you need to follow:

1. Check what is the latest version of Vulkan you have
- Path should be at "C:\Program Files (x86)\VulkanRT\", open the folder with the latest date (that is, highest version number) and run vulkaninfo.exe
- I assume this is the 10.0.65.0 from above, so that's done.

2. Go to "C:\Windows\System32\DriverStore\FileRepository\" and look for folders starting with "nv_dispi.inf_amd64_"
- Open the folder with the latest date (should be the date when you installed the drivers, but just pick the latest one)
- Find the "nv-vk64.json" file and copy the path to it
- Path will look like this: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_xxxxxxxx\nv-vk64.json, where xxxxxxxx is the random text in the folder name

3. In registery editor (regedit), go to "HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\Drivers"
- Right click on the "Drivers" folder and select "New > DWORD (32 bit) Value" and paste the path to nv-vk64.json you got earlier (make sure there are no quotes) as the name
- The value should be 0 by default, but if not, double click the new entry and set value to 0

4. Run the vulkaninfo.exe from the latest version again
- it should say that it loaded the json file from registry, even if not, try looking if RPCS3 can load it


If this doesn't help, then somebody else needs to help.
(01-13-2018, 02:24 PM)Otakon7 Wrote: [ -> ]@"albundy" Ah, I see, I will try to keep it simple then.

So here are the steps you need to follow:

1. Check what is the latest version of Vulkan you have
- Path should be at "C:\Program Files (x86)\VulkanRT\", open the folder with the latest date (that is, highest version number) and run vulkaninfo.exe
- I assume this is the 10.0.65.0 from above, so that's done.

2. Go to "C:\Windows\System32\DriverStore\FileRepository\" and look for folders starting with "nv_dispi.inf_amd64_"
- Open the folder with the latest date (should be the date when you installed the drivers, but just pick the latest one)
- Find the "nv-vk64.json" file and copy the path to it
- Path will look like this: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_xxxxxxxx\nv-vk64.json, where xxxxxxxx is the random text in the folder name

3. In registery editor (regedit), go to  "HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\Drivers"
- Right click on the "Drivers" folder and select "New > DWORD (32 bit) Value" and paste the path to nv-vk64.json you got earlier (make sure there are no quotes) as the name
- The value should be 0 by default, but if not, double click the new entry and set value to 0

4. Run the vulkaninfo.exe from the latest version again
- it should say that it loaded the json file from registry, even if not, try looking if RPCS3 can load it


If this doesn't help, then somebody else needs to help.

Thank you very much. Searching for the json-File and changing the registry works.
Vulkan is running again!!!
(01-13-2018, 03:07 PM)albundy Wrote: [ -> ]Thank you very much. Searching for the json-File and changing the registry works.
Vulkan is running again!!!

Glad I helped, enjoy Smile
Pages: 1 2 3 4