Lightmixer AOL

[HHbomb]

Not very easy to use... Can't even see the values

[paride4331]

Hi HHbomb,
I can't tell if this is something specific to a particular node, I haven't been able to reproduce the issue. Do you happen to have any custom interface settings, a specific screen resolution, or anything else that's been customized?
Regards
Paride

[remKa]

It would be very nice to have a simple click solution to access the lightmixer

[HHbomb]

@Paride. I'm on 3dsmax 2022.3 , even in new empty fresh scene I get the same ugly window...

[paride4331]

@Paride. I'm on 3dsmax 2022.3 , even in new empty fresh scene I get the same ugly window...

Hi HHbomb,
Which version of the plugin are you using?
Regards
Paride

[HHbomb]

Hi Paride ! I was using 2026_3 and I just install 2026_4 to test : it is the same.

Now, as you implying that it's my fault, I just verify one thing.... And it is my fault !!!
I have "Activate Values Texmaps" set to all... when I set it to never I get the Nice Lightmixer AOL window...

[paride4331]

Hi Paride ! I was using 2026_3 and I just install 2026_4 to test : it is the same.

Now, as you implying that it's my fault, I just verify one thing.... And it is my fault !!!
I have "Activate Values Texmaps" set to all... when I set it to never I get the Nice Lightmixer AOL window...

Hi HHbomb,
I'm happy the issue has been resolved!
Regards
Paride

[Elvissuperstar007]

You already have the best example of how this feature should work — Corona Renderer. With a single click, you can create a LightMix for all light sources, individual lights, or organize them into groups. Everything should be designed to simplify the workflow, rather than forcing the user to manually click and assign a Light ID to every object in the scene.

Just one button that automatically analyzes the scene, creates all the necessary Light IDs, and immediately provides a ready-to-use list. The user should not have to manually assign a Light ID to every object.

[remKa]

It would be indeed a marvelous time saver !

[Elvissuperstar007]

Another point that would be technically very simple to implement is giving users the ability to rename Light ID layers.

Why should the user constantly have to guess which light source they are editing and what each ID is responsible for? This is simply not practical in a real production pipeline. Production workflows rely on standardized processes and clear naming conventions precisely to avoid this kind of endless chaos.

The user should be able to rename each light source layer, for example:

Light ID 7 → Kitchen Ceiling / Window Light / Exterior Fill / Night Light

Instead of having to work with meaningless Light ID 1, Light ID 2, Light ID 7 labels and constantly remember which light corresponds to which number, users should be able to assign meaningful names to them.

This is a small change that would significantly improve usability and make LightMixer much more practical for a real production pipeline.

Please give users the ability to rename Light ID layers instead of forcing them to work with anonymous numbers.