[Bf-funboard] Re: Flash, Layers & Max (Lamps)

[Thorsten Wilms]

On Tue, Jan 06, 2004 at 05:27:58PM -0500, Paul Lunneberg wrote:

> About Lights:
> I had another thought but along the lines of how the lights work.  I would love
> to have the ability to have more control over what a light does or does not
> illuminate as well as casting shadows from/to.  Max does it with editable lists.
>  Edit the list and add the group or object and tell the lite to include or
> ignore objects on the list.  Much better control wise for lights than just using
> the layer controls.  You may need a light to only work on several objects in 2
> different layers but not the other objects in those layers... which currently
> you would have to have those 3 objects on their own layers by them selves but
> would then conflict with your layer organization.
> Just an idea.  There may be another way to handle this but the list way would
> seem pretty straight forward and simple.

I listed it as a problem on my page about grouping/visibility management, 
that selective lighting and visibility management is currently tied 
together. Same thing with env-maps.
One of my basic ideas is, that the whole "layer" thing is about savable 
selections and assigning properties to all memmbers of a selection (group) 
at once, what reminded of inheritance.
Thats why I'm thinking about having 1 mechanism to handle all (or most) 
kinds of savable selections.
For selective lighting and similar things there could lists of groups 
which members will receive light exlusively or that will be excluded
(exclude/include lists, giving 1 the priority would allow to have both).
But with a single group manager, those groups propably only set up for 
selective lighting would show up, ready to be used for visibility 
management, and having a timeline(?). A fast way to hide or view the members 
of such groups will be very nice. But with the same objects in several 
lists, one has to think about how visibility management should be handled 
in detail (WIP).


---
Thorsten