I don't think you have a full grasp of what non-associative means, Sven. A non-associative light is a light which doesn't care about associations. It will illuminate everything in the scene regardless whether objects are associated to it or not. That IS the default behavior of lights in Softimage. Therefore, to show a light by default as 'inclusive' when it's actually non-associative is misleading and poor UI. To not have a parameter setting for non-associative is even worse and why I labeled it horrible because once the light is made associative (regardless of whether it's inclusive or exclusive), how can a user make it non-associative after the fact if you change your mind? You can't. You have to create a new light.
An inclusive light is a light which ONLY illuminates objects associated to it. Since no objects are associated to a light when the light is created, and objects are affected by such a light by default, the light is not inclusive and disproves your theory. Using your logic, if all lights were truly inclusive and illuminate all objects by default, then it would require all light associations lists to be fully populated with all objects in the scene at all times, and maintained when objects are added/removed from the scene. Since we can clearly see the light association lists are empty by default, your theory is again disproven. I know this feature very well, Sven. I've written many shaders that have to support it. Contrary to popular belief, light associations are actually a feature of material shaders, not lights. The associative data the user interacts with resides on the lights, but during export of the scene for rendering, the translator rewrites the association data as user data on the object. When the material shader is called, it has the responsibility of looking up that user data and deciding whether to honor it or not. That's why many custom/3rd party shaders do not respect light associations (because the shader programmer didn't know he had to do it). Matt Date: Tue, 16 Aug 2016 23:26:32 +0200 From: "Sven Constable" <sixsi_l...@imagefront.de> Subject: RE: redshift materials show gray in viewport To: <softimage@listproc.autodesk.com> There *are* three values but the third is just not translated. It's non-associative but present. The result however (an obj is illuminated by a light) is the same as associative-inclusive (in semantics this sounds illogical somehow, but it makes sense work wise). A strictly non associative light would be useless until associated, because it would be identical to associative-exclusive, no? The only case a non-associative light would make sense, is a scene where it doesn't exist. I don't'think that can happen. sven ------ Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
