Drivers in Armature layer or in Bone Layers lock linked armature #38139

Closed
opened 2014-01-09 13:40:23 +01:00 by Juan Pablo Bouza · 10 comments

Ubuntu 13.04 64 bits

Hash: 17a4ba2

I've attached a sample blend file with 2 Armatures that belong to 2 different groups that are called as follows:

armature_layers
bone_layers

Well, the name of the group correspond to where I have added a driver in the armature. So, one armature has a driver in the armature layer properties, and the other one has it in the layer properties of one of its bones.

Now, If you link these groups into a new blend file and make a proxy of each armature, you'll notice that in the latest GIT, everything gets locked, that is, you can't move any bone in pose mode, and not even the empty of the group. I've come to the conclusion that these drivers, which were working perfectly well with linked rigs in 2.69, are the cause of the problem in GIT.

Ubuntu 13.04 64 bits Hash: 17a4ba2 I've attached a sample blend file with 2 Armatures that belong to 2 different groups that are called as follows: armature_layers bone_layers Well, the name of the group correspond to where I have added a driver in the armature. So, one armature has a driver in the armature layer properties, and the other one has it in the layer properties of one of its bones. Now, If you link these groups into a new blend file and make a proxy of each armature, you'll notice that in the latest GIT, everything gets locked, that is, you can't move any bone in pose mode, and not even the empty of the group. I've come to the conclusion that these drivers, which were working perfectly well with linked rigs in 2.69, are the cause of the problem in GIT.
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @jpbouza-4

Added subscriber: @jpbouza-4
Author
Member

linking_bug.blend

Trying to attach the blend file again. Guess it didn't work last time

[linking_bug.blend](https://archive.blender.org/developer/F65193/linking_bug.blend) Trying to attach the blend file again. Guess it didn't work last time

Added subscribers: @Sergey, @brecht

Added subscribers: @Sergey, @brecht

I can see the difference, however both 2.69 and latest Git find dependency cycles in this file:

Dependency cycle detected:
  Bone_Layer depends on bone_layers_proxy through Proxy.
  bone_layers_proxy depends on Bone_Layer through Driver.

Dependency cycle detected:
  Armature_layers depends on armature_layers_proxy through Proxy.
  armature_layers_proxy depends on Armature_layers through Driver.

Maybe @Sergey knows if dependency cycles are handled different now in the threaded depsgraph, but these cycles can give problems in various situations and should be avoided.

I can see the difference, however both 2.69 and latest Git find dependency cycles in this file: ``` Dependency cycle detected: Bone_Layer depends on bone_layers_proxy through Proxy. bone_layers_proxy depends on Bone_Layer through Driver. Dependency cycle detected: Armature_layers depends on armature_layers_proxy through Proxy. armature_layers_proxy depends on Armature_layers through Driver. ``` Maybe @Sergey knows if dependency cycles are handled different now in the threaded depsgraph, but these cycles can give problems in various situations and should be avoided.
Sergey Sharybin self-assigned this 2014-01-10 09:58:18 +01:00

That's what i'm fighting right now.

Currently all the objects from the cycle are not updated. which is a real bummer. However, i don't know yet what would be the correct order of update in such situation.

That's what i'm fighting right now. Currently all the objects from the cycle are not updated. which is a real bummer. However, i don't know yet what would be the correct order of update in such situation.

This issue was referenced by blender/blender-addons-contrib@bc989497de

This issue was referenced by blender/blender-addons-contrib@bc989497deeaf2ec79ccfbe7b5e43509eb867b06

This issue was referenced by bc989497de

This issue was referenced by bc989497deeaf2ec79ccfbe7b5e43509eb867b06

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Closed by commit bc989497de.

Closed by commit bc989497de.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#38139
No description provided.