Problem summary
GridWarp + GridWarpTracker nodes render incorrectly from terminal or frame server.
Customer reported version
nuke.13.1v2
Customer reported platform
windows10
Steps to reproduce
1) In Nuke, create a Checkerboard node.
2) Add a GridWarpTracker or GridWarp attached to the Checkerboard.
3) Adjust the control point of the GripWarp in the Viewer, then select the Render tab in the Properties.
4) Set the submesh resolution to anything above or below 10.
5) Add a Write node downstream and execute the Render knob.
6) Enable the frame server checkbox, then render the frame.
7) Read the rendered frame back in and compare the results.
Expected behavior
The correct submesh samples should be applied to the render.
Actual behavior
An incorrect submesh is always applied as the value 10 when rendering with terminal or frame server.
Workaround
Rendering interactively (in GUI) does not seem to experience the issue.
Reproduced by Support in:
Nuke 13.1v 3 - Windows 10, CentOS 7
Nuke 13.1v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v1 - Windows 10, CentOS 7
Earliest version tested
Nuke 9.0v1 - This issue appears to be in all versions of the product
