Hi there,
We have ran into a weird issue, which we are still trying to sort out with another 3rd party vendor. But the behavior was that local renders would look different from farm renders. After a while, we could narrow it down to some lights changing their color values upon the run of customize.ms. It was due to the resetting of a property, of which the value did not actually change (as in, it was zero, then deadline customize.ms set it to zero again). Somehow a trigger on that value changed the colors. Anyway, we have patched our version of customize.ms to only set a value if its actually different from whats in the max file, and wanted to pass this on to you guys as well.
cheers
laszlo
Thanks Laszlo. What setting are you referring to?
one of the vray props:
options_rgbColorSpace = 0
Thanks Laszlo. I think it might be best if we just comment this setting out in our shipping customize.ms file if it is known to cause an issue and simply respect the setting in the 3ds Max scene file. There are a number of other settings in V-Ray where we ignore for this reason as well.
Might be, i’ve reported to Vlado.
In our patched version, we simply skip setting of values, unless the new value is different from what the parameter is set to already.
Hmm…I’ll log this as it feels like a better approach to handle these situations. We could potentially also report what other settings have changed as a result of changing one or more properties in the renderer, which might be nice to help track and narrow down a problem. Thanks!