PFND3D11DDI_CREATEDEPTHSTENCILVIEW - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d10umddi.h
PFND3D11DDI_CREATEDEPTHSTENCILVIEW Pfnd3d11ddiCreatedepthstencilview;
VOID Pfnd3d11ddiCreatedepthstencilview(
D3D10DDI_HDEVICE unnamedParam1,
const D3D11DDIARG_CREATEDEPTHSTENCILVIEW *unnamedParam2,
D3D10DDI_HDEPTHSTENCILVIEW unnamedParam3,
D3D10DDI_HRTDEPTHSTENCILVIEW unnamedParam4
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The CreateDepthStencilView(D3D11) function creates a depth-stencil view.
unnamedParam1hDevice [in]
A handle to the display device (graphics context).
unnamedParam2pCreateDepthStencilView [in]
A pointer to a D3D11DDIARG_CREATEDEPTHSTENCILVIEW structure that describes the parameters that the user-mode display driver uses to create a depth-stencil view.
unnamedParam3hDepthStencilView [in]
A handle to the driver's private data for the depth stencil view.
unnamedParam4hRTDepthStencilView [in]
A handle to the shader resource view that the driver should use when it calls back into the Direct3D runtime.
The driver can use the pfnSetErrorCb callback function to set an error code.
The driver might run out of memory. Therefore, the driver can pass E_OUTOFMEMORY or D3DDDIERR_DEVICEREMOVED in a call to the pfnSetErrorCb function. The Direct3D runtime determines that any other errors are critical. If the driver passes any errors, which includes D3DDDIERR_DEVICEREMOVED, the Direct3D runtime determines that the handle is invalid; therefore, the runtime does not call the DestroyDepthStencilView function to destroy the handle that the hDepthStencilView parameter specifies.
CalcPrivateDepthStencilViewSize(D3D11)
D3D11DDIARG_CREATEDEPTHSTENCILVIEW