while on the subject, I wanted to vent a little.
untill now I never had problems with adding instances inside models.
but on this job, it suddenly turned all weird.
i've got something like:
-- model
\- objects
\- null
\-instances
\- model to be instanced
\- object
the model node and the objects have srt animation, as well as the instances.
the master has none.
i've had several unspeakable things happen, on reopening the saved scenes.
some of them were:
"rogue instances" appearing on the scene root level,
the instance master automagically getting duplicated, each with an instance
group with all instances in there.
"instances becoming offset towards their nulls" - this freaked me out
completely, since you cant even do this if you'd try by hand.
and XSI crashing when deleting rogue instances, or one of the duplicated
masters, or changing anything to the instance groups.
total mayhem. Trying to correct the errors was just allways leading to a
crash.
I solved it by taking an older scene, and putting the instance master and
objects outside of the model, and placing them on scene root level.
No weirdness happening. But here's the thing: I have another model in the
scene, with a very comparable structure, with instances in there and
instance master, and there's no problem at all.
(I ll see if I can get all job related stuff out of the scene and send it
off to support, but Im not sure I can do that.)
To cut things short,
I would like to be able to avoid making models out of the masters, and
simple putting objects in a group, and selecting this group to create
instances, very much like it works with particles. and with control over
wich source object gets assigned to which instance, with a property or index
orso.
Being forced to make models out of the masters complicates the scene
structure unnecessary in my opinion, and can lead to problematic situations.
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
