Disk nCache vs. Live Nucleus Solving: Which Invalidation Policy for Heavy nCloth Playback?

For a heavy nCloth shot requiring real-time playback, Maya offers two documented paths: live Nucleus solving while scrubbing, or disk-based nCache created via nCache > Create New Cache. In current Maya versions, the disk cache provides stable frame timing, but Maya does not automatically invalidate stored frames when certain upstream inputs change, such as the nucleus start frame, initial state, or the cached mesh's construction history. The cache node keeps serving stored geometry until it is deleted, so the image can stay stale after a solver edit.

The unresolved decision is the invalidation policy. Maya provides no automatic reconciliation between the nucleus solver and the cache node, forcing a choice between a conservative rule that deletes the cache on any upstream edit and a faster rule that recaches only when the visual result changes. Appending via nCache > Append to Cache extends a range without a full rebuild, but the same staleness rule still applies to appended frames. Invalidation behavior can differ across solvers.

Against a specific playback deadline and scene complexity, which policy should govern cache deletion: a strict delete-on-any-upstream-edit rule, or a visual-check recache rule? How should the policy differ when appending versus creating a new cache? Does construction history on the cached mesh demand a stricter threshold than a pure nucleus parameter change?