| UID | title | description | old-location | 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 | tech.root | req.typenames | f1_keywords | topic_type | api_type | api_location | api_name | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NC:d3d10umddi.PFND3D11_1DDI_CREATERASTERIZERSTATE |
PFND3D11_1DDI_CREATERASTERIZERSTATE (d3d10umddi.h) |
The PFND3D11_1DDI_CREATERASTERIZERSTATE callback function creates a user-mode display driver rasterizer state. |
display\createrasterizerstate_d3d11_1_.htm |
05/10/2018 |
|
CreateRasterizerState(D3D11_1), CreateRasterizerState(D3D11_1) callback function [Display Devices], PFND3D11_1DDI_CREATERASTERIZERSTATE, PFND3D11_1DDI_CREATERASTERIZERSTATE callback, d3d10umddi/CreateRasterizerState(D3D11_1), display.createrasterizerstate_d3d11_1_, display.pfncreaterasterizerstate |
d3d10umddi.h |
D3d10umddi.h |
Desktop |
Windows 8 |
Windows Server 2012 |
Windows |
display |
|
|
|
|
|
Creates a rasterizer state.
hDevice [in]
A handle to the display device (graphics context).
pRasterizerDesc [in]
A pointer to a D3D11_1_DDI_RASTERIZER_DESC structure that describes the parameters that the user-mode display driver uses to create a rasterizer state.
hRasterizerState [in]
A handle to the driver's private data for the rasterizer state.
hRTRasterizerState
A handle to the rasterizer state 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 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 incorrect; 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.