-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating imported instance from original rigging changes (workaround) #36
Comments
Comment by Nico-Duduf Thanks for your feedback, I'll have a look at this. I think there is indeed something to be scripted here |
Comment by JuanGarces Yes, I also thought that scripting would be applicable but that is far away from my skills. Please, let me know if you make it happen. |
Comment by JuanGarces I've just found a problem with my procedure: |
Comment by Nico-Duduf I'm thinking of several ways to update a rig after it has been animated. Maybe you can test that using the copy/paste animation tool of Duik ; copy the animation before deleteing and reimporting the rig, then just hit the paste button. |
Comment by Nico-Duduf (or you could simply follow your procedure, but instead of deleting the new controllers, copy and paste the animation from the old controllers to the new ones, and delete the old controllers) |
Comment by JuanGarces It almost worked. The animation itself is fine but it didn't copy some "loopout" expressions I had. I don't know if I did something wrong. |
Comment by Nico-Duduf No you didn't, the copy/paste animation tool does not copy expressions. But that's something it should optionnally do, I'll add this to the next version! |
Comment by JuanGarces I'm looking forward to it. Thanks! |
Issue by JuanGarces
Thursday Mar 10, 2016 at 01:48 GMT
Originally opened as https://github.com/Rainbox-dev/Duik-15/issues/204
Hi, I'm new and I didn't find a better solution when I make changes in the original rigging and I want my animation to be updated with them (like adding a new layer or modifying the puppet mesh). Please, tell me if there is a easier way instead of what I did:
Is there a better way to do it? Thanks in advance.
The text was updated successfully, but these errors were encountered: