Hey everyone! Forgive me if this post has been asked before. I tried looking and couldnt find what I needed.
Well I wanted to know if Vulkan is supported for the New Surface Pro 2017?
-Intel Core i7-7660U CPU
-Intel Iris Plus Graphics 640
-According to DirectX Diagnostic Tool I have driver version 126.96.36.19949
I am using Visual Studio 2017. Ive looked around and Ive seen that Vulkan 1.0 only, then up to 1.0.50 and recently up to 1.0.60 version is supported. So I am a bit confused. I get an exception when trying to create the instance with vkCreateInstance. Even the samples are not working. Anyone have any ideas? Am I missing something or is it not supported?
Those versions are interchangeable. The last number is bugfix\clarifications of the Vulkan specification and can change weekly.
The drivers package updates that when it feels like it. It has little bearing on functionality, except it signalls the driver was recently updated and is (hopefully) bit more mature.
Thanks for the reply. Yeah I tried downloading those drivers but it says its unsupported for this system. Just thought that since im in version 22, it didnt like downgrading to 15 or something. Just not sure why it would fail.
I got it to work!! I just uninstalled the graphics driver from Device Manager. Then went into the first link you sent me to download the driver. It actially worked this time which is weird. A bug maybe?!? Well now the driver date is 2/4/2018 which seems better.
Though now the only thing im getting is Access Violation when I call vkCreateGraphicsPipeline that im not getting in my desktop. It succeeds when I create it the first time but when I called it again to create a new one it gives me a violation. Its probably on my side. Will have to dig in deeper on it and see whats going on.
Yes, without it the Vulkan loader would think there is no driver and return VK_ERROR_INCOMPATIBLE_DRIVER
I guess. Though awfully specific one.
Also the new driver is 23.X, so should not really complain about versions. Sometimes the notebook vendor makes some embellishments. Does everything work as before (especially function keys, overlays - e.g. volume meter if there was one, external display port works)?
Those happen. Try Validation Layers.
Sometimes the driver itself does not like some arguments, in which case report it for all our sakes.