PFND3D11DDI_CREATECOMMANDLIST - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d10umddi.h
PFND3D11DDI_CREATECOMMANDLIST Pfnd3d11ddiCreatecommandlist;
VOID Pfnd3d11ddiCreatecommandlist(
D3D10DDI_HDEVICE unnamedParam1,
const D3D11DDIARG_CREATECOMMANDLIST *unnamedParam2,
D3D11DDI_HCOMMANDLIST unnamedParam3,
D3D11DDI_HRTCOMMANDLIST unnamedParam4
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The CreateCommandList function creates a command list.
unnamedParam1hDevice [in]
A handle to the display device (graphics context).
unnamedParam2pCreateCommandList [in]
A pointer to a D3D11DDIARG_CREATECOMMANDLIST structure that describes the parameters that the user-mode display driver uses to create a command list.
unnamedParam3hCommandList [in]
A handle to the driver's private data for the command list.
unnamedParam4hRTCommandList [in]
A handle to the command list 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 is only required to implement CreateCommandList if the driver supports the D3D11DDICAPS_COMMANDLISTS_BUILD_2 capability that can be returned in the D3D11DDI_THREADING_CAPS structure from a call to the GetCaps(D3D10_2) function.
The driver can pass E_OUTOFMEMORY (if the driver runs out of memory) or D3DDDIERR_DEVICEREMOVED (if the device is removed) 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 DestroyCommandList function to destroy the handle that the hCommandList parameter specifies.