The fact that they don't follow naming down the hierarchy is enough in
itself for me. Consider ModelA with ModelB and ModelC under it. What happens
if both ModelA and ModelB have an object named 'null1' under them. That's
going to screw all sorts of things up. I wouldn't go near them no matter
what.
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> Behalf Of Bernard Lebel
> Sent: 03 July 2006 05:21
> To: XSI(at)Softimage.COM
> Subject: Re: constraints dropping off reference model components
>
> > > Also, when dealing with saving actions and the likes accross nested
> > > models, I once or twice noticed that the "lowest" Mixer (the one of
> > > ModelB for example) would "copy" itself onto all parents that are
> > > models. Messy. Not sure if this is still the case in XSI 5.11
> though.
> > [kim aldis]
> >
> > In 5.1 and 5.11, any nested models don't have any of their objects
> > stored in the action. They're completely left out. AARRGGHH!!!!
>
> Oh, ouch....... one more reason not to use nested models.
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
> body:
> unsubscribe xsi
>
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
