Copy bones doesn't copy drivers #87415

New Issue

Nahuel Belich · 2021-04-12T11:56:02+02:00

Nahuel Belich commented

2021-04-12 11:56:02 +02:00

System Information
Operating system: Linux-5.4.0-70-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39

Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-04-11 06:02, hash: d3cb1d845b

Short description of error
When copy bones with drivers the drivers are not copied, does work with constraint but not drivers, this makes really difficult to do and copy half of a symmetrical rig

no copy drivers.mp4

Steps to reproduce the error.
dontcopydrivers.blend
1- open the file.
2-select armature and enter edit mode
3-Duplicate the bones using any method (shift+d, symmetry etc )
4-the new bone does not have a the driver in the X location

**System Information** Operating system: Linux-5.4.0-70-generic-x86_64-with-glibc2.31 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39 **Blender Version** Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-04-11 06:02, hash: `d3cb1d845b` **Short description of error** When copy bones with drivers the drivers are not copied, does work with constraint but not drivers, this makes really difficult to do and copy half of a symmetrical rig [no copy drivers.mp4](https://archive.blender.org/developer/F9930307/no_copy_drivers.mp4) Steps to reproduce the error. [dontcopydrivers.blend](https://archive.blender.org/developer/F9930311/dontcopydrivers.blend) 1- open the file. 2-select armature and enter edit mode 3-Duplicate the bones using any method (shift+d, symmetry etc ) 4-the new bone does not have a the driver in the X location

Nahuel Belich commented

2021-04-12 11:56:02 +02:00

Added subscriber: @NahuelBelich

VLC commented

2021-04-12 12:16:13 +02:00

Added subscriber: @VLC

VLC commented

2021-04-12 12:16:13 +02:00

I have the same problem. I'm working on linux and blender 2.93 alpha.

Falk David commented

2021-04-12 12:35:43 +02:00

Added subscriber: @filedescriptor

Falk David commented

2021-04-12 12:35:43 +02:00

I believe this is working as intended. Duplication of the drivers is just not implemented/supported. (E.g. this would not classify as a bug)

Germano Cavalcante commented

2021-04-15 17:22:23 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2021-04-15 17:22:23 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Germano Cavalcante commented

2021-04-15 17:22:23 +02:00

I'm not familiar with that.
If there are cases where the drivers are also copied, then this can be considered a bug.
Otherwise it is a request for modified/improved behavior.

I'm not familiar with that. If there are cases where the drivers are also copied, then this can be considered a bug. Otherwise it is a request for modified/improved behavior.

Falk David commented

2021-04-19 07:46:45 +02:00

I believe the problem is that drivers are attached to RNA properties. So duplicating them would be a bit complicated. You would first need to iterate over all relevant RNA properties of the bone (props that could have drivers) and then check every property if it has a driver attached to it. So maybe that's why we don't do it.

Delano762 commented

2021-09-20 18:39:05 +02:00

Added subscriber: @Delano762

Pauan commented

2021-09-25 22:15:49 +02:00

Added subscriber: @pauanyu_blender

Cigitia commented

2022-05-05 00:25:59 +02:00

Added subscriber: @Cigitia

Sybren A. Stüvel commented

2022-11-24 15:08:24 +01:00

Added subscriber: @dr.sybren

Sybren A. Stüvel commented

2022-11-24 15:08:24 +01:00

In #87415#1148431, @filedescriptor wrote:
I believe the problem is that drivers are attached to RNA properties. So duplicating them would be a bit complicated. You would first need to iterate over all relevant RNA properties of the bone (props that could have drivers) and then check every property if it has a driver attached to it. So maybe that's why we don't do it.

That wouldn't be too hard, because all the RNA paths will start with pose.bone["bonename"]…, so matching on prefix is quite doable.

In #87415#1146939, @mano-wii wrote:
If there are cases where the drivers are also copied, then this can be considered a bug.
Otherwise it is a request for modified/improved behavior.

It would be handy if the drivers were copied along as well. Currently it's simply not implemented for bones. Then again, on the other hand it is implemented for objects. In any case this is a duplicate of #49182 (Bone drivers do not copy when duplicated).

> In #87415#1148431, @filedescriptor wrote: > I believe the problem is that drivers are attached to RNA properties. So duplicating them would be a bit complicated. You would first need to iterate over all relevant RNA properties of the bone (props that could have drivers) and then check every property if it has a driver attached to it. So maybe that's why we don't do it. That wouldn't be too hard, because all the RNA paths will start with `pose.bone["bonename"]…`, so matching on prefix is quite doable. > In #87415#1146939, @mano-wii wrote: > If there are cases where the drivers are also copied, then this can be considered a bug. > Otherwise it is a request for modified/improved behavior. It would be handy if the drivers were copied along as well. Currently it's simply not implemented for bones. Then again, on the other hand it **is** implemented for objects. In any case this is a duplicate of #49182 (Bone drivers do not copy when duplicated).

Sybren A. Stüvel commented

2022-11-24 15:08:41 +01:00

Closed as duplicate of #49182

Sybren A. Stüvel closed this issue

2022-11-24 15:08:41 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Copy bones doesn't copy drivers #87415