ID 502179 - Expressions cause nodes to not be saved when a Group's node uses an expression which checks for nuke.dependencies of the parent group with a Write node downstream of the group
Problem summary Expressions cause nodes to not be saved when a Group's node uses an expression which checks for nuke.dependencies of the parent group
The contents of the group won't be saved, and if the node which is expression links to the group doesn't have a node down stream, the expression linked to node can also not get saved. This can cause data loss from Nuke scripts.
This only seems to happen if there is a Write node down stream of the Group node which contains the expression checking node.
Customer reported version nuke.13.1v1
Customer reported platform centos7
Steps to reproduce
Trouble_Group node's contents not saved:
1) Open attached Scene_no_env.nk Nuke script, the Trouble_Group node has nodes inside it
2) Make a Grade node in the script, disconnected from any other nodes
3) Save the script
4) File>Clear
5) Open the Nuke script and check the contents of Trouble_Group, it is now empty:
Missing_Group not saved and Trouble_Group node's contents not saved:
1) Open attached Scene_no_env.nk Nuke script, there is a group node called Missing_Group
2) Detach the Security_NoOp from the Missing_Group node
3) Save the script
4) File>Clear
5) Open the Nuke script, the Missing_Group node is now missing and check the contents of Trouble_Group, it is now empty:
Expected behaviour For the nodes present in the node graph to be saved
Actual behaviour The nodes were not saved, causing data loss.
Workaround Press Save twice set Lazy Expressions to Always in Edit>Preferences...>Performance>Expressions>Mode
Reproduced by support This bug has been reproduced in: Nuke 13.1v2 - Windows 10, CentOS 7, macOS 10.15 Nuke 12.0v1 - Windows 10 Nuke 9.0v1 - Windows 10, macOS 10.15
Earliest version tested Nuke 9.0v1 - This issue appears to be in all versions of the product
