State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:378851|
Problem summary:
An incorrect amount of Deep samples are created when using antialiasing in the Scanline Render node.
Customer reported version:
nuke.11.2v5
Customer reported platform:
centos6
Steps to reproduce:
1) From Nuke, create 2 Card geometry nodes.
2) Rotate the Card nodes so that they intersect.
3) Create a Scene node and attach the Card nodes.
4) Create a Scanline Render node and attach it to the Scene, also adding a Camera.
5) Adjust the Camera to view the intersection of the 2 Card nodes.
6) Access the Properties bin of the Scanline Render node and turn on antialiasing.
7) Create a DeepSample node attached to the Scanline Render.
8) Move and place the DeepSample pos coordinates, observing the samples output in the Properties bin.
Workaround:
There is no current workaround at this time.
Reproduced by Support in:
Nuke 11.3v1 - Windows 10, CentOS 7, macOS 10.13 High
Nuke 11.2v1 - Windows 10
Nuke 11.1v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.5v1 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v1 - Windows 10, CentOS 7, macOS 10.13 High Sierra
Earliest version tested:
Nuke 8.0v1 - This issue appears to be in all versions of the product
Expected behavior:
Antialiasing should have a minimal amount of Deep samples generated when using the Scanline Render.
Actual behavior:
Additional Deep samples are created when using antialiasing with the Scanline Render node.
We're sorry to hear that
Please tell us why