New client application

Version 3.40 of the Vulkan Hardware Capability Viewer is now available for all platforms (Windows, Linux, Android, Mac OSX). An update for the Google Play Android version should land soon.

New extensions

This version is based on Vulkan Headers 1.3.280 and adds support for the following new extension features and properties provided via VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2:

• VK_EXT_map_memory_placed
• VK_NV_shader_atomic_float16_vector
• VK_NV_raw_access_chains
• VK_NV_ray_tracing_validation

Other changes

• Made some minor adjustments to the JSON output that should hopefully fix some wrongly reported format feature flags
  • JSON’s number type is limited to double, and some drivers reported numbers larger than that, resulting in wrong values stored to the database
  • To avoid this, those flags are now stored as string, avoiding any problems with conversion
• Updated the LunarG Profiles library

New client application Version 3.33 of the Vulkan Hardware Capability Viewer is now available for all platforms (Windows, Linux, Android, Mac OSX). An update for the Google Play Android version is also pending and should be live soon. New extensions As the last release has been a while ago, this version did a rather large jump to Vulkan Headers 1.3.276 and adds support for a lot of new extension features and properties provided via VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2: [Read More]

New client application Version 3.32 of the Vulkan Hardware Capability Viewer is now available for all platforms (Windows, Linux, Android, Mac OSX). An update for the Google Plays Android version is also pending and should be live soon. New extensions This version has been updated to Vulkan Headers 1.3.264 adding support for reading new features and properties provided via VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2 for the following extensions: VK_KHR_cooperative_matrix VK_EXT_frame_boundary VK_EXT_depth_bias_control VK_EXT_dynamic_rendering_unused_attachments VK_NV_descriptor_pool_overallocation VK_MSFT_layered_driver VK_QCOM_image_processing2 VK_QCOM_filter_cubic_weights VK_QCOM_ycbcr_degamma VK_QCOM_filter_cubic_clamp VK_QNX_external_memory_screen_buffer Other changes Supported image layouts for the VK_EXT_host_image_copy are now properly displayed using their Vulkan enums. [Read More]

New client application Version 3.29 of the Vulkan Hardware Capability Viewer is now available for all platforms (Windows, Linux, Android, Mac OSX). An update for the slightly outdated Google Playstore is also pending and should be live soon. New extensions This version has been updated to Vulkan Headers 1.3.243 adding support for reading new features and properties provided via VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2 for the following extensions: VK_ARM_shader_core_properties VK_EXT_image_sliced_view_of_3d VK_EXT_pipeline_library_group_handles VK_QCOM_multiview_per_view_render_areas Other changes The new version also includes a usability improvement for filtering data. [Read More]

New global surface data listings Being able to filter for all data available from submitted reports is an important aspect of the database, so I’m constantly adding new global listings that also let you check coverage numbers. The surface part of the database was missing two important listings: One for the surface transform modes and one for the surface composite alpha modes. They have been added to the database and quickly let you find out global and per-platform coverage numbers: [Read More]

Comparing devices - Current state A core feature of all my GPU databases (Vulkan, OpenCL, OpenGL and OpenGL ES) is the possibility to compare reports. This lets you quickly see how the implementations differ, e.g. regarding extension support or api limits. For this you check the reports (or devices) to compare from the currently visible list: And after pressing “compare” you’ll get a side-by-side comparison of the selected reports: But the current implementation has an annoying limitation that has been bothering users (and me) for years now: You can only ever select reports (to compare) from the currently visible list of reports. [Read More]

New client application

Version 3.27 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.3.230 adding support for reading new features and properties provided via VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2 for the following extensions:

• VK_EXT_descriptor_buffer (proposal)
• VK_ARM_shader_core_builtins
• VK_NV_copy_memory_indirect
• VK_NV_memory_decompression
• VK_NV_ray_tracing_invocation_reorder

New client application Version 3.26 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.3.230 adding support for reading new features and properties provided via VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2 for the following extensions: VK_EXT_opacity_micromap VK_EXT_extended_dynamic_state3 VK_EXT_device_fault VK_EXT_device_address_binding_report VK_EXT_pipeline_protected_access VK_EXT_legacy_dithering VK_EXT_mutable_descriptor_type VK_EXT_rasterization_order_attachment_access VK_NV_present_barrier VK_NV_optical_flow Changes and bugfixes Updated Vulkan profiles library to the latest version Added detection for Windows 11 (was showing up as Windows 10 in older versions) Fixed a bug with large values for maxTimelineSemaphoreValueDifference Database I also did some minor tweaks and bugfixes to the database: [Read More]

Some background More than 6 years ago (time flies!) I released the Vulkan Hardware Database and Capability Viewer along with the first public release of Vulkan 1.0. Traffic on the database has been rising steadily and is approaching 1,000,000 hits per month. 2021 more than 3,000 reports have been uploaded to the database, a number that also has been steadily increasing since launch. This makes it my mostly used database (compared to OpenGL and OpenGL ES) and judging by the feedback it seems to be a widely and often used feature among Vulkan developers. [Read More]

Vulkan profiles Along with Vulkan 1.3, Khronos also introduced Vulkan Profiles into the Vulkan ecosystem: “The new Vulkan profile mechanism enables the precise specification and management of sets of API capabilities. Each profile specifies a core version of Vulkan plus a set of required extensions, with supported limits, features, and formats. Profiles provide a way to precisely communicate functionality requirements and device capabilities between participants in the Vulkan ecosystem to streamline the development and deployment of portable applications. [Read More]