From 411a781491954c226ae1f91a8b2735328d85258e Mon Sep 17 00:00:00 2001 From: Sergey Sharybin Date: Fri, 2 Mar 2018 15:50:28 +0100 Subject: Depsgraph: Silence obviously noisy relations build errors Those were happening for drivers which points to invalid drivers, and those drivers will have their own dedicated error prints. --- .../blender/depsgraph/intern/builder/deg_builder_relations.cc | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'source/blender/depsgraph') diff --git a/source/blender/depsgraph/intern/builder/deg_builder_relations.cc b/source/blender/depsgraph/intern/builder/deg_builder_relations.cc index 0d85b1dfc93..914c8ef33db 100644 --- a/source/blender/depsgraph/intern/builder/deg_builder_relations.cc +++ b/source/blender/depsgraph/intern/builder/deg_builder_relations.cc @@ -1126,7 +1126,16 @@ void DepsgraphRelationBuilder::build_driver_data(ID *id, FCurve *fcu) } else { RNAPathKey target_key(id, rna_path); - add_relation(driver_key, target_key, "Driver -> Target"); + if (RNA_pointer_is_null(&target_key.ptr)) { + /* TODO(sergey): This would only mean that driver is broken. + * so we can't create relation anyway. However, we need to avoid + * adding drivers which are known to be buggy to a dependency + * graph, in order to save computational power. + */ + } + else { + add_relation(driver_key, target_key, "Driver -> Target"); + } } } -- cgit v1.2.3