Vulkan check timeout

RonaldM_Intel


Moderator

‎
Hello,



I checked this report with our Vulkan dev team and confirmed that the change of the Vulkan key you are seeing is intentional.



Due to the upcoming https://docs.microsoft.com/en-us/windows...versal-dri... Universal Windows Drivers (UWD) and as per Microsoft's https://docs.microsoft.com/en-us/windows...l-inf-file# which-inf-sections-are-invalid-in-a-universal-inf-file UWD requirements the key was moved from the old location you use in your .reg file to a new one. The name of the key is a bit more complex now, and contains a unique device identifier (distinct for each machine).



The main point is however, that this key is not intended to be used directly by applications. Applications shall access Vulkan API using the Vulkan Loader (aka Vulkan RunTime or VulkanRT) which is distributed with the driver (VulkanRT is an open source component that all graphics vendors are shipping with their drivers. It can be also downloaded by game developers as a part of Vulkan SDK). When changing the registry key used by our driver, we also updated VulkanRT (in a way that it now understands both old and new keys) what ensured that existing games continue to work.



RPCS3 developers do not use the loader distributed with the graphics cards, but chose instead to statically link to a certain version from Vulkan SDK.



I can see in their release notes, that they already solved the issue in their product by using a newer version of that library.



Please note that their approach (static linking) does not guarantee not having similar problems in the future.



I hope this information helps understanding what and why the change. We also wish to thank you for coming up with this work around as it can help many other users.



Best Regards,



Ronald M.

I dunno, might be relevant? Maybe not?