State:New|TargetRelease:No Target|icon_bug|icon_katana|database:public|Resolution:None|BugID:75638|
Problem summary
When merging different EXR files into one, ExrCombine can fail for different reasons including the images to merge having different data windows. ExrCombine may crash with a segmentation fault when used outside Katana, or the render may fail within the application with a generic error message.
The errors provided should be clearer to specify what the issue is and help tracking down the cause.
Customer reported version
Katana 2.6v4
Customer reported platform
Linux
Steps to reproduce
Open the Secondary Images (AOVs) example project.
Add an additional RenderOutputDefine node into the node graph upstream of the Render node, set its type parameter to merge, select the three existing render passes as mergeOutputs, set locationType to file and specify a location for the file under locationSettings.renderLocation.
Right-click the Render node > Disk Render.
Observe that the ‘raw’ render outputs render correctly, but the render fails when attempting to write out the ‘merge’ output.
To write out a correct ‘merge’ output, the other outputs need to be of type color (set in RenderOutputDefine nodes) and can’t be tiled (uncheck driverParameters.tiled in ArnoldOutputChannelDefine nodes).
Workaround
See the following article for further details and potential troubleshooting steps: Q100384: Render fails when merging multiple channels/AOVs in Katana via ExrCombine
Expected behaviour
The specified render passes should be merged into a single EXR file.
Actual behaviour
In many cases, the ExrCombine process fails and there is no merged EXR file written out. The user is given a render error.
We're sorry to hear that
Please tell us why