Vulkan check timeout

terminal command results:

WARNING: [Loader Message] Code 0 : ReadDataFilesInRegistry: Registry lookup failed to get layer manifest files.
WARNING: [Loader Message] Code 0 : loader_icd_scan: ICD JSON C:\WINDOWS\System32\amd-vulkan64.json does not have an "api_version" field.

Same problem here.
Just clean reformatted my pc with complete drivers and all. RPCS3 is still fine after that.
Then the next day RPCS3 doesn't work anymore.

I also get this error "Vulkan Check Timeout"
FYI: I can play Rainbow six siege using vulkan, and all other emulators installed are working fine except RPCS3
I just wanted to play my favorite Tales of Graces and persona 5...

R5 2600
RX580 driver 20.9.1
16gb Ram
Win10x64

sorry have to revive the old thread. but i got the same random error like this. ive uninstall every display driver (including chipset and soundcard), but rpcs3 randomly popping up this error.
the only work around is to restart rpcs3, if it still fail, then restart your PC

configuration:
GTX1660 (latest drvier)
Ryzen 5 3600
motherboard B550
16GB RAM

Same problem here.
Just clean reformatted my pc with complete drivers and all. RPCS3 is still fine after that.
Then the next day RPCS3 doesn't work anymore.

I also get this error  "Vulkan Check Timeout"
FYI: I can play Rainbow six siege using vulkan, and all other emulators installed are working fine except RPCS3
I just wanted to play my favorite Tales of Graces and persona 5...

R5 2600
RX580 driver 20.9.1
16gb Ram
Win10x64

I am having this exact same issue, after a clean reformat it works fine, but after a couple of days it just doesn't work. Can also use vulkan with other emulators and games with no issues.

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?

We haven't statically linked to Vulkan for ages. That post must be 2 years old if not more.

Edit:
I found where that comes from - https://community.intel.com/t5/Graphics/...d-p/592011
It's not 2 years old, it's 3 years old.

We haven't statically linked to Vulkan for ages. That post must be 2 years old if not more.

Edit:
I found where that comes from - https://community.intel.com/t5/Graphics/...d-p/592011
It's not 2 years old, it's 3 years old.

So is the issue. As you can see, others are still encountering it. Sorry just thought that would have been more pertinent.

The issue is not our bug anymore since it is caused by broken driver install, a side effect of loading Vulkan dynamically the correct way.