01-10-2018, 04:07 PM -
(01-10-2018, 09:01 AM)Ravi Wrote: Did as here recommended did not help. He rolled back to 388.84 volcano on the list appeared. in the registry in the branch "HKEY_LOCAL_MACHINE \ SOFTWARE \ Khronos \ Vulkan \ Drivers" there was a record REG_DWORD "C: \ WINDOWS \ system32 \ nv-vk64.json"
sorry googletranslate
Normally when you install Vulkan run times, it copies "nv-vk64.json" and "nvoglv64.dll" (I can't check the name of this one from here) and the 32 bit versions to "/Windows/system32/" and then sets the registry in "HKEY_LOCAL_MACHINE \ SOFTWARE \ Khronos \ Vulkan \ Drivers" to have a dword named as the path to the json file.
While there is this problem with installing Vulkan, it's sufficient, rather than manually copying files to system32, just to point to the json in the driverstore folder in "HKEY_LOCAL_MACHINE \ SOFTWARE \ Khronos \ Vulkan \ Drivers". The json points to the folder it is stored in for the required dll files, and the correct files are beside it in the driverstore.
But in case there is variation in the folder in the driverstore, check in "/windows/system32/driverstore /" for the location of the json file in the newest driver folder,and confirm its in the registry.
Oh but after setting the location in registry, you need to reboot or run vulkaninfo.exe which is in a sub folder in "/program files (x86)/Vulkan RT/".
Them Vulkan should correctly appear in RPCS3.