Problem summary
NukeStudio won't buffer into the timeline rendered files when a Nuke script has a Write node with a variable in the file path. The files can be rendered to timeline from NukeStudio, and the files are created on disk, however NukeStudio then won't read in the rendered files to display them in the viewer.
Customer reported version
nuke.10.0v1
Customer reported platform
centos6
Steps to reproduce
1) Create a directory into which the image files can be written, I used C:/temp.
2) Open NukeStudio
3) Import the attached Nuke script and put it into a sequence.
4) Open the comp, select the Write node, and go to the User tab. In the projectDir knob, input the path you created earlier.
5) Click render, then and Ok to render to timeline.
6) Select the Sequence 1 pane, and observe that the Nuke script renders, but no preview becomes available in the viewer.
NukeStudio also displays the below error during rendering with a variable in the file path of the Write node of the Nuke script.
If the file path is replaced with the absolute equivalent, then the files are read in correctly, and the preview works.
In my case changing the path from: [value this.projectDir]/testRender_####.dpx to C:/temp/testRender_####.dpx
The image on the left shows what happens after rendering to timeline with a variable in the write node, on the right is what happens when the path is absolute.
Reproduced by support
I have reproduced the bug in:
NukeStudio 9.0v1 Windows 10
NukeStudio 9.0v8 Windows 10
NukeStudio 10.0v1 Windows 10
NukeStudio 9.0v1 MAC OSX 10.11
NukeStudio 9.0v8 MAC OSX 10.11
NukeStudio 10.0v1 MAC OSX 10.11
Expected behaviour
For the clip in the timeline to turn green, and to see the rendered sequence.
Actual behaviour
The frames were rendered, but they can't be read by NukeStudio with the variable in the file path of the Write node.
