ID 148627 - Precomp nodes have a "file does not match input" error when rendered with OCIO color management

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary:
Precomp nodes have a "file does not match input" error when rendered with OCIO color management.
 
This issue only affects .exr files.
 
Customer reported version:
Nuke 14.0v3
 
Customer reported platform:
CentOS 7
 
Steps to reproduce:
1) Launch Nuke and create a CheckerBoard node in the Node Graph. 
2) Create a Write node and set its file path to an .exr, like /tmp/test.exr
3) Save the Nuke script, name it something like "simple_comp.nk", and close Nuke.
4) Open Nuke again, and navigate to Edit > Project Settings...
5) In the Color tab, change the color management from Nuke to OCIO


6) Create a Preomp node in the Node Graph, and load the simple_comp.nk file.
7) Click the Render button, and render one frame:

6) View the Precomp node, and observe the "Cannot read from file; file does not match input" error message:

 
Expected behavior:
No changes were made between rendering and reading the .exr file from the Precomp node, so it should match the input and not have an error message.
 
Actual behavior:
The Precomp node reports that the .exr on disk does not match the input, and nothing is displayed.
 
Workaround:
Inside the Precomped file, in this case simple_comp.nk, enable the Write node's raw data checkbox:

 
Alternatively, disable the Write node's check file matches input checkbox.
 
Reproduced by Support in:
Nuke 14.0v3 - Windows 10, CentOS 7
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 10.0v1 - This issue appears to be in all tested versions of the product

    We're sorry to hear that

    Please tell us why