Consider a model as anything other than a name space and a top level host for mixers and deltas and you are half way down the road to madness and picking up speed. Models are made to be created when you need a definite name space, or isolate a mixer/delta, and be hidden and left alone ever after.
That's the beginning and the end of it and has always been that way in the small secret club of people trying to stay sane :p Have a consistently named "input" item for each model/namespace/component to host graphs that are supposed to hop around different items (assuming you don't mind, or simply can't avoid efficiently, the performance hit of a graph with multiple outputs and corresponding excessively frequent pulls). On Fri, Jun 21, 2013 at 3:06 AM, Ponthieux, Joseph G. (LARC-E1A)[LITES] < [email protected]> wrote: > Eric, > > Thanks. I guess now I am confused. I always interpreted Model as a > toplevel parent. If I understand this right the practice is to have a > transform group underneath the Model and the rest of the hierarchy > underneath the transform group? All animation is then performed at the > transform group and below while the model is nothing more than a "mini > scene" container and kinematics at model level are ignored. Is that a > correct assumption? > > -- > Joey Ponthieux > LaRC Information Technology Enhanced Services (LITES) > Mymic Technical Services > NASA Langley Research Center > __________________________________________________ > Opinions stated here-in are strictly those of the author and do not > represent the opinions of NASA or any other party. > >
