- User Since
- Mar 3 2013, 8:34 PM (293 w, 1 d)
Dec 31 2017
I feel strongly that the grid:
Aug 15 2015
- How do we "use" their poses if is not possible to apply them? The utility of poses is:
Aug 14 2015
Select the object gun_2_src_arma in tester.blend. Note it's pose_position property value, either Pose Position or Rest Position.
Aug 5 2015
The workaround is to create a child of constraint on a particle system. Regardless, I believe this should be maintained as a bug and fixed regardless of any possibility of a particle system rewrite.
Jun 9 2015
I don't see how closing this is a productive action... It is the only place solicit input on the value of this feature.
Ideally I'd like to discuss the challenges specifically with instancing recursive dupligroups by the particle system. If you are not refering to object hierarchies in the general sense, please do not respond to #2.
Jun 8 2015
This is not a bug.
Jun 7 2015
Jun 6 2015
It may not have been supported at all but dupligroups are the only way to manage object hierarchies and instancing in blender. Dupligroups are the only way to this common object hierarchy workflow:
Jun 5 2015
May 30 2015
I have a file that has materials caused by workflow as well. I don't quite remember how these materials accumulated these ghost users but I will try to remember.
You can append the test duplicating empty from this provider file.
This is with 2.74 3-31 release from the main site and has been occuring since atleast 2.65, but presumably during all of Blender's life.
This is also occuring with this plugin because the plugin does not place the objects assigned to the group into the scene anywhere (as opposed to append, which does).