Issue with linking to rigs running Blender in new depsgraph mode #46723

New Issue

S J Bennett · 2015-11-08T12:40:14+01:00

S J Bennett commented

2015-11-08 12:40:14 +01:00

System Information
Windows 7 64-bit, NVidia GeForce GTX 580

Blender Version
Broken: 2.76b running with --enable-new-depsgraph flag

Short description of error

Exact steps for others to reproduce the error

Start blender with --enable-new-depsgraph option
From default scene, create the default armature with one bone.
Parent Armature to Default Cube with Automatic Weights. (select Cube, select Armature, Ctrl+P, Automatic Weights)
Select Armature. Switch to Pose Mode, confirm that transforming Bone moves the Cube with it.
Group Armature and Default Cube into group TestCube (select both, Ctrl+G)
Save this file as testcube.blend
Start a new file.
Link the group TestCube into your scene
Make a proxy of the Armature (with instance selected, Ctrl+Alt+P, select "Armature")
With armature selected, go to Pose Mode and transform the bone

Note that
a) the bone doesn't transform the cube;
b) the rig is still visually present in the Linked instance, meaning there's two rigs on the screen;
c) if you save here and load the file back into Blender, the saved version doesn't work whether or not --enable-new-depsgraph was specified

If you repeat the steps above without --enable-new-depsgraph, the bone will transform the cube and the rig is no longer visible in the instanced version. If you save here and load it into Blender, it will work whether or not --enable-new-depsgraph was specified.

**System Information** Windows 7 64-bit, NVidia GeForce GTX 580 **Blender Version** Broken: 2.76b running with --enable-new-depsgraph flag **Short description of error** **Exact steps for others to reproduce the error** - Start blender with --enable-new-depsgraph option - From default scene, create the default armature with one bone. - Parent Armature to Default Cube with Automatic Weights. (select Cube, select Armature, Ctrl+P, Automatic Weights) - Select Armature. Switch to Pose Mode, confirm that transforming Bone moves the Cube with it. - Group Armature and Default Cube into group TestCube (select both, Ctrl+G) - Save this file as testcube.blend - Start a new file. - Link the group TestCube into your scene - Make a proxy of the Armature (with instance selected, Ctrl+Alt+P, select "Armature") - With armature selected, go to Pose Mode and transform the bone Note that a) the bone doesn't transform the cube; b) the rig is still visually present in the Linked instance, meaning there's two rigs on the screen; c) if you save here and load the file back into Blender, the saved version doesn't work whether or not --enable-new-depsgraph was specified If you repeat the steps above without --enable-new-depsgraph, the bone will transform the cube and the rig is no longer visible in the instanced version. If you save here and load it into Blender, it will work whether or not --enable-new-depsgraph was specified.

S J Bennett commented

2015-11-08 12:40:14 +01:00

Changed status to: 'Open'

S J Bennett commented

2015-11-08 12:40:14 +01:00

Added subscriber: @quollism

Bastien Montagne commented

2015-11-13 15:57:26 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2015-11-13 15:57:26 +01:00

Think this may have been already reported… Can you please:

Try the latest build from our buildbot.
Attach here simple .blend file to help reproducing the issue, as requested by template.

Think this may have been already reported… Can you please: * Try the latest build from [our buildbot](https://builder.blender.org/download). * Attach here simple .blend file to help reproducing the issue, as requested by template.

S J Bennett commented

2015-11-15 06:17:27 +01:00

Using the latest buildbot version 8c84a18 for Win64. It's better but not 100% fixed.

The broken proxy problem gets fixed on the following events:

file is saved and reloaded
Hitting Undo (Ctrl-Z) after creating the proxy (!)

I haven't found other tricks to make it work aside from those two workarounds.

This is how it looks when it's bugging out.

Here is the simple rig.

riggedcube.blend

Link this into a scene with Blender and follow from step 7 onwards. The rig is called RiggedCube. I can't attach broken files because they won't be broken when you load them due to the "in memory" nature of the bug. :)

Using the latest buildbot version 8c84a18 for Win64. It's better but not 100% fixed. The broken proxy problem gets fixed on the following events: - file is saved and reloaded - Hitting Undo (Ctrl-Z) after creating the proxy (!) I haven't found other tricks to make it work aside from those two workarounds. This is how it looks when it's bugging out. ![buggy_behaviour.png](https://archive.blender.org/developer/F254673/buggy_behaviour.png) Here is the simple rig. [riggedcube.blend](https://archive.blender.org/developer/F254671/riggedcube.blend) Link this into a scene with Blender and follow from step 7 onwards. The rig is called RiggedCube. I can't attach broken files because they won't be broken when you load them due to the "in memory" nature of the bug. :)

Sergey Sharybin was assigned by Bastien Montagne

2015-12-04 16:47:41 +01:00

Bastien Montagne commented

2015-12-04 16:47:41 +01:00

Added subscriber: @Sergey