| Previous | Next |
| MILAVERR_UNKNOWNHARDWAREERROR | MILEFFECTSERR_EFFECTNOTPARTOFGROUP |
MILEFFECTSERR_UNKNOWNPROPERTY
MILEFFECTSERR_UNKNOWNPROPERTY identifies a failure in MIL effect property lookup. The effect graph was asked to read or set a property that the target effect does not expose. Investigation of this result should preserve the original object generation before cleanup, retry, or fallback creates a secondary result.
Start with the returning API
Effect properties are resolved against metadata belonging to a particular effect implementation and registration. A property name, index, or identifier valid for one effect or runtime version does not become valid for another., preserve the effect identity and declared property set before converting the failure into a generic binding or XAML error.
Inspect the following boundary: property lookup by identifier, name, index, or registered metadata.
Diagnostic evidence matrix
| Record | Why it matters here |
|---|---|
| Effect instance and owning graph or group identity | Preserving effect instance and owning graph or group identity provides the evidence needed to test this distinction: mILEFFECTSERR_RESERVED should not be used as a substitute for unknown application properties. |
| Connector, input, child, listener, property, or transform involved | Recording connector, input, child, listener, property, or transform involved separates the MIL effect property lookup boundary from a later wrapper symptom. |
| Calculated input and output bounds | In this result diagnostics, recording calculated input and output bounds ties the HRESULT to the MIL effect property lookup boundary rather than to the final visible failure. |
| Construction sequence and first method returning the HRESULT | Comparing construction sequence and first method returning the HRESULT shows whether this result follows input, object state, or environment. |
Useful comparison axes
| Test | Interpretation | Hold constant |
|---|---|---|
| Same environment, reduced input | If this result disappears with a smaller faithful case, complexity within MIL effect property lookup 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. |
Reproduce without destructive cleanup
When it is returned, enumerate the available properties from the exact effect instance, then read a known property and the disputed property without changing graph membership. This separates metadata lookup from rendering and bounds calculation.
- Compare the requested property with the effect’s declared property table and value type.
- 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.
Limits of this code
MILEFFECTSERR_RESERVED should not be used as a substitute for unknown application properties. Do not catch the HRESULT and continue rendering with a partially connected graph; later failures can obscure the invariant that was first violated.
What success must demonstrate
A correction for it should let the operation at the MIL effect property lookup boundary complete repeatedly under the original supported conditions. Repeat the control that begins with “Compare the requested property with the effect’s declared property table and value type” 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.