Problem summary When a Merge node is created with an input in the A source and the source image in the B source, any time this Merge node is disabled, the input should no longer be calculated.
It has been recently discovered that if a roto shape is transformed and merged into the same B stream multiple times, disabling the Merge node will have no influence on the roto shape's bezier location.
Customer reported version nuke.n/a
Customer reported platform
Steps to reproduce
Open and view attached script
or
1) Within a new Nuke session, create a Checkerboard node
2) Create a Roto node, and draw a bezier around four squares in the checkerboard grid (see above)
3) Create a Merge node, connecting the Roto node into the A input and the Checkerboard into the B input
4) Add a Transform node between the Roto node and the Merge node, then alter the x and y values to 200, 200
5) Create a new Merge node under the existing Merge node, connecting the A input to the Roto node (before the Transform node), and the B input to the Merge node. (see below)
6) Disable the first Merge node and view through the second Merge node Result: Roto shape will remain incorrectly at the first Merge node location, even though its disabled
Expected behaviour When the Merge node is disabled, the Roto nodes influence should not be calculated
Actual behaviour The disabled Merge node's input is calculated and the Roto shape remains in the same position.
Workaround Unknown.
Reproduced by support This bug has been reproduced in: Nuke 12.2v5 - Windows 10 - CentOS 7 - MacOS 10.15.6 Nuke 12.2v1 - Windows 10 Nuke 12.1v1 - Windows 10 Nuke 12.0v1 - Windows 10 Nuke 11.3v1 - Windows 10 Nuke 11.2v1 - Windows 10 Nuke 11.1v1 - Windows 10 Nuke 11.0v1 - Windows 10 Nuke 10.5v1 - Windows 10 Nuke 10.0v1 - Windows 10 Nuke 9.0v1 - Windows 10 - CentOS 7 - MacOS
Earliest version tested Nuke 9.0v1 - This issue appears to be in all versions of the product
