Problem summary Motion/Forward Vectors generated from the ScanlineRenderer can contain incorrect results
Customer reported version nuke.10.0v4
Customer reported platform 10.09
Steps to reproduce
1) Open the attached Nuke script
2) View the Motion/Foward layer
3) Play the Viewer, occasionally you will get frames like below Left images show what the result should be, right images show the random errors
4) Increasing the samples on the Scanlinerender node (under the MultipleSample tab) also seems to result in artifacts on frames that previously displayed the expected result. The image on the left shows the ScanlineRender node's samples set to 1, and the right shows when the samples are set to 3:
Workaround Use the RayRender node, as it doesn't appear to be affected by the issue.
Reproduced by support This problem has been reproduced on:
Nuke 13.2v2 - Windows 10 - CentOS 7
Nuke 10.0v5 - Windows 10 - CentOS 6.8
Nuke 10.0v1 - Windows 10
Nuke 9.0v9 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v6 - Windows 10 - CentOS 6.8
Expected behaviour To get consistent render results