Alembic export: don't assume transform is always animated

Instead of always writing the transform on every frame, it's now checked
whether the object is animated at all. This could be made stricter to
reduce false positives, for example by checking FCurves and drivers to
see whether translation/rotation/scale is animated. However, this
approach is already better than the `return true` we had before.

This commit adds the BKE_animdata_id_is_animated(id) function, which
returns true if the ID datablock has non-empty animation data. This is
determined by checking the the active action's fcurves, the drivers, and
NLA tracks.

1 files changed, 18 insertions, 0 deletions

diff --git a/source/blender/blenkernel/intern/anim_sys.c b/source/blender/blenkernel/intern/anim_sys.c
index 88a8463b994..6ecfeaffdba 100644
--- a/source/blender/blenkernel/intern/anim_sys.c
+++ b/source/blender/blenkernel/intern/anim_sys.c
@@ -283,6 +283,24 @@ void BKE_animdata_free(ID *id, const bool do_id_user)
   }
 }
 
+bool BKE_animdata_id_is_animated(struct ID *id)
+{
+  if (id == NULL) {
+    return false;
+  }
+
+  AnimData *adt = BKE_animdata_from_id(id);
+  if (adt == NULL) {
+    return false;
+  }
+
+  if (adt->action != NULL && !BLI_listbase_is_empty(&adt->action->curves)) {
+    return true;
+  }
+
+  return !BLI_listbase_is_empty(&adt->drivers) || !BLI_listbase_is_empty(&adt->nla_tracks);
+}
+
 /* Copying -------------------------------------------- */
 
 /**