Vulkan API Support

Vulkan

This page details the current Vulkan support within RenderDoc, which features are implemented and any caveats or details you need to know about.

Note: RenderDoc technically works on Linux as well as Windows, but the Linux UI (written in Qt) is not functional and still in need of a lot of work to bring it up to equal with the Windows UI. OS X support is in theory not far behind Linux, but is not yet implemented.

Version support

RenderDoc supports Vulkan 1.0 and any core extensions (such as the WSI extensions). Support for vendor-specific extensions will happen on a case-by-case basis, but in general won't be supported unless trivial. Multi-vendor extensions will likely be supported unless the cost-benefit is prohibitive.

Current status

• RenderDoc assumes that API use is valid and defined, according to the definition of the spec. Similar to how drivers have only minimal built-in error checking, so does RenderDoc.
• At the moment RenderDoc only supports a single VkDevice and VkQueue per VkInstance, and likewise multiple VkInstances in a single program is untested.
• Given the above, RenderDoc also doesn't support sharing and transfering ownership of resources between different queues
• RenderDoc captures are not currently portable between machines unless their hardware/driver configuration is almost identical.
• When using sparse textures, only 2D images without array slices or mips are supported

To do

• Shader debugging
• Pixel history
• Geometry/tessellation shader output display in the mesh output pane