Problem summary
If a Nuke 11.2 script contains a node that is cloned, when the script is saved and the comp is cleared, Nuke will crash.
This issue only appears within the Nuke 11.2 releases on all operating systems and works correctly in the Nuke 11.1 releases and prior.
This issue also occurs when the node is contained within a Group/LiveGroup or Precomp.
Customer reported version
nuke.11.2v1
Customer reported platform
centos7
Steps to reproduce
1) Open a new Nuke session within a Nuke 11.2 release
2) Create a Grade node
3) Selecting the Grade node, tap 'alt + k' to clone the node
5) Save the script
6) Use either 'clear' or 'close comp' to close the current script Result: Nuke will crash
Workaround
Unknown. Avoid cloning nodes within the Nuke 11.2 releases until this issue is resolved.
Reproduced by support
This bug has been reproduced in:
Nuke 11.2v3 - Windows 7 - CentOS 6.9 - MacOS 10.13.4
Nuke 11.2v2 - Windows 7
Nuke 11.2v1 - Windows 7 - CentOS 6.9 - MacOS 10.13.4 - regression
Unable to reproduce bug in:
Nuke 11.1v5 - Windows 7 - CentOS 6.9 - MacOS 10.13.4
Earliest version tested
Nuke 11.1v5
- This issue no longer appears in this version and has regressed
Expected behaviour
Nuke should not crash when clearing a saved script that contains cloned nodes
Actual behaviour
Nuke crashes when clearing a saved script that contains cloned nodes