RxLaboratory Forum

Hi there!

Lets say, I have a prerigged arm here in a comp, done with puppet-pins and with a controller.
Now, I want to stack this arm-comp on a body in a different comp.
Question: Is it possible to connect the prerigged armcomp to the body (in its comp) in order to fully (re)act as in a normal characters IK-Chain?
If so: How?

Thx in advance, keep on animating
hrundi

Hi!

Two ways:

one a bit experimental for now (but I'm working on it):

- Use the "extract controllers" tool for the arm precomp (using expressions will be better for performance and you don't really need master properties for this), and parent the extracted controllers to the rest of the body
Easy but I'm not sure extracting again all the controllers of the characters will work correctly for animation. I'm working on that too and it will be guaranteed to work in the next update

- Add all the structures in the same comp (the one of the body) but keep the need precomposed if you need. Add anything "substructure" (like puppet tool and bones) inside these precomps, but when it comes to parenting to the structures, use the "parent across comps" tool to parent what you need to the structures. Then, run the auto-rig, use the connector, do anything you need in the main comp. Et voilà

Note that you could also simply use the "parent across comps" tool with an arm already rigged, you'll just need to parent the structure of the arm to the torso, and parent the controller to another one outside of the comp. That should work correctly too. This tool is very, very useful!

The doc for parent across comps is there: https://duik-docs.rainboxlab.org/parent ... tions.html

Hi Duduf and thank you VERY much,
Your tip#2 brings me on the road now. Amazing!

A few questions regarding to the parenting-across-comps window:
There are not all project comps listed here (also, pressing the refresh-button doesnt bring them up)?
And what is this pipette-button for?

Thx in advance,
hrundi

Yep, that's normal, you can only parent from one precomp to a containing comp or the opposite. That's because if you have several levels of nesting, and use the same precomp in several comps, Duik can't decide how to handle transformations "in between" the precomp and the containing(s) comp(s).
The simple workaround is to parent each level to the next intermediate sub or top level comp manually, all the way to the comp where is your parent layer, using null layers for example

I see, my fault - I had the wrong Arm-Precomp thrown in the final Comp to rig. Therefore, the final Comp wasnt shown in the Cross-Comp-Window.

But - I ran into an other issue now.
After cross-connecting the structures of my precom-Arm to the structures of the arm in the final Comp (and further after auto-rig&IK), moving of the final-comp-controller results in distorted image in its preview (please see attached picture).
Any idea whats happening here?
thx in advance
hrundi

Got it.
Using the advanced Puppet Pins instead of the legacy ones I was able to get rid of this issue.

That's strange anyway. Maybe the mesh needed to be expanded a little

Duduf wrote: ↑Thu Apr 02, 2020 7:24 am - Use the "extract controllers" tool for the arm precomp (using expressions will be better for performance and you don't really need master properties for this),

Hi! Just saw the comment above regarding performance. I am about to "reference" a character into several shots using the methods outlined above and I was just curious if I'm using the latest version of DuIK and the latest version of AFX 2020, is the expression method of extracting controllers still faster/better performance than using the master properties? I'd like the best performance, but i'm still confused about when to use the master properties vs the expression method?

thanks!

Hi,

yes, performance is still better with expressions ; Master properties have been improved in Ae2020, but they're still not as fast as expressions.

My suggestion is to test both in an empty project: import your character, put it in an empty comp and extract controllers using MPs. If the performance is enough for you, go for it!
If you feel it's a bit too laggy, try again with expression and see if the difference is significative, then you'll be able to make your choice.