Conditional Visibility

aerogator · Post by **aerogator** » 19 Jun 2008, 15:22

Hey guys, I've been thinking about conditional visibility because of a model I'm working on, and wondered if it would be possible to make an entire model visible/invisible? Reason being, you could have a bunch of a/c parked in hangers that would become visible only when time for taxi-out and take off, hence not wasting computing power. (Of course this is all based on whether the computer still draws the invisible part, which I don't know

) I know we all like to see a lot of parked aircraft, but I also know, especially with GA airports, there are a lot more aircraft there than you can see.

This all may not even be necessary or even possible but I thought it might be worth discussion.

Weescotty · Post by **Weescotty** » 19 Jun 2008, 18:16

You could try using the TIMEOFDAY XML option perhaps.

Of course all parts would need to be tied to a single poly/part that has the condition applied to it.

Firebird · Post by **Firebird** » 19 Jun 2008, 18:50

Just for info sake, wouldn't an object still be rendered even if its invisible?

I realise that Jake is asking about the feasibility of something, rather than the narrow question I am asking. I am just curious about the answer.

aerogator · Post by **aerogator** » 20 Jun 2008, 11:24

wouldn't an object still be rendered even if its invisible?

Actually, thats the crux of this whole premise.

Does anyone know the answer?

RipPipPip · Post by **RipPipPip** » 20 Jun 2008, 12:52

My vote is that invisible parts (or model itself) is NOT rendered when it's invisible.
As simple as that

PS. Here's an argument:
this is the reason why M$ did c_wheelwell hierarchy variable, which is built-in.
You attach every central gear part to this variable and they all disappear when the gear is up - not to be rendered during all the flight!

aerogator · Post by **aerogator** » 20 Jun 2008, 15:02

this is the reason why M$ did c_wheelwell hierarchy variable, which is built-in

Could you elaborate on that oh "Holder Of All Knowledge"

. I have never heard of this. Where might I find some more info?

Dark Morelia · Post by **Dark Morelia** » 20 Jun 2008, 17:08

I've been told they don't use any extra resources, and some testing seems to confirm this.
I'm hoping it's true anyway :p

Weescotty · Post by **Weescotty** » 20 Jun 2008, 17:24

c_wheelwell, l_wheelwell and r_wheelwell are built in names for parts, the same as c_gear, l_gear and r_gear.

You get to them the same way as you usually get part names, but choose "Visibilty" in the drop down menu.

They are not rendered when the gear is up.

aerogator · Post by **aerogator** » 20 Jun 2008, 18:11

so I link all parts that I don't want to be rendered when the gear is up to the c_, l_, r_wheelwell(s)? Do I just make the before-mentioned wheelwell parts the parent part?

Thanks,

Weescotty · Post by **Weescotty** » 21 Jun 2008, 10:24

aerogator wrote:so I link all parts that I don't want to be rendered when the gear is up to the c_, l_, r_wheelwell(s)? Do I just make the before-mentioned wheelwell parts the parent part?

Thanks,

Yup, just make the parts childs of the wheewell parts.

RipPipPip · Post by **RipPipPip** » 21 Jun 2008, 10:36

...you can use other custom part as a parent part as well.
That one custom parent part may have custom visibilty XML condition attached.