That's more or less true for any pull only DAG in regards to multiple outputs, SCOPs in example (or any op really) will do the same. The issue is some times you have to do it that way when order of execution gets really dodgy and you need to rule a certain way. I'm still waiting in trepidation for the day we'll be able to set a preferred order of eval/eval sort in ops. Been asking for that since Moondust :)
On Wed, Feb 6, 2013 at 2:07 PM, Ahmidou Lyazidi <[email protected]>wrote: > Also you might not write kinematics for multiple objects in the same > graph. > If you do so, the whole graph is executed for each affected object and > performances will be exponentialy slower. > > Ahmidou Lyazidi > Director | TD | CG artist > http://vimeo.com/ahmidou/videos > >
