Fix T66556: Noisy drivers relations in certain cases
This commit is contained in:
parent
b2a9627600
commit
867cd8218a
Notes:
blender-bot
2023-02-14 08:58:01 +01:00
Referenced by issue #66556, Driver fail console message during update dependencies / rendering, appears to be working correctly though.
|
@ -56,8 +56,8 @@ void DepsgraphNodeBuilder::build_scene_parameters(Scene *scene)
|
|||
if (built_map_.checkIsBuiltAndTag(scene, BuilderMap::TAG_PARAMETERS)) {
|
||||
return;
|
||||
}
|
||||
build_parameters(&scene->id);
|
||||
add_operation_node(&scene->id, NodeType::PARAMETERS, OperationCode::SCENE_EVAL);
|
||||
add_operation_node(&scene->id, NodeType::PARAMETERS, OperationCode::PARAMETERS_EVAL);
|
||||
/* NOTE: This is a bit overkill and can potentially pull a bit too much into the graph, but:
|
||||
*
|
||||
* - We definitely need an ID node for the scene's compositor, otherwise re-mapping will no
|
||||
|
|
|
@ -52,8 +52,9 @@ void DepsgraphRelationBuilder::build_scene_parameters(Scene *scene)
|
|||
if (built_map_.checkIsBuiltAndTag(scene, BuilderMap::TAG_PARAMETERS)) {
|
||||
return;
|
||||
}
|
||||
build_parameters(&scene->id);
|
||||
OperationKey parameters_eval_key(
|
||||
&scene->id, NodeType::PARAMETERS, OperationCode::PARAMETERS_EVAL);
|
||||
&scene->id, NodeType::PARAMETERS, OperationCode::PARAMETERS_EXIT);
|
||||
OperationKey scene_eval_key(&scene->id, NodeType::PARAMETERS, OperationCode::SCENE_EVAL);
|
||||
add_relation(parameters_eval_key, scene_eval_key, "Parameters -> Scene Eval");
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue