Problem summary:
RotoPaint nodes can cause the Viewer and Node Graph to be one step behind and not update properly.
Customer reported version:
Nuke 13.2v6
Customer reported platform:
Windows 10
Steps to reproduce:
1) Open Nuke and create a CheckerBoard node in the Node Graph.
2) Add a RotoPaint node and then a Transform node.
3) View the Transform node, and select the Brush tool from the RotoPaint menu bar.
4) Paint a stroke, but when your cursor is over the Transform Overlay, press the Ctrl/Cmd key without releasing the mouse.
5) Observe how the Viewer and Node Graph behave:
Expected behavior:
The Viewer and Node Graph should update consistently, and always display the latest information.
Actual behavior:
The Viewer and Node Graph can become one action behind after using the RotoPaint node, and this can take on a few different forms:
1) Disabling nodes becomes sticky, and you have to click in the empty space of the Node Graph to see if it's enabled/disabled.
2) The Viewer won't update automatically, and you have to either toggle the 1 and 2 keys, or create a new node.
3) The labels of new nodes don't update correctly and only display the node's Class. For example, a Blur node is labeled Blur instead of Blur1, and a Merge node is labeled Merge2 instead of Merge1.
These behaviors can be triggered with other interactable overlay elements, like the Crop node for instance, and other RotoPaint tools, like Clone, Blur, and Bezier.
Additionally, this problem can also be triggered by rapidly alternating between painting and undoing strokes, but this is much more inconsistent than the reproduction steps above.
Workaround:
The issue seems to be resolved after closing the RotoPaint node's Properties bin, reopening it, and painting another stroke. Additionally, clicking inside the Viewer window will sometimes complete the brush stroke and allow Nuke to catch up.
It has also been observed that creating a Roto node and making a closed Bezier shape in the Viewer can restore the Viewer and Node Graph back to working order.
Otherwise, the Nuke session must be fully closed and the file reopened.
Reproduced by Support in:
Nuke 14.0v3 - Windows 10, CentOS 7
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10, CentOS 7
Earliest version tested:
Nuke 10.0v1 - This issue appears to be in all tested versions of the product
