Open Tim1022 opened 4 years ago
Hi, and thanks for the suggestion.
I've thought a lot about that already...
it's quite complicated actually, because extracting only some controllers, you'd lose the relations between them... So to keep everything working, there would be a need for some links to their parents in the precomp anyway, links which would have to use master properties too. So that won't change much for your issue.
The problem actually is that master props were not meant to be used like that, and there are a lot of peformance issues with them, and even also scripting issues as the scripting interface is still very incomplete for them. The only solution I see is to keep the pressure on Adobe to finish these.
Hi Duduf
Thanks for providing this amazing tool case for us.
I had an issue when I want to extract the controllers by using master properties. Actually, it's not an issue, it can be called workflow optimizing suggestion.
So, basically, when I extract the controllers from the nested comp, it extracts everything, which is fine normally.
However, when I have a complex rigging with a whole body, 2d sliders, etc, it will load all corresponding properties to essential graphics panel. Then, when I drag this comp to a new comp, it freezes and crashes eventually...... I think it's due to the massive properties it has to load in the master properties list.
So, my question is, is it possible to specify the controllers I want to extract and let Duik only extract those ones rather than everything?
Hope it's not a complex one, haha.
Thanks