Objects move when I add a null object or DUIK controller

[PeteFalcon]

Bit of a vague question but I'm hoping this might be a quick answer for some.

I have a character animation rig made up of photoshop layers. I have the body part layers parented with anchor points at the joints, and use DUIK inverse kinematics to create joint movement/flexing/walking. The DUIK script puts expressions on the position and rotation properties.

So I have my full rig created and my puppet walking across the screen. But I'm experiencing an issue where, when I add a Null object, or a Duik Controller, upon creation of that object, it slightly shifts my rig somehow. It's as if I took the master controller and shifted it over a few pixels. This appears to be happening regardless of which layer I have selected when I click to create the null object.

Super vague I know but does anyone have any idea why this might be happening? Or what to check?

Thanks

[David Arbor]

Are you properly naming all of your layers and Puppet Pins? I believe Duik Bassel (version 16) addresses this, but when you have pins and layers that have the same name, adding new controllers or layers that are connected to other layers with the same name causes issues because you can have expressions that reference something called "Puppet Pin 1," but you have to pins with that name.

Please post a screenshot of your full timeline and rig (with all the hidden layers showing).

Also, please list out the exact details of what and why you're adding the null and controllers. Between that info and the screenshot that will give a clearer picture of how your rig works.

[PeteFalcon · Accepted solution]

I found that it has to do with the indexes of the layers.. somewhere in my expressions there must have some kind of layer index reference (when I say "layer index" im referring to the ID number of the layer which counts the number of layers, or number of layers from the top, don't know if this is the correct jargon). the problem was happening when i created a new layer thus changing the index of all the layers below it. Still dont know where in my expressions the index reference was but now I know how to resolve/avoid. thanks

[David Arbor]

Oh, yes, if you were using the index to reference a specific layer, that's a bad idea for exactly the reason you said. You can always pickwhip to a specific layer if you need a hard connection