Updates to the Vulkan Hardware database and the Hardware Capability Viewer

I have released a small update of the Vulkan Hardware Capability Viewer to 1.91 for Windows and Linux. It adds support for reading the features of the recently added VK_EXT_transform_feedback extension and replaces the experimental VK_NVX_raytracing extension with VK_NV_ray_tracing. You can download the new version from https://vulkan.gpuinfo.org/download.php. New features for the online Hardware Database The online hardware database at https://vulkan.gpuinfo.org also got a few new features and now also has dedicated listings and pages for properties and features that are specific to extension. [Read More]

Vulkan Hardware Capability Viewer 1.9 released

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

This version fully supports Vulkan 1.1 and adds support for reading additional features and properties for the following extensions:

  • VK_KHR_driver_properties
  • VK_KHR_shader_atomic_int64
  • VK_NVX_raytracing
  • VK_NV_mesh_shader
  • VK_NV_shading_rate_image
  • VK_NV_compute_shader_derivatives
  • VK_AMD_shader_core_properties

You can download the new version from https://vulkan.gpuinfo.org/download.php.

Vulkan Hardware Capability Viewer 1.8 released

Version 1.8 of the Vulkan Hardware Capability Viewer is now available for all platforms (Windows, Linux, Android). As with 1.8 this version fully supports Vulkan 1.1 and adds support for new extensions: VK_EXT_inline_uniform_block VK_KHR_vulkan_memory_model VK_EXT_vertex_attribute_divisor The UI has also been slightly updated. Instead of listing extension features and properties on a separate tab, these are now included in the extensions tab: You can download the new version from https://vulkan. [Read More]

Vulkan conditional rendering

Introduction Note: Source code that demonstrates this feature can be found in this new example at my open source C++ Vulkan examples repository. With the new VK_EXT_conditional_rendering extension, Vulkan gains the possibility to execute certain rendering and dispatch commands conditionally, based on values stored in a dedicated buffer. So instead of having to rebuild command buffers if the visibility of objects change, it’s now to possible to just change a single buffer value to control if the rendering commands for that object are executed without the need to touch any command buffers. [Read More]

Vulkan input attachments and sub passes

Introduction I have added a new example to my open source C++ Vulkan examples that demonstrates the use of input attachments and subpasses within a single render pass. Input attachments are image views that can be used for pixel local load operations inside a fragment shader. This basically means that framebuffer attachments written in one subpass can be read from at the exact same pixel (that they have been written) in subsequent subpasses. [Read More]

Multiview rendering in Vulkan using VK_KHR_multiview

I have added a new example to my open source C++ Vulkan examples that demonstrates the use of multiview rendering. Multiview enables rendering to multiple views simultaneously instead of having to use multiple passes. Esp. with stereoscopic rendering (e.g. for VR related applications) there’s usually little change between two views, like different matrices, and having to do multiple passes for such small differences is inefficient. With multiview an implementation can now render different views simultaneously in a single pass and the Vulkan extension even adds hints for the implementation to even further improve performance (see correlation mask down below). [Read More]

OpenGL hardware database overhaul

After reworking the OpenGL ES hardware database some time ago (which was in dire need of an update to be usable again) I have also released a substantial update to the OpenGL hardware database. Server-side processing Biggest change is the use of server-side processing (as with the Vulkan and OpenGL ES databases), so gone are the days where each request to the report listing page would fetch all reports at once, and had the client do the heavy lifting, resulting in a long delay before any filtering or sorting could be done. [Read More]

OpenGL ES database ES 3.1 and 3.2 support, capability listing pages

After the recent overhaul I now also have added support for OpenGL ES 3.1 and 3.2 to the OpenGL ES hardware database and the Android app. Both versions added lots of new capabilities that have been lacking from the client application and database, so even though there are lots of reports for OpenGL ES 3.1 and 3.2 those only contain capabilities up to OpenGL ES 3.0. GLES 3.1 brought compute shaders, GLES 3. [Read More]