Problem summary Users have found a difference between GUI and Terminal rendering when using Project3D and ScanlineRender nodes in Nuke.
The difference is not within the main rendered image, but artifacting within the overscan.
GUI render: ( Footage transformed up to display overscan )
Terminal render: ( Footage transformed up to display overscan )
Customer reported version nuke.11.2v3
Customer reported platform
Steps to reproduce
1) Open the provided script ( open your script )
2) Render out Frame 1013 within the GUI as an EXR. ( Name the file overscanRender_GUI.%4d.exr )
3) Rename the Write node to overscanRender_Terminal.%4d.exr and save the script.
4) Open a command prompt window and render the script with the following: "Nuke -F 1013 -x nukeScriptHere.nk"
Replace 'Nuke' with your Nuke.exe location.
5) Read both rendered files into the Node Graph.
6) Add a transform to each, which moves the overscan into the main Viewer area.
Result: The Terminal Render will look 'Cropped' when compared to the GUI render.
Expected behaviour There should be no differences between GUI and Terminal rendering.
Actual behaviour There is a difference within the Overscan of the Terminal rendered footage.
Workaround Unknown.
Reproduced by support
This bug has been reproduced in: Nuke11.3v1- Windows 7 - Mac10.14 - CentOS7 Nuke11.3v1- Windows 7 - Mac10.14 - CentOS7 Nuke11.2v1 - Windows 7 Nuke11.1v1 - Windows 7 Nuke11.0v1 - Windows 7 Nuke10.5v1 - Windows 7 Nuke10.0v1 - Windows 7 Nuke9.0v1 - Windows 7 Nuke8.0v1 - Windows 7 - Mac10.14 - CentOS7
Earliest version tested - This issue appears to be in all versions of the product
