I am working on a large project where each room contains different lights, and I rely heavily on the LightMix manager to achieve the ideal lighting conditions. However, LightMix becomes problematic when the scene contains a high number of lights — for example, 10 rooms with an average of 3–5 lights in each.
For every room, I create a dedicated TAKE in order to store specific global lighting adjustments (sky, sun) and any additional material tweaks. For each TAKE, I would like to enable only the lights or LightSelects relevant to that particular room.
The issue is that the Multi-Pass manager does not respond to the TAKE system. It does not store which LightSelect passes are enabled or disabled. This makes it very difficult to manage LightMix per TAKE in larger projects.
Please consider adding support so that Multi-Pass settings (including LightSelect visibility) react properly to the TAKE system.
This improvement would significantly streamline workflows for large, multi-room scenes.
If this is still valid - I wanted to set up a new idea in the Ideas Portal based on this, but I am not sure if I understand it correctly. Can you clarify if:
You would like the “Setup interactive LightMix” button to generate LightSelect passes only for the lights which are visible in the current Take? So for example, in your Take you hide lights in room A and leave lights in room B, then set up LightMix, and you end up with LightSelects only for room B lights.
or
You would like to be able to create different Takes with different LightSelect passes enabled/disabled. So you could add all LightSelects for all lights (room A and B) and then set up Take A where only room A LightSelects would be enabled and room B LightSelects disabled, and Take B where room A LightSelect would be disabled and room B LightSelects would be enabled.
Originally, I meant the second option, where different LightSelects would be set up for Room A and additional LightSelects for Room B, and depending on which Take (A or B) was active, I would manually enable or disable the corresponding LightSelect.
However, your idea in the first option would save work and prevent situations where I might forget to manually switch a LightSelect on or off. So Variant 1, as you described it, would be the better solution. I would simply create separate LightSelects for Room A and Room B, and if, for example, the lights in Room B were hidden or disabled, they would automatically be disabled in the corresponding LightSelect as well. This would prevent rendering passes for inactive lights.
Variant 1, “Setup Interactive LightMix,” would definitely be the better choice.
I have logged this idea at Chaos
Please note that it won’t be visible until it is approved (or declined) by product management. Once it’s visible, feel free to vote for it.
Actually, if you hide lights, you can use this workflow, unless I am missing some important part of your workflow. Please check the attached video.
So you set up Take A where only lights in room A are visible and Take B where only lights in room B are visible. You go to Take A and set up Lightmix > this results in LightSelects only for lights in room A. Isn’t this exactly what we discussed in the previous messages?