PFND3D10DDI_QUERYBEGIN - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d10umddi.h
PFND3D10DDI_QUERYBEGIN Pfnd3d10ddiQuerybegin;
VOID Pfnd3d10ddiQuerybegin(
D3D10DDI_HDEVICE unnamedParam1,
D3D10DDI_HQUERY unnamedParam2
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The QueryBegin function marks the beginning of a sequence of graphics commands for a query and transitions the query to the "building" state.
unnamedParam1hDevice [in]
A handle to the display device (graphics context).
unnamedParam2hQuery [in]
A handle to the query object to begin.
The driver can use the pfnSetErrorCb callback function to set an error code.
The driver is not required to support the QueryBegin function for a D3D10DDI_QUERY_EVENT or D3D10DDI_QUERY_TIMESTAMP query operation. Such a query operation has an implied beginning.
The Microsoft Direct3D runtime cannot call QueryBegin on a predicate that is currently bound to the pipeline through a call to the SetPredication function.
The driver should not encounter any error, except for D3DDDIERR_DEVICEREMOVED. Therefore, if the driver passes any error, except for D3DDDIERR_DEVICEREMOVED, in a call to the pfnSetErrorCb function, the Direct3D runtime will determine that the error is critical. Even if the device was removed, the driver is not required to return D3DDDIERR_DEVICEREMOVED; however, if device removal interfered with the operation of QueryBegin (which typically should not happen), the driver can return D3DDDIERR_DEVICEREMOVED.