PFND3D10DDI_RESOURCERESOLVESUBRESOURCE - NtDoc

Native API online documentation, based on the System Informer (formerly Process Hacker) phnt headers
// d3d10umddi.h

PFND3D10DDI_RESOURCERESOLVESUBRESOURCE Pfnd3d10ddiResourceresolvesubresource;

VOID Pfnd3d10ddiResourceresolvesubresource(
  D3D10DDI_HDEVICE unnamedParam1,
  D3D10DDI_HRESOURCE unnamedParam2,
  UINT unnamedParam3,
  D3D10DDI_HRESOURCE unnamedParam4,
  UINT unnamedParam5,
  DXGI_FORMAT unnamedParam6
)
{...}
View the official Windows Driver Kit DDI reference

NtDoc

No description available.

Windows Driver Kit DDI reference (nc-d3d10umddi-pfnd3d10ddi_resourceresolvesubresource)

PFND3D10DDI_RESOURCERESOLVESUBRESOURCE callback function

Description

The ResourceResolveSubresource function resolves multiple samples to one pixel.

Parameters

unnamedParam1

hDevice [in]

A handle to the display device (graphics context).

unnamedParam2

hDstResource [in]

A handle to the destination resource to resolve to. This resource must have been created as D3D10_USAGE_DEFAULT and single sampled.

unnamedParam3

DstSubresource [in]

An index that indicates the destination subresource to resolve to.

unnamedParam4

hSrcResource [in]

A handle to the source resource to resolve from.

unnamedParam5

SrcSubresource [in]

An index that indicates the source subresource to resolve from.

unnamedParam6

ResolveFormat [in]

A DXGI_FORMAT-typed value that indicates how to interpret the contents of the resolved resource.

Remarks

The driver can use the pfnSetErrorCb callback function to set an error code.

The algorithm to resolve multiple samples to one pixel depends on the implementation.

The resolve operation shares similar restrictions to copy operations that occur in calls to the ResourceCopy and ResourceCopyRegion functions. That is, both source and destination resources must be the same type (for example, Texture2D), and no stretching or format conversions can occur. The driver can resolve only a whole subresource; therefore, both the source and destination subresources must be equal in dimensions. Because of typeless resources, the following interactions can exist with either the source or destination resource format:

See also

ResourceCopy

ResourceCopyRegion

pfnSetErrorCb