Vulkan Hardware Capability Viewer 3.02 released

Release

Version 3.02 of the Vulkan Hardware Capability Viewer is now available for all platforms (Windows, Linux, Android, Mac OSX).

New extensions

This version has been updated to Vulkan Headers 1.2.184 (from 1.2.175), adding support for reading new features and properties provided via VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2 for the following extensions:

  • VK_EXT_physical_device_drm
  • VK_EXT_multi_draw
  • VK_EXT_global_priority_query
  • VK_KHR_shader_subgroup_uniform_control_flow
  • VK_HUAWEI_subpass_shading
  • VK_NV_ray_tracing_motion_blur
  • VK_NV_external_memory_rdma
  • VK_EXT_provoking_vertex
  • VK_EXT_extended_dynamic_state2

Queue family presentation support on Linux

This version also fixes a long-standing issue with presentation support on Linux always getting reported as false. I have reworked the code for queue family presentation support to use vkGetPhysicalDeviceSurfaceSupportKHR on all platforms. This also works on Linux, so all reports uploaded with this version (and newer) will finally report proper presentation support on Linux.

32 bit builds for Windows

Upon request there is now also a 32 bit Windows build available. Some implementations won’t expose certain features on 32 bit operating systems. So with this build, people can easily can check how 32 bit implementations differ. One such example are the ray tracing extensions, that aren’t exposed under 32 bit on some implementations.

Report uploads no longer require file access

Uploading reports has been reworked and no longer needs to temporarily store reports to disk before submitting them to the database. This was an issue on Mac OSX, where certain security features of the operating system would not let the application store the reports to disk, thus trying to upload empty reports. This is now completely handled in memory with no file access.

Filtering on nested values

As a small usability improvement, all listings now also filter on nested values. Up until now, filtering only worked on the first level of data presented in the tree views.