ID 494776 - When returning to the Timeline from the Node Graph, after saving a comp, some shots can not be displayed in the Viewer

Follow

Problem summary
When returning to the Timeline from the Node Graph, after saving a comp, some shots can not be displayed in the Viewer.

Customer reported version
N/A

Customer reported platform
N/A

Steps to reproduce


1) Open Nuke Studio.

2) Import at least 5 clips and drag them on to the Timeline.
Alternatively, you can also import a single clip, add it to the Timeline and cut it into 5, or more, separate shots.

3) Select one of the shots on the Timeline, ensuring that there are multiple shots before and after it.

4) Right click > Effects > Create Comp.

4) After the comp container is created, double click it to open the script.

5) Inside the Node Graph, make a change to the script (for example, add a Blur node) and save it (File > Save Comp).

6) Go back to the Timeline. You can do this by either changing the workspace or by clicking the Sequence tab. 

7) Scrub along the Timeline.

RESULT: The shot with the comp container will be displayed in the Viewer, as will the shots either side of it. All other shots will not display in the Viewer, when scrubbing over them.

Expected behaviour
When returning to the Timeline from the Node Graph, after saving a comp, you should be able to see all of the shots in the Viewer by scrubbing over them.

Actual behaviour
When returning to the Timeline from the Node Graph, after saving a comp, some shots can not be displayed in the Viewer.

Workaround
Disabling and re-enabling the affected tracks should allow you to see all the shots in the Viewer again.

Reproduced by support
This bug has been reproduced in:
Nuke Studio 13.0v5 - Windows 10 - macOS 10.13 (High Sierra) - Linux CentOS 7
Nuke Studio 12.0v1 - Windows 10 - macOS 10.13 (High Sierra) - Linux CentOS 7

Unable to reproduce bug in:
Nuke Studio 9.0v1 - Windows 10 - macOS 10.13 (High Sierra)

Earliest version tested
Nuke 9.0v1
- This issue doesn't appear in this version and has regressed

    We're sorry to hear that

    Please tell us why