ID 361035 - Cloned nodes can delete nodes and cause corruptions within Nuke scripts

Problem summary
When opening a Nuke script that contains multiple clone nodes, users can encounter an issue that corrupts the script itself and can delete a portion of the nodes from the script.

From further testing the below message (or a variation), is generated within all operating systems:

​

For example, you may see a "blank error message" instead:

 

Customer reported version
Nuke 14.1v5
 

Customer reported platform
Windows 10

 

Steps to reproduce

1) Open affected Nuke script

Result: You should receive the following error message or similar:

OR:

1) Open Nuke.

2) Create a Grade node.

3) Clone the Grade node (Alt+K).

4) Add the cloned Grade node to a Group (Ctrl+G).

5) Copy paste both the Grade and Group node.

Result: You should receive the following error message:

If you open the copied Group node, you should see that it only contains an Input node.

 

Expected behaviour
Clone nodes should not be corrupting scripts and deleting nodes

Actual behaviour
Clone nodes are corrupting scripts and deleting nodes

 

Workaround

1) As the cause may be related copying cloned nodes between scripts, we would suggest copying cloned nodes between scripts as a precaution. As an alternative, we suggest to de-clone the node first before copying into a new script.

2) As the error message itself relates to the object id of the corrupt clone node, the suggested workaround is to remove the corrupt cloned node at a text-based level, before the script is opened in Nuke.

To do this:

a) Open the corrupt script in Nuke

b) Take note of the corrupt object id, through the error message. For example 'C5d4d82a0'

c) Duplicate the Nuke script and rename to avoid overwriting the original Nuke script.

d) Open the duplicated .nk script within a text editing application.

e) Within the text editor, use the search function to locate the object id, 'C5d4d82a0'

e) Select from the start of clone through to the last closing bracket, after selected false in the above example.

f) Delete this selection of the script, taking care not to delete anything outside of the above selected clone node.

g) Save and close the revised script from the text edit application, ensuring that the extension remains as .nk

h) Open the newly revised Nuke script in a new Nuke session

Result: This will remove the corrupt cloned node and not delete the nodes that have been removed as a result of the corruption.

Note: If you receive another error message in relation to another object id, please continue through the steps above again until the script opens without error.

 

Reproduced by support
This bug has been reproduced in:
Nuke 15.1v2 - Windows 11
Nuke 11.2v3 - Windows 7 - Centos 6.9 - MacOS 10.13.4
Nuke 11.2v1 - Windows 7
Nuke 11.1v5 - Windows 7
Nuke 11.1v1 - Windows 7
Nuke 11.0v4 - Windows 7
Nuke 11.0v1 - Windows 7
Nuke 10.5v7 - Windows 7
Nuke 10.5v1 - Windows 7
Nuke 10.0v6 - Windows 7
Nuke 10.0v1 - Windows 7
Nuke 9.0v9 - Windows 7
Nuke 9.0v1 - Windows 7
Nuke 8.0v7 - Windows 7
Nuke 8.0v1 - Windows 7
Nuke 7.0v10 - Windows 7 - Centos 6.9 - MacOS 10.13.4

Earliest version tested
Nuke 7.0v10
- This issue appears to be in all versions of the product