I have objects which are constrained to paths. The objects move down their 
paths with a given velocity via an ICE solution. I want the objects to not be 
visible at the start and end of the path, but visible everywhere else. Manually 
keyframing visibility in this situation does not seem optimal, especially since 
the objects aren't really being keyframed.

--
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.

From: [email protected] 
[mailto:[email protected]] On Behalf Of Matt Lind
Sent: Wednesday, June 19, 2013 5:04 PM
To: [email protected]
Subject: RE: Can you see me now?

Any reason why you have to use ICE to drive visibility?  I would think the 
established toolset should suffice.


Matt




From: 
[email protected]<mailto:[email protected]>
 [mailto:[email protected]] On Behalf Of Ponthieux, 
Joseph G. (LARC-E1A)[LITES]
Sent: Wednesday, June 19, 2013 12:33 PM
To: [email protected]<mailto:[email protected]>
Subject: Can you see me now?

I've got a model hierarchy of dozens of parts under a parent object.

The parent object is animated via an ICE tree and I've added conditional 
behavior to the ice tree to affect things like visibility of the parent object 
when certain situations are met.

This is all working as I would like with one except. I'd like the visibility 
condition to propagate from the parent to the entire model.

Am I required to apply a setdata node of visibility for every child of the 
parent, or is there an easier way?

I seem to recall I would have performed  a branch key in the past, but I have 
no clue how this might translate to ICE.


--
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.

Reply via email to