This happened a couple weeks ago. Created a light with a bitmap in texture slot. Production CUDA (CPU & GPU) render. Used light mix on this light and other lights. Then “to scene” to save light settings.
2 attached images show light before & after corrupted light mix.
File then became excessively slow to open, and render, a several minute pause.
To fix temporarily, I deleted the affected lights, importing the file into a clean Rhino file, remade the lights, then didn’t use light mix when I have textures in any light slot. File then rendered fine.
The same situation occurs when I used procedural noise “B” in the texture slot (simulating a disco ball light effect on walls & floor).
Shown light is rectangle, also corrupts with spotlight.
Excuse us for the delayed response!
The described from you is reproducible on CPU too and also with V-Ray 6.
I have logged it in our bug tracking system with VRW-3910 number for further investigation.
Please confirm that the shown scenario is happening after clicking over To Scene more than once - every next click is creating the new nested Mix (Operator).
According to my tests this is happening.
@tsvetomira.girginova ,
Thank you for the reply.
Yes, every time you click “to scene” the nested mix is created and grows.
I recently switched to Vray6, so thanks for the heads up.
As a workaround (with a texture light), I can use light mix, without clicking to scene, instead manually adjust the lights.
Glenn
Our dev team will look at this.
This nested Mix (Operator) could be seen also in Textures, since it’s created also for the Environment texture.
Еven though it affects the UI, the values are properly translated from Light Mix to V-Ray Asset Editor.
But we understand that it is a disadvantage and requires more clicking - you have to be precise where are you adding changes, will they apply to the texture etc.