Visual feedback on Dependecy Cycles errors
Blender makes it extremely cryptic to know about such cycle existence in scene:
-
Message about it exists only in System Console(ie forcing users to run Blender from terminal on MacOS/Linux in lack of menu entry for opening it like on Windows)
-
Effects sometimes can be anything but obvious, or apparent only in some specific conditions, and keeping track of those issues in process requires constant attention to a system console what's not even a part of Blender UI
-
Those deps chains can be very long, involving bones, constraints, parent relations, modifiers, etc...
Even reporting (Error) in Python Console would've been enough for me, but why not show some visual clues in viewport? That way user will see the problem immediately upon creating it. We already have info in the output(object name and cause), something simple like overlay color(red) over objects with a text, displaying error on deptree update.
2 Comments
That would come with nodal rigging. Which was announced as part of the "Even Further Future" plans in the "A new Animation System" Blender Conference .
But that has nothing to do with rigging. It affects every object in scene, i just used armature as most common occurrence.