Skip to main content
D
dgregowich
Known Participant
May 21, 2020
Answered

Moving DUIK controllers back to original comp

  • May 21, 2020
  • 2 replies
  • 3385 views

Hi,

So I've rigged a character with DUIK Bassel in a comp and extracted the controllers into another comp. I did all the animation of the character in this comp, but the character has a skirt and to animate the skirt I need to go back to the 1st comp, but this comp doesn't have the controllers with the keyframes now. (Somehow there are still controllers in here, just not the keyframes). So I can't see the animation timings to animate the skirt accordingly.

Is there a way to move the controllers back to the 1st comp with all the keyframes intact? Or another way I can sort this out?

This topic has been closed for replies.
Correct answer Martin_Ritter

I didn't made good experience extracting the controllers (there have been updates on that, maybe it's better now) and I try to avoid it.

Carefully copy the keyframes back to the in-comp controllers. If they are not there anymore, copy the controllers back into the comp. You'll have to edit the expressions on the rig, since it still referres to the outside controllers. I think the best workflow is to delete the outside-controllers and than solve every expression error. Make a backup copy of your project, you can easily screw up your work.

 

Therefore, I would just open both comps on top of each other and animate the skirt inside, while the controllers of the rig are still outside. If it's just about timing, it's just a matter of your workspace. I'm doing this all the time: voice over is in main comp, but I'm animating 3 or 4 hierachry steps into it. Timing is not an issue, the CTI updates over all comps simultaneously.

 

*Martin

2 replies

Martin_Ritter
Martin_RitterCorrect answer
Legend
May 21, 2020

I didn't made good experience extracting the controllers (there have been updates on that, maybe it's better now) and I try to avoid it.

Carefully copy the keyframes back to the in-comp controllers. If they are not there anymore, copy the controllers back into the comp. You'll have to edit the expressions on the rig, since it still referres to the outside controllers. I think the best workflow is to delete the outside-controllers and than solve every expression error. Make a backup copy of your project, you can easily screw up your work.

 

Therefore, I would just open both comps on top of each other and animate the skirt inside, while the controllers of the rig are still outside. If it's just about timing, it's just a matter of your workspace. I'm doing this all the time: voice over is in main comp, but I'm animating 3 or 4 hierachry steps into it. Timing is not an issue, the CTI updates over all comps simultaneously.

 

*Martin

    D
    dgregowichAuthor
    Known Participant
    May 21, 2020

    Thank you! 

    "Therefore, I would just open both comps on top of each other and animate the skirt inside, while the controllers of the rig are still outside. If it's just about timing, it's just a matter of your workspace. I'm doing this all the time: voice over is in main comp, but I'm animating 3 or 4 hierachry steps into it. Timing is not an issue, the CTI updates over all comps simultaneously."

     

    I thought this would be the case, but it didn't update over both comps, I wonder if i did something wrong while extracting about the master properties or something. I tried copying the controllers back to the 1st comp but it sent everything haywire, but copying the keyframes worked. I'm very new to Duik, and still learning as I go along the project - even though the tutorials make it look all too easy, I guess there will be a lot more trial and error. Thanks for your help!

    Mylenium
    Mylenium
    Legend
    May 21, 2020

    Nothing stops you from using simple copy&paste to carry over the controllers. Everything else would likely require extensive manual editing of the DUIK code to chnage the references in the expressions themselves, but it's really not clear how your project is actually rigged from your somewhat vague and confusing description.

     

    Mylenium

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices