Depsgraph: Fix missing point cache reset when physics changes

Among all the lines moved around, the general idea is quite simple.
Actually, there are two ideas implemented there.

First one, is when object itself is tagged for update, we tag its
point cache component for evaluation, which makes it so point cache
is properly reset. We do it implicitly because otherwise we'll need
to go everywhere and add explicit tag in almost all the properties.

Second thing is, we link all collider and force fields to a point
cache component using special type of link. This type of link only
allows flush if change is caused by a user update. This way reset
does not happen when change is caused due to animation, but will
properly happen when user causes indirect change to the objects
which are part of physics simulation.

1 files changed, 6 insertions, 4 deletions

diff --git a/source/blender/depsgraph/intern/depsgraph.h b/source/blender/depsgraph/intern/depsgraph.h
index 3e7d34414ea..bbf1f883bde 100644
--- a/source/blender/depsgraph/intern/depsgraph.h
+++ b/source/blender/depsgraph/intern/depsgraph.h
@@ -72,11 +72,13 @@ struct OperationDepsNode;
 /* Settings/Tags on Relationship */
 typedef enum eDepsRelation_Flag {
 	/* "cyclic" link - when detecting cycles, this relationship was the one
-	 * which triggers a cyclic relationship to exist in the graph.
-	 */
-	DEPSREL_FLAG_CYCLIC     = (1 << 0),
+	 * which triggers a cyclic relationship to exist in the graph. */
+	DEPSREL_FLAG_CYCLIC               = (1 << 0),
 	/* Update flush will not go through this relation. */
-	DEPSREL_FLAG_NO_FLUSH   = (1 << 1),
+	DEPSREL_FLAG_NO_FLUSH             = (1 << 1),
+	/* Only flush along the relation is update comes from a node which was
+	 * affected by user input. */
+	DEPSREL_FLAG_FLUSH_USER_EDIT_ONLY = (1 << 2),
 } eDepsRelation_Flag;
 
 /* B depends on A (A -> B) */