| Previous | Next |
| D2DERR_INVALID_GRAPH_CONFIGURATION | D2DERR_CYCLIC_GRAPH |
D2DERR_INVALID_INTERNAL_GRAPH_CONFIGURATION
D2DERR_INVALID_INTERNAL_GRAPH_CONFIGURATION belongs to Direct2D custom-effect transform graphs. Direct2D detected an invalid state inside the effect graph after or beyond public graph validation.
Read the HRESULT in context
A transform graph must have valid node identities, supported input counts, complete input mappings, one reachable output, and no cycles. Public graph configuration errors usually point to caller construction; an internal graph error warrants preserving a minimal valid-looking graph and runtime evidence rather than inventing a missing public rule.
runtime-created graph state, custom effect callbacks, and possible Direct2D defect.
A minimal test sequence
Build one pass-through node, validate it, and add one node or edge per step. Log input count, edge endpoints, effect-input mapping, output selection, and topological order before committing the graph.
- Verify the public graph with a minimal sample.
- Recreate the effect and device context.
- Remove custom transforms until the internal failure disappears.
- Test on another supported OS build or driver.
Evidence to preserve
- Public graph definition that preceded the error
- Debug-layer output and OS build
- Custom effect implementation and registration XML
- Device/context recreation result
Common wrong turns
The public INVALID_GRAPH_CONFIGURATION is the first suspect for caller-defined edges; this code warrants preserving evidence of a deeper runtime inconsistency. 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.
Technical references
Looking for a different code? Search another status or error code.