State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:226415|
Problem summary
When an .exr Write node is downstream of another .exr Write node reading in pre-rendered frames with multiple views, then the earlier Write node's checkHashOnRead knob keeps being turned on, which causes the second Write node to fail to render.
Customer reported version
nuke.10.0v3
Customer reported platform
fedora
Steps to reproduce
1) Open the attached Nuke script
2) Open the properties for the Early_Render Write node, checkHashOnRead knob will be on, turn it off.
3) Save the Nuke script, and close Nuke
4) Open Nuke and the saved Nuke script, the checkHashOnRead knob will be on again, ignoring the Nuke script.
This is also disconnects any expressions or inputs connected to the checkHashOnRead knob.
Reproduced by support
The problem has been reproduced in:
Nuke 10.0v3 - Windows 10 - CentOS 6.7
Nuke 10.0v1 - Windows 10
Nuke 9.0v9 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v6 - Windows 10 - CentOS 6.7
Expected behaviour
For the checkHashOnRead knob to remain off, so the script can be rendered
Actual behaviour
The checkHashOnRead knob turns on when reopening the Nuke script
We're sorry to hear that
Please tell us why