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.
Usually, the part after VRayExtraTex (in your case “_AO”) is the name of the map; when no map is selected the name is VRayExtraTex. Maybe there was an issue with the particular VRayDirt? Does it have maps attached? Is it happening locally? A quick solution may be to simply use the VRayAO element.
It was strange cause it rendered fine on ~10 machines, only two machines added the suffix. (They all had the same v-ray version number in the .exr metadata)
We’ll probably stick to VRayAO from now on. Just wanted to check if this was a know issue
The name of the extratex map (in your case “AO”) is automatically appended to the render element name *at render time*.
However, if the render element name is manually edited, there won’t be any automatic renaming (see attached).
Please keep an eye out for this re-happening, in which case we’d likely want more details on the setup.
