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.
--
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.
If you hide the master, all the instances will be hidden too.
Matt
From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of David Barosin
Sent: Wednesday, June 19, 2013 12:54 PM
To: xsi
Subject: Re: Can you see me now?
Can you just make the model an instance and hide the instance masters?
--
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.
Any reason why you have to use ICE to drive visibility? I would think the established toolset should suffice.
Matt
--
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: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Matt Lind
Sent: Wednesday, June 19, 2013 5:04 PM
To: soft...@listproc.autodesk.com
I could yes. It’s an older asset and isn’t set up that way, but frankly that makes a lot of sense.
Admittedly what I was really hoping for, was that there was an ICE solution,. So for example instead of using:
“self.visibility.viewvis”
I could something like:
“all.visibility.viewvis”
or:
“branch.visibility.viewvis”
or:
“model.visibility.viewvis”
And the visibility parameter would just propagate through the selected object and down the hierarchy. Since it already is able to assume the selected object without a name, why shouldn’t it be able to assume the selected object’s hierarchy without a name?
--
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.