Skip to content

Latest commit

 

History

History
68 lines (55 loc) · 2.37 KB

ns-dxgiddi-dxgi_ddi_multiplane_overlay_caps.md

File metadata and controls

68 lines (55 loc) · 2.37 KB
Raw
UID title description old-location tech.root ms.date keywords ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames f1_keywords topic_type api_type api_location api_name
NS:dxgiddi.DXGI_DDI_MULTIPLANE_OVERLAY_CAPS
DXGI_DDI_MULTIPLANE_OVERLAY_CAPS (dxgiddi.h)
The DXGI_DDI_MULTIPLANE_OVERLAY_CAPS structure contains information that is used by the user-mode display driver to specify overlay plane capabilities.
display\dxgi_ddi_multiplane_overlay_caps.htm
display
05/10/2018
DXGI_DDI_MULTIPLANE_OVERLAY_CAPS structure
DXGI_DDI_MULTIPLANE_OVERLAY_CAPS, DXGI_DDI_MULTIPLANE_OVERLAY_CAPS structure [Display Devices], display.dxgi_ddi_multiplane_overlay_caps, dxgiddi/DXGI_DDI_MULTIPLANE_OVERLAY_CAPS
dxgiddi.h
D3d10umddi.h
Windows
Windows 8.1
Windows Server 2012 R2
Windows
DXGI_DDI_MULTIPLANE_OVERLAY_CAPS
DXGI_DDI_MULTIPLANE_OVERLAY_CAPS
dxgiddi/DXGI_DDI_MULTIPLANE_OVERLAY_CAPS
APIRef
kbSyntax
HeaderDef
Dxgiddi.h
DXGI_DDI_MULTIPLANE_OVERLAY_CAPS

DXGI_DDI_MULTIPLANE_OVERLAY_CAPS structure

-description

Used by the user-mode display driver to specify overlay plane capabilities.

-struct-fields

-field MaxPlanes

The maximum number of inputs, including the primary surface, to the display hardware that can be supported in the current mode. This value can change if the mode changes.

For example, if the hardware allows one overlay plane and one normal primary surface, the driver should set MaxPlanes to 2.

-field NumCapabilityGroups

The number of different types of overlay planes that can be supported.

Here are 2 examples:

  • If the hardware supports 2 RGB-only planes with limited stretching capabilities, plus 2 YUV planes with more flexible stretching capabilities, then the driver should set NumCapabilityGroups to 2.
  • If the hardware supports one RGB-only plane with no stretching capabilities, plus 2 RGB-only planes with full stretching capabilities, plus 2 RGB/YUV planes with full stretching capabilities, then the driver should set NumCapabilityGroups to 3.