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]

Vulkan Tutorial For a lot of developers wanting to learn Vulkan, the tutorial at www.vulkan-tutorial.com is the first learning resource they’ll encounter. It teaches most of the basics required to get started with Vulkan, but up until now only for the graphics part. But Vulkan does more than graphics, with compute shader support being mandatory and as such available on all devices and platforms that support Vulkan. New compute chapter And being well aware on how important the tutorial is as a learning resource, we have a small group of people inside Khronos that takes care of keeping the tutorial up-to-date and in line with api changes. [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: [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]

New Vulkan version Vulkan 1.3 has just gone public, adding some recent features into the core to establish a new baseline for the api. You can find more information in this blog from Khronos and additional resources in this one. There’ll also be a special Vulkanized webinar on February 1st that’s dedicated to the new version. As with previous releases I added support for the new core version to the Vulkan Hardware Capability Viewer and the database day-one. [Read More]

New OpenCL Hardware Database 2022 starts off with a new addition to my GPU Hardware databases at GPUInfo.org! With the databases for Vulkan, OpenGL and OpenGL ES being widely used by many graphics developers, ISVs and IHVs, members of the OpenCL working group approached me for a similar database for OpenCL. OpenCL is a mature and widely adopted api for parallel programming of heterogeneous systems, available on all kinds of platforms. [Read More]