We’re seeing this pest again and can’t seem to shift it.
vray_adv_37001_max2019_x64
max 2019 3.4
windows 10
even checked color correct versions even though the scene isn’t using it
other scenes render ok on this setup so the issue is file related
all paths are UNC and we’ve checked the nodes can see a license
The slaves are continually rendering bright areas just a little darker.
Tried Motion blur on/off/ embree on/off overide material on/off max ray intensity on/off, sub pixel on/off clamp on/off gamma 1 or 2.2 in colour mapping
running brute force, tried changing bucket size
Any ideas on what to check? Whatever it is it’s consistent
The file had the max Enviroment to use Linear Exposure Control.
Setting this to No Exposure Control made all buckets the same.
Thought we’d leave this here for others. @vlado might advise on why this isn’t sent to DR slaves and if it’s fixed on newer versions which are being developed still
Unfortunately for me this does not fix the issue. It’s been affecting my render passes in a lot of different ways. I render in bucket and there may or may not be a difference in butckets for the slave and main unit. Sometimes the RGB looks fine and then the Zdepth, RenderID, diffuse filter or whichever pass is messed up. A lot more often than not at least one thing is wrong. It results in gamma/color difference when it’s RGB/Effect Result but for the other passes it results in just plain black / what it should be. This has started happening about 2 weeks ago and it’s getting rather problematic.
I hope someone could explain / investigate what’s going on because this is starting to be a real problem for me.
Ensure there are no warning in the log, and if there are address them (f.e. incompatible maps or materials, with the scene converter.).
If the problem persists, you may want to send a scene to investigate, and some more details, to support.
@VanWijnenVR , to add to Lele’s comment: can you share your V-Ray/host platform versions? Are you sure you’ve got the same service packs on all your slave machines? Have you got any screengrabs demonstrating the issues, or can you show us what the passes look like?
Best would be to forward a scene to support@chaosgroup.com (make sure to mention this thread in the email) so we can try and reproduce this in our environment.
Ok, so if it’s a massively Referenced scene, you’ll want to run a v-ray scene conversion on each of the incoming material.
It ought to simply be Open->Convert->Save: no biggie, time-wise, and with no need for user input.
If any xRef had incompatible nodes (say, very old stuff), you’d run out of luck quickly.
and if it’s fixed on newer versions which are being developed still