Hi
We've encountered a strange bug, we have a extra tex render element to output vray dirt as a AO pass.
It's saved as "VRayExtraTex" with the rest of the render elements in a VRay raw .exr
But two computers save the element as "VRayExtraTex_AO" making Fusion/Chaos player unable to read the data from the .exr on those frames.
We've only submitted this job once to backburner so I don't think its a "cached" file that's messing it up.
Is this something that's been seen before?
I think I'm going to do some re-installs on the computers that had the issue, see if that helps.
We've encountered a strange bug, we have a extra tex render element to output vray dirt as a AO pass.
It's saved as "VRayExtraTex" with the rest of the render elements in a VRay raw .exr
But two computers save the element as "VRayExtraTex_AO" making Fusion/Chaos player unable to read the data from the .exr on those frames.
We've only submitted this job once to backburner so I don't think its a "cached" file that's messing it up.
Is this something that's been seen before?
I think I'm going to do some re-installs on the computers that had the issue, see if that helps.
Comment