ID 497373 - Time nodes cause Nuke to display the same image in different Viewers, which are viewing different parts of the script

Problem summary
Time nodes cause Nuke to display the same image in different Viewers, which are viewing different parts of the script.

Customer reported version
Nuke 13.1v1

Customer reported platform
ubuntu

Steps to reproduce

1) Open Nuke.

2) Open the attached .nk script.

3) Split the two Viewers into separate panes, to be viewed side-by-side.

4) Click in the Viewers and notice that they will both update and display the same image.


Alternative steps: 

1) Open Nuke.

2) Create a ColorWheel.

3) Downstream from the ColorWheel, create a Transform node.

4) Set a key on the Transform's translate x and y knobs. Animate the ColorWheel across a number of frames.

5) Create a NoTimeBlur node, downstream from the Transform.

6) Create a Constant node.

7) Create a Merge node.

8) Connect the Merge's A input to the NoTimeBlur, and the B input to the Constant node.

9) Create a FrameHold and connect it downstream from the NoTimeBlur. 

10) Create two Viewers, one connected to the FrameHold and one connected to the Merge node. Your script should now look something like the following: 

11) Split the two Viewers into separate panes, to be viewed side-by-side.

12) Move to frame 10, or any frame where the Viewers should show different images.

13) Click in the Viewers and notice that they will both update and display the same image.

​

​​​


Expected behaviour
The Viewers should display the correct image, depending on where it is connecting to the node tree:

​

​

Actual behaviour
Time nodes cause Nuke to display the same image in different Viewers, which are viewing different parts of the script.

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
Nuke 13.1v1 - Windows 10 - Linux CentOS 7 - macOS 10.15 (Catalina)
Nuke 12.0v1 - Windows 10 - Linux CentOS 7 - macOS 10.15 (Catalina)
Nuke 9.0v1 - Windows 10

NOTE: In Nuke 12, the issue appears to happen more frequently when changing frames, rather than just clicking on the Viewers.

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