(12-21-2017, 01:11 AM)Alcatraz Wrote: [ -> ]
its of updating Windows
im reinstall a old win 10 versión and it the vulkan option apears... and with a old Intel hd diver
wtf
i dont know why but when I updated to the falls creators update the vulkan option disappeared
of couse (afterwards) im upadate the Intel hd direvers but nothing
i5 7400 - hd 630
Windows version have nothing to do, at least not on HD530, I've updated to Falls Creators as soon as it was available and I still had the Vulkan option. It's all about the drivers. If I install the drivers version 22.20.16.4815 it works (i5 6600k - HD530).
Weird, I checked a couple of months ago and the recent driver updates were all Windows 10 only. Seems like they released a Windows 7 update last month.
(12-21-2017, 04:41 AM)M1hai Wrote: [ -> ] (12-21-2017, 01:11 AM)Alcatraz Wrote: [ -> ]
its of updating Windows
im reinstall a old win 10 versión and it the vulkan option apears... and with a old Intel hd diver
wtf
i dont know why but when I updated to the falls creators update the vulkan option disappeared
of couse (afterwards) im upadate the Intel hd direvers but nothing
i5 7400 - hd 630
Windows version have nothing to do, at least not on HD530, I've updated to Falls Creators as soon as it was available and I still had the Vulkan option. It's all about the drivers. If I install the drivers version 22.20.16.4815 it works (i5 6600k - HD530).
Windows does in fact update your drivers (with or without your consent) tho it does so from it's own list of drivers, which are not always the latest compared to the ones found Intel's site.
For example, about a week ago, I got notifications about updates, and saw that Intel HD drivers were on the list despite me hiding the drivers updates before, so I had to hide them again.
But yes, I too have 22.20.16.4815 (latest one is 4877, but that one doesn't list Vulkan so had to rollback) and it works.
Hello, Happy New Year!
So, Intel issued a new driver 4901, but sadly, nothing has been fixed.
Now, one thing I did notice was that the Intel HD panel lists Vulkan 1.0.62 as the active version, but the version installed is 1.0.61.1.
To it is possilbe that's what is confusing RPCS3.
Is there a way to "point" RPCS3 to a Vulkan driver manually?
OR, if somebody knows to manually edit the Intel config?
Either, hoping for feedback on this.
(01-01-2018, 12:56 PM)Otakon7 Wrote: [ -> ]Hello, Happy New Year!
So, Intel issued a new driver 4901, but sadly, nothing has been fixed.
Now, one thing I did notice was that the Intel HD panel lists Vulkan 1.0.62 as the active version, but the version installed is 1.0.61.1.
To it is possilbe that's what is confusing RPCS3.
Is there a way to "point" RPCS3 to a Vulkan driver manually?
OR, if somebody knows to manually edit the Intel config?
Either, hoping for feedback on this.
In fact, if you go to the VulkanRT folder and click on "vulkaninfo.exe" you'll find this:
Quote:Vulkan API version: 1.0.61
.... info ....
scroll down a few lines
.... info ....
Device Properties and Extensions :
==================================
GPU0
VkPhysicalDeviceProperties:
===========================
apiVersion = 0x40003e (1.0.62)
driverVersion = 65538 (0x10002)
vendorID = 0x8086
deviceID = 0x1912
deviceType = INTEGRATED_GPU
deviceName = Intel® HD Graphics 530 ((This is in my case, I5 6600K))
@M1hai: Oh, I have a 6600, so that's basically the same.
Does Vulkan show up for you on RPCS3?
Anyway, have the same info as you, have a bunch of Loader warnings at the start tho.
Have not figured out how RPCS3 checks whether or not Vulkan is valid, seems to be tied to the VK libraries which do their own thing. Hmm, last C++ dist I have is 2015; wonder if having 2017 would help in any way.
(01-01-2018, 06:00 PM)Otakon7 Wrote: [ -> ]@M1hai: Oh, I have a 6600, so that's basically the same.
Does Vulkan show up for you on RPCS3?
Anyway, have the same info as you, have a bunch of Loader warnings at the start tho.
Have not figured out how RPCS3 checks whether or not Vulkan is valid, seems to be tied to the VK libraries which do their own thing. Hmm, last C++ dist I have is 2015; wonder if having 2017 would help in any way.
Vulkan doesn't show on mine neither with this new version of the drivers + newest RPCS3
(01-01-2018, 06:07 PM)M1hai Wrote: [ -> ] (01-01-2018, 06:00 PM)Otakon7 Wrote: [ -> ]@M1hai: Oh, I have a 6600, so that's basically the same.
Does Vulkan show up for you on RPCS3?
Anyway, have the same info as you, have a bunch of Loader warnings at the start tho.
Have not figured out how RPCS3 checks whether or not Vulkan is valid, seems to be tied to the VK libraries which do their own thing. Hmm, last C++ dist I have is 2015; wonder if having 2017 would help in any way.
Vulkan doesn't show on mine neither with this new version of the drivers + newest RPCS3
Yeah, seems like Intel changed how Vulkan is handled and RPCS3 can't pick it up using it's standard functions :/
Installing the SDK alone doesn't do anything sadly.
Well, guess it's back to 4815 until it's resolved.
I'd hate to buy a physical GPU given the iGPU is more then enough for the games I play, but if all else fails, guess I'll get myself a RX 550
FOUND A FIX!
Thank Ani:
https://forums.rpcs3.net/thread-197839-p...#pid294395
(01-09-2018, 07:05 PM)Ani Wrote: [ -> ]Known issue with latest NVIDIA drivers.
Under "HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\Drivers", create a new REG_DWORD, name it "C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nv-vk64.json", and put the value as 0.
You have to do the same thing with Intel drivers.
So, here is what I did:
I created a REG_DWORD in the same location, but the path to my intel Driver was:
"Y:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_daa5fd44d52a5762\igvk64.json"
That's the 4901 drivers, yours might be different, but in short, you're looking for folders starting with "gdlh64.inf_amd64_" inside your "\System32\DriverStore\FileRepository", just find the one with the latest date and that should be the one you're looking for.
You might need to run vulkaninfo.exe for Vulkan to appear on RPCS3 first (located under "\Program Files (x86)\VulkanRT" in the version folder you use)
P.S. Don't mind me having Windows on the Y drive, it's a joke; when people ask me "Why", I say "Y indeed"
(01-10-2018, 09:32 PM)Otakon7 Wrote: [ -> ]FOUND A FIX!
Thank Ani:
https://forums.rpcs3.net/thread-197839-p...#pid294395
(01-09-2018, 07:05 PM)Ani Wrote: [ -> ]Known issue with latest NVIDIA drivers.
Under "HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\Drivers", create a new REG_DWORD, name it "C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nv-vk64.json", and put the value as 0.
You have to do the same thing with Intel drivers.
So, here is what I did:
I created a REG_DWORD in the same location, but the path to my intel Driver was:
"Y:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_daa5fd44d52a5762\igvk64.json"
That's the 4901 drivers, yours might be different, but in short, you're looking for folders starting with "gdlh64.inf_amd64_" inside your "\System32\DriverStore\FileRepository", just find the one with the latest date and that should be the one you're looking for.
You might need to run vulkaninfo.exe for Vulkan to appear on RPCS3 first (located under "\Program Files (x86)\VulkanRT" in the version folder you use)
P.S. Don't mind me having Windows on the Y drive, it's a joke; when people ask me "Why", I say "Y indeed"
Yeah! It's working
I tried it too when I've seen the solution in the NVidia post, but couldn't find igvk64.json xD well, now it's working, thank you both so much