Crash in TestGuis and TestPhysics on Windows about acid

[Karmel0x]

Looks like my driver did not support vulcan, I thought I had the latest (but my system used the previous one, as if I did not uninstall it ?)
But still same problem, just console output has been changed:

-- Avalable Layers For: 'Instance' --
VK_LAYER_AMD_switchable_graphics, VK_LAYER_RENDERDOC_Capture, VK_LAYER_VALVE_ste
am_overlay, VK_LAYER_LUNARG_standard_validation,
-- Done --
-- Physical Device: 'Intel(R) HD Graphics 520' --
ID: 6422
Type: Integrated
Vendor: Intel
Supports Version: 1.0.31
Header Version: 82
-- Done --
Selected Physical Device: 'Intel(R) HD Graphics 520', 6422

[mattparks]

You need to have the latest driver for Intel (you should see Supports Version have a version like 1.1.X): https://downloadcenter.intel.com/product/88355/Intel-HD-Graphics-520
You might be able to change the API version from (1, 1, 0) to (1, 0, 0) in https://github.com/Equilibrium-Games/Acid/blob/d5e79d0c58d8a36e8a861d63a567fcaaabf48f05/Sources/Display/Display.cpp#L550

[Karmel0x]

Yea, I reinstalled the graphic drivers to the latest version (15.45 for Windows 7).
I also uninstalled vulkan and removed vulkan* files from System32 and SysWOW64, I installed the latest version 1.1.82.1. But 'TestGuis' and my graphic driver still shows version 1.0.31. vulkaninfo.exe shows 1.1.82
Same results after changing the API version from (1, 1, 0) to (1, 0, 0).
After reinstalling I only came back to the error from my first post:

-- Avalable Layers For: 'Instance' --
VK_LAYER_LUNARG_api_dump, VK_LAYER_LUNARG_assistant_layer, VK_LAYER_LUNARG_core_
validation, VK_LAYER_LUNARG_device_simulation, VK_LAYER_LUNARG_monitor, VK_LAYER
_LUNARG_object_tracker, VK_LAYER_LUNARG_parameter_validation, VK_LAYER_LUNARG_sc
reenshot, VK_LAYER_LUNARG_standard_validation, VK_LAYER_GOOGLE_threading, VK_LAY
ER_GOOGLE_unique_objects, VK_LAYER_LUNARG_vktrace, VK_LAYER_VALVE_steam_overlay,

-- Done --
-- Physical Device: 'Intel(R) HD Graphics 520' --
ID: 6422
Type: Integrated
Vendor: Intel
Supports Version: 1.0.31
Header Version: 82
-- Done --
Selected Physical Device: 'Intel(R) HD Graphics 520', 6422
 [ VUID-VkDeviceQueueCreateInfo-queueCount-00382 ] Object: 0x3058520 (Type = 2)
| vkCreateDevice: pCreateInfo->pQueueCreateInfos[0].queueCount (=2) is not less
than or equal to available queue count for this pCreateInfo->pQueueCreateInfos[0
].queueFamilyIndex} (=0) obtained previously from vkGetPhysicalDeviceQueueFamily
Properties (i.e. is not less than or equal to 1). The spec valid usage text stat
es 'queueCount must be less than or equal to the queueCount member of the VkQueu
eFamilyProperties structure, as returned by vkGetPhysicalDeviceQueueFamilyProper
ties in the pQueueFamilyProperties[queueFamilyIndex]' (https://www.khronos.org/r
egistry/vulkan/specs/1.0/html/vkspec.html#VUID-VkDeviceQueueCreateInfo-queueCoun
t-00382)

EDIT: I think it's problem in Acid, I've tested Cube - Demo from KhronosGroup Vulkan-Tools, its working.

[Karmel0x]

Finally, I've got it working, needs to change this variable to 1.
https://github.com/Equilibrium-Games/Acid/blob/d5e79d0c58d8a36e8a861d63a567fcaaabf48f05/Sources/Display/Display.cpp#L798

[mattparks]

Did you only need to change the queueCount to 2, or was the version also set to 1,0,0?

[Karmel0x]

Not need, I set it back to (1, 1, 0)
I had only change the queueCount to 1.

[mattparks]

The commit I just pushed, d02c64a, should fix the queue issue. Acid will now have per-queue VkDeviceQueueCreateInfo structs, and look for multiple usages of families. If this now works for you you can close the issue.