Direct3D 10

Direct3D 10 introduced a fixed set of mandatory requirements for the graphics hardware. Before Direct3D 10, new versions of the API introduced support for new hardware capabilities, however these capabilities were optional and had to be queried with "capability bits" or "caps".

Direct3D 10.1 was the first to use a concept of "feature levels"^[1][3][6] to support both Direct3D 10.0 and 10.1 hardware.^[3][7][8]

Direct3D 11

In Direct3D 11, the concept of feature levels has been further expanded to run on most downlevel hardware including Direct3D 9 cards with WDDM drivers.

There are seven feature levels provided by D3D_FEATURE_LEVEL structure; levels 9_1, 9_2 and 9_3 (collectively known as Direct3D 10 Level 9) re-encapsulate various features of popular Direct3D 9 cards conforming to Shader Model 2.0, while levels 10_0, 10_1, 11_0 and 11_1 refer to respective versions of the Direct3D API.^[1] "10 Level 9" feature levels contain a subset of the Direct3D 10/11 API^[9] and require shaders to be written in HLSL conforming to Shader Model 4.0 4_0_LEVEL_9_x compiler profiles, and not in the actual "shader assembly" language^[10] of Shader Model 1.1/2.0; SM 3.0 (vs_3_0/ps_3_0) has been omitted deliberately in Direct3D 10 Level 9.^[3]

Since Direct3D 11.1 for Windows 8, some mandatory features introduced for level 11_1 are available as optional on levels 10_0, 10_1 and 11_0 - these features can be checked individually via CheckFeatureSupport function^[11] however feature level 11_1 and optional features are not available in Direct3D 11.1 for Windows 7 platform update^[12] because it does not support WDDM 1.2.^[13]

Direct3D 11.2 for Windows 8.1 adds optional mappable buffers and optional tiled resources for levels 11_0 and 11_1; these features require WDDM 1.3 drivers.^[14]

Direct3D 11.3 for Windows 10 requires WDDM 2.0 drivers; it adds more optional features and levels 12_0 and 12_1 from Direct3D 12.

Direct3D 12

Direct3D 12 requires graphics hardware conforming to feature levels 11_0 and 11_1 which support virtual memory address translations.^[25][26]

There are two new feature levels, 12_0 and 12_1, which include some features that are optional on levels 11_0 and 11_1.^[27] Due to the restructuring of the API, some previously optional features are realigned as baseline on levels 11_0 and 11_1.

Direct3D 12 from Windows 10 Anniversary update (version 1607) includes Shader Model 6.0,^[28] which requires WDDM 2.1 drivers, and new DXIL compiler based on LLVM.^[29] Windows 10 Creators Update versions 1703 and 1709 include Shader Model 6.1 and WDDM 2.2/2.3.

Direct3D 12 introduces a revamped resource binding model, allowing explicit control of memory. Abstract resource "view" objects^[36] which allowed random read/write access are now represented by resource descriptors, which are allocated using memory heaps and tables.^[37] This model is supported on majority of existing desktop GPU architectures and requires WDDM 2.0 drivers. Supported hardware is divided into three Resource Binding tiers, which define maximum numbers of descriptors that can be used for CBV (constant buffer view), SRV (shader resource view) and UAV (unordered access view); CBVs and SRVs per pipeline stage; UAVs for all pipeline stages; samplers per stage; and the number of SRV descriptor tables. Tier 3 hardware such as AMD GCN and, Intel Skylake has no limitations, allowing fully bindless resources only limited by the size of the descriptor heap, while Tier 1 (Nvidia Fermi, Intel Haswell/Broadwell) and Tier 2 (Nvidia Kepler) hardware impose some limits on the number of descriptors ("views") that can be used simultaneously. Additionally, buffers and textures can mixed together in the same resource heap only on hardware supporting Resource Heap Tier 2, while Tier 1 hardware requires separate memory heaps for buffers, textures, and render-target and depth stencil surfaces. Resource binding tier 1 and resource heap tier 1 are required for all supporting hardware.

Some of the optional features such as tiled resources and conservative rasterization have "tiers" which define the set of supported capabilities.

Most features are optional for all feature levels, but some of these features are promoted to required on higher feature levels.

Support matrix