When writing out an exr file from Nuke, the metadata will contain a node_hash attribute. This attribute works in collaboration with the Write nodes 'check file matches input' and 'Read from file' checkbox, to determine if any changes have been made upstream after the render was rendered.
This node_hash identifier will correctly inform the user with the following error message:
It has been discovered that when an exr file is written out, the node_hash value within the Write node itself is not written out. This in turn causes issues if there are any modifications to the Write node itself.
The underlying cause of this issue is that the node_hash value that is written out is different to the value on the Write node itself when compared.
Customer reported version
nuke.12.2v1
Customer reported platform
centos6
Steps to reproduce
1) Within a new Nuke session, create a Colorwheel node
2) Create a Write node
3) Within the Write node
a) Set a location for the file
b) Ensure the file format is .exr
c) Set to RGB (not RGBA)
d) Render a single frame
4) Once rendered, within the Write node select 'read from file' and ensure that 'check file matches input' is active
5) Alter the RGB of the Write node to RGBA
Result: Even though the state of the Write node has changed, you are not given the expected error message implying any changes have happened.
6) To confirm this is caused by different node_hash values compare:
a) The metadata value for the Write node using a ViewMetaData node (value being read back in)
b) The metadata value for the Write node using the 'i' get information shortcut (value of the Write node itself.
Result: These do not match
Expected behaviour
As the Write node has been modified, you would expect the above error message to occur, letting the user know that there have been changes made
Actual behaviour
No error messages occur, and any changes made in the Write node will not be carried downstream with the user unaware of any issues that may occur.
