PFND3D10DDI_CREATERASTERIZERSTATE - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d10umddi.h
PFND3D10DDI_CREATERASTERIZERSTATE Pfnd3d10ddiCreaterasterizerstate;
VOID Pfnd3d10ddiCreaterasterizerstate(
D3D10DDI_HDEVICE unnamedParam1,
const D3D10_DDI_RASTERIZER_DESC *unnamedParam2,
D3D10DDI_HRASTERIZERSTATE unnamedParam3,
D3D10DDI_HRTRASTERIZERSTATE unnamedParam4
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The CreateRasterizerState function creates a rasterizer state.
unnamedParam1hDevice [in]
A handle to the display device (graphics context).
unnamedParam2pRasterizerDesc [in]
A pointer to a D3D10_DDI_RASTERIZER_DESC structure that describes the parameters that the user-mode display driver uses to create a rasterizer state.
unnamedParam3hRasterizerState [in]
A handle to the driver's private data for the rasterizer state. The driver returns the size, in bytes, of the memory region that the Microsoft Direct3D runtime must allocate for the private data from a call to the driver's CalcPrivateRasterizerStateSize function. The handle is really just a pointer to a region of memory, the size of which the driver requested. The driver uses this region of memory to store internal data structures that are related to its rasterizer state object.
unnamedParam4hRTRasterizerState [in]
A handle to the rasterizer 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 DestroyRasterizerState function to destroy the handle that the hRasterizerState parameter specifies.
The user-mode display driver is not required to create more than 4,096 unique instances of rasterizer-state objects on a device at a time.
CalcPrivateRasterizerStateSize