| Previous | Next |
| D2DERR_BITMAP_BOUND_AS_TARGET | D2DERR_INTERMEDIATE_TOO_LARGE |
D2DERR_INSUFFICIENT_DEVICE_CAPABILITIES
The scope of D2DERR_INSUFFICIENT_DEVICE_CAPABILITIES is Direct2D targets, device capabilities, and intermediates. The Direct3D device backing Direct2D lacks a capability required by the requested operation. Keep 0x88990026 beside the returning method because a wrapper can replace this distinction with a generic subsystem message.
Subsystem context
A device context has target identity and is backed by a Direct3D device with format, feature, shader, and maximum-size limits. Temporarily changing targets, requesting unsupported capabilities, or propagating huge effect bounds are different problems. Record target history and capability queries before allocating or drawing.
Feature level, format support, shader model, effects, and device creation flags.
Do not hide the original condition
UNSUPPORTED_VERSION concerns the Direct2D API contract; this code concerns the backing device’s capabilities. Do not respond with a universal render-target recreation loop unless the returned status specifically documents device-loss recovery; graph, property, numeric, lifetime, and print-state errors require correcting their contract.
Evidence to preserve
- Adapter, feature level, WARP or hardware mode
- Required formats and D3D support flags
- Effect or operation requesting the capability
- Device creation and capability-query results
Isolation procedure
Use the original target and a small supported bitmap or effect region first. Then change one target, capability, format, or spatial expansion at a time while logging device and context generations.
- Query support before constructing resources.
- Test WARP software rendering.
- Use a simpler effect or supported format.
- Compare another adapter without changing application logic.
Technical references
Looking for a different code? Search another status or error code.