If an ICE tree executes while any components of the mesh are selected, the
entire stack will execute twice. (SI2013)
When this happens, none of the data from the first pass is reset.
This generally isn't much of a problem, unless parts of your tree only
initializes a value after checking that it has not already been set.
First pass: Value not initialized. Setting to 0.
Adding 1. Output: 1.
Second pass: Value initialized. Leaving at 1.
Adding 1. Output: 2.
Gif of behavior: https://gfycat.com/HauntingDecisiveKoalabear
It would be nice to know if this issues exists in later versions of
XSI, but I don't have very high hopes.
I am adding ICETrees as operators, with each individually having to
check whether to use the
value set by the previous operator (if it exists), or load the base
value from an external source.
The only workaround I can think of is to leave an ICEtree at the top
(bottom?) of the stack dedicated to loading the base data,
rather than relying on the operators to check themselves. It wouldn't
be a very pretty solution, and someone is bound to
delete it by mistake and break everything.
Penny for your thoughts?
------
Softimage Mailing List.
To unsubscribe, send a mail to [email protected] with
"unsubscribe" in the subject, and reply to confirm.
