Internal Direct3D Mobile Driver Errors (Windows Embedded CE 6.0)
1/6/2010
A number of Microsoft® Direct3D® Mobile methods cause the Direct3D Mobile middleware to place low-level commands into a buffer before sending them to the driver for execution. The return values from these methods only reflect the methods' success in adding commands to the command buffer. They do not reflect the driver's success in parsing and executing commands from the command buffer.
Direct3D Mobile drivers are expected to parse and process as much of the command buffer as possible. Drivers can, though they are not required to, make their internal error codes arising from command buffer processing available to applications. They can do this through a driver-defined value to be passed in the DevInfoId parameter of the IDirect3DMobileDevice::GetInfo method. For example, the null driver uses the value D3DM_GETDRIVERERROR_DEVINFOID for this purpose.