Comments on: Don’t use the panel texture in a non-cockpit object.

By: Benjamin Supnik

Benjamin Supnik — Tue, 10 Jul 2007 19:23:00 +0000

Dhruv,

You are right - all of your clickabale parts need to be in ONE object.

But the whole cockpit does not need to be in one object.

Remember, you will always be stuck with only 1024x1024 of "active" texture...so merging all of the clickable parts doesn't represent a loss of active texture space.

And the "passive" parts of the panel don't have to be consolidated, so you can continue to split the cockpit to get more texture space.

(Did that make any sense?)

By: DK

DK — Tue, 10 Jul 2007 17:56:00 +0000

If we're not allowed to use the panel texture in a non-cockpit object, does that imply that we should have only one obj per plane that can be mouse-clickable?

That's a little hard when you're building an airliner and need to not only have several mouse-clickable areas, but also need to be able to texture a rather vast amount of mesh. Cramming all the texturing for a cockpit of that complexity into one 1024 x 1024 texture's basically impossible. As a result, we're almost forced to split everything up.

By: Benjamin Supnik

Benjamin Supnik — Mon, 09 Jul 2007 16:40:00 +0000

True – this is a design limitation. We’ll redo this someday – we didn’t put it in the original design to keep fps up and VRAM use low, but today’s hardware can handle it.

By: Bertrand

Bertrand — Mon, 09 Jul 2007 16:33:00 +0000

One more thing about panel texture: a panel texture don't change its luminosity with sun.

Not really useful for many situations.