wave5-chunk-did-change-incremental-update

Use chunk.DidChange() inside your IJobChunk Execute method to gate per-chunk execution, returning early when no relevant input component data changed since the last frame to skip unnecessary recomputation.

chunk.DidChange always returning true usually means you are not passing a fresh LastSystemVersion. You must pass state.LastSystemVersion so DidChange reflects real system-to-system change versioning.

For multiple input components, combine multiple DidChange checks (e.g., parent and child transforms) to propagate change logic correctly, ensuring only chunks with actual modifications trigger recomputations.

Yes, chunk-level incremental execution is ideal for mostly-static worlds where most entities remain unchanged across frames, preventing wasted CPU time on expensive derived values like world-space bounds.

Chunk-level incremental execution is a performance optimization that gates per-chunk processing using chunk.DidChange(), skipping work for entire chunks whose input component data has not changed since the last system version.

DidChange operates at chunk granularity, meaning any single component change forces recomputation for the entire chunk, and it requires correct component handles and a fresh LastSystemVersion to function properly.