Problem summary
Views render incorrectly when using a Switch node with nodes after it. If the switch node has been modified so it switches to match the requested view, by either expressions or blue splitting off views, then when rendering, the first frame renders the incorrect view, after that it renders correctly.
Customer reported version
nuke.9.0v8
Customer reported platform
windows10
Steps to reproduce
1) Open Nuke and open the attached file
2) Run the code below in the script editor, this allows the creation of the view render folders:
def CreatePath(): file = nuke.thisNode()["file"].getEvaluatedValue() dir = os.path.dirname(file) osdir = nuke.callbacks.filenameFilter(dir) try: os.makedirs (osdir) except OSError: pass
3) Select the Write node, and change the path to a local directory, insuring /%V/ is somewhere in the path to allow the multiple views to be rendered.
4) Press render, the first frame for some of the views will be incorrect, the other frames will be correct.
5) Disable the Text1 and Blur1 nodes, and render again. This time all the frames will render correctly.
Reproduced by support
I have reproduced this on:
Nuke 10.0v2 - Windows 10 - CentOS 6.7
Nuke 9.0v8 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v6 - Windows 10 - CentOS 6.7
Expected behaviour
For all the frames to render correctly when there are nodes after the Switch node.
Actual behaviour
The first frame rendered incorrectly.