Nah, it’s not that. Paths to the reference models aren’t
changing. We do have some nested models here which I’ve found have caused some
problems, particularly with saving actions. I’ve only been here a few days and
I’ve not actually seen it happen myself. Just nosing around for now.
I don’t think nested models preserve the
<model>.<object> conventions down the nestings. That could be causing
all sorts of problems, including possible the action saving thing. That seems
like a rather obvious and unpleasant oversight to me.
From:
owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Andy
Nicholas
Sent: 02 July 2006 18:00
To: XSI(at)Softimage.COM
Subject: RE: constraints dropping off reference model components
I don't know if it's related, but we found a bug a few weeks ago
where a constraint (as you described) with an animated parameter will loose
that animation if the path of the reference model changes and the scene can't
find it anymore. The solution is to move the reference model back to where it
came from, and then change the path in the model clip to where you want to
move your reference model to. Saving the scene before you do that will loose
the animation permanently.
It was a real nasty one for us when we decided to move all our
reference models to another directory.
From: owner-xsi(at)Softimage.COM
[mailto:owner-xsi(at)Softimage.COM] On Behalf Of kim aldis
Sent: 29 June 2006 12:25
To: XSI(at)Softimage.COM
Subject: constraints dropping off reference model components
I seem to remember something being
discussed here a while back about this. An object in a reference model
constrained to another object that’s not a part of the reference model falls
off when the scene is reloaded. But only some of the time. Does anyone have any
thoughts on what the necessary parameters for a break might be?
K
