PFND3D10DDI_CREATEDEPTHSTENCILSTATE - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d10umddi.h
PFND3D10DDI_CREATEDEPTHSTENCILSTATE Pfnd3d10ddiCreatedepthstencilstate;
VOID Pfnd3d10ddiCreatedepthstencilstate(
D3D10DDI_HDEVICE unnamedParam1,
const D3D10_DDI_DEPTH_STENCIL_DESC *unnamedParam2,
D3D10DDI_HDEPTHSTENCILSTATE unnamedParam3,
D3D10DDI_HRTDEPTHSTENCILSTATE unnamedParam4
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The CreateDepthStencilState function creates a depth stencil state.
unnamedParam1hDevice [in]
A handle to the display device (graphics context).
unnamedParam2pDepthStencilDesc [in]
A pointer to a D3D10_DDI_DEPTH_STENCIL_DESC structure that describes the parameters that the user-mode display driver uses to create a depth stencil state.
unnamedParam3hDepthStencilState [in]
A handle to the driver's private data for the depth stencil state.
unnamedParam4hRTDepthStencilState [in]
A handle to the depth stencil state that the driver should use anytime it calls back into the Direct3D runtime.
The driver can use the pfnSetErrorCb callback function to set an error code.
The driver can pass E_OUTOFMEMORY (if the driver runs out of memory) or D3DDDIERR_DEVICEREMOVED (if the device has been removed) in a call to the pfnSetErrorCb function. The Direct3D runtime will determine that any other errors are critical. If the driver passes any errors, including D3DDDIERR_DEVICEREMOVED, the Direct3D runtime will determine that the handle is invalid; therefore, the runtime will not call the DestroyDepthStencilState function to destroy the handle that the hDepthStencilState parameter specifies.
The user-mode display driver is not required to create more than 4,096 unique instances of depth-stencil-state objects on a device at a time.
CalcPrivateDepthStencilStateSize
D3D10_DDI_DEPTH_STENCILOP_DESC