| Previous | Next |
| MILEFFECTSERR_NOINPUTSOURCEATTACHED | MILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT |
MILEFFECTSERR_CONNECTORNOTCONNECTED
MILEFFECTSERR_CONNECTORNOTCONNECTED identifies a failure in MIL effect connectors and input binding. A connector exists in the effect graph but is not connected to the required peer. Investigation of this result should preserve the original object generation before cleanup, retry, or fallback creates a secondary result.
Telemetry with explanatory value
| Record | Why it matters here |
|---|---|
| Effect instance and owning graph or group identity | Comparing effect instance and owning graph or group identity shows whether this result follows input, object state, or environment. |
| Connector, input, child, listener, property, or transform involved | Preserving connector, input, child, listener, property, or transform involved provides the evidence needed to test this distinction: nOINPUTSOURCEATTACHED describes the effect-level absence of source input; this result points to an unconnected graph edge. |
| Calculated input and output bounds | Recording calculated input and output bounds separates the MIL effect connectors and input binding boundary from a later wrapper symptom. |
| Construction sequence and first method returning the HRESULT | In this result diagnostics, recording construction sequence and first method returning the HRESULT ties the HRESULT to the MIL effect connectors and input binding boundary rather than to the final visible failure. |
Where the failure occurs
Connectors represent edges between effect nodes and are meaningful only with their owning effect and graph. An unconnected connector, a connector from another effect, and a required input with no source are three different graph defects., preserve connector identity, owner identity, slot, direction, and the point at which the edge was established.
Inspect the following boundary: edge creation between graph nodes or groups.
Smallest faithful reproducer
When it is returned, build one source, one effect, and one output connection. Add the disputed connector or input only after the baseline validates, and inspect both ends of the edge before bounds or shader work begins.
- Trace both connector endpoints and connect them once in the documented direction.
- rebuild the smallest graph containing only the implicated node and one known input.
- When it is returned, log ownership changes and graph generation numbers.
- Validate the graph before allocating large intermediate resources.
Avoid broad resets
NOINPUTSOURCEATTACHED describes the effect-level absence of source input; it points to an unconnected graph edge. Do not catch the HRESULT and continue rendering with a partially connected graph; later failures can obscure the invariant that was first violated.
Separate object, input, and environment
| Test | Interpretation | Hold constant |
|---|---|---|
| Same environment, reduced input | If it disappears with a smaller faithful case, complexity within MIL effect connectors and input binding is implicated. | Keep effect instance and owning graph or group identity fixed while simplifying calculated input and output bounds. |
| Same input, fresh object generation | If it changes after rebuilding state, examine ownership across the effect instance, connector builder, graph owner, listener, and bounds calculator. | Place connector, input, child, listener, property, or transform involved on the timeline of the last successful transition. |
| Same operation on a controlled second path | If it follows one environment, the failure is not explained by source data alone. | Compare visual generation, effect registration, shader profile, rendering tier, and target dimensions while preserving construction sequence and first method returning the HRESULT. |
Completion test
A correction for it should let the operation at the MIL effect connectors and input binding boundary complete repeatedly under the original supported conditions. Repeat the control that begins with “Trace both connector endpoints and connect them once in the documented direction” and confirm that the following lifecycle step also succeeds. Keep the original failing sample and one deliberate negative case so fallback cannot be mistaken for repair.
Technical references
When it is returned, these references define the public API family, object model, or error list used to interpret this status.
- Microsoft Open Specifications: HRESULT values.
- Microsoft: WPF bitmap effects overview.
- Microsoft: PixelShader class.
- Microsoft: Direct2D custom effects.
- Microsoft: ID2D1TransformGraph.
Looking for a different code? Search another status or error code.