Does Maya's playback cache automatically invalidate when a referenced node's attribute lock changes?
0 reputation · 19 Jun 2022, 00:06 UTC
0 reputation · 19 Jun 2022, 00:06 UTC
When working with referenced rigs in Maya, artists often lock certain attributes to prevent accidental changes. The playback cache is designed to store evaluated animation data and update only when the dependency graph signals a modification. However, it is unclear whether changing an attribute lock on a referenced node triggers the necessary dependency graph dirty flag that would cause the cache to discard stale entries.
If the cache does not invalidate in this scenario, scrubbing the timeline may display outdated transforms or deformations, leading to incorrect animation review. This uncertainty affects rig validation workflows where artists rely on real‑time playback to assess deformation correctness after locking attributes.
Does Maya's playback cache automatically purge stale data when an attribute lock on a referenced node is toggled? If not, what specific dependency graph events are required to force a cache refresh in this context? Are there any known work‑arounds besides manually flushing the cache that ensure up‑to‑date playback?
31275 reputation · 19 Jun 2022, 05:23 UTC
No. Toggling the lock state of an attribute on a referenced node does not automatically invalidate Maya's playback cache. Because locking or unlocking an attribute is a metadata change rather than a value change, it does not trigger the dependency graph's "dirty" flag, leaving the existing cached evaluation intact.
Maya's playback cache monitors for changes in attribute values that affect the final output of a node. When you lock an attribute, the underlying value remains the same; only the ability to modify that value is restricted. Since the data flowing through the dependency graph has not changed, the Evaluation Manager assumes the cached frames are still valid.
This behavior persists regardless of whether the node is local or referenced. Referencing does not add an additional layer of invalidation for attribute state changes.
If you have modified a rig's constraints or locked attributes and need to ensure the playback reflects the current state, use one of the following methods:
Cached Playback icon in the timeline and select Flush Cache.Parallel to DG and back can sometimes force a re-evaluation, though a manual flush is the only guaranteed method.To verify this behavior in your specific Maya version (assuming Maya 2022 or newer):
Cached Playback.Flush Cache and observe if the visual result updates.Diagnostic Detail Required: Are you utilizing a custom Evaluation Manager configuration or a specific version of the Parallel Evaluation mode? Certain custom overrides in the Evaluation Manager can alter how dirty flags are propagated.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.