Problem summary
The 'DeeptoPoints' node does not behave correctly when a 'Camera' is connected into the 'Camera' input only in Nuke 11 releases. Work's correctly in Nuke 10 and earlier releases.
Customer reported version
nuke.11.0v2
Customer reported platform
Steps to reproduce
1) 'Deep Read' in any deep data
2) Create a 'DeeptoPoints' node under the 'Deep Read' node
3) Create a 'Camera' node
4) Connect 'DeepRead' in the 'deep' input of the 'DeeptoPoints' node
5) View Result in 3d scene, deep data can be seen as points in the scene laid out erratically in the scene along the baseline x-axis
6) Connect the 'Camera' into the 'camera' input of the 'DeeptoPoints' node Result: The point cloud should generate the point cloud based on the camera's direction. Instead adding the Camera removes any trace of the point cloud.
Workaround
Unknown.
Reproduced by support Nuke 11.0v2 - Windows 7 - MacOSX 10.12 - CentOS 6.9 (Issue present)
Nuke 11.0v1 - Windows 7 (Issue present)
Nuke 10.5v6 - Windows 7 - MacOSX 10.12 - CentOS 6.9 (works correctly)
Nuke 10.0v5 - Windows 7 (works correctly)
Nuke 9.0v9 - Windows 7 (works correctly)
Earliest version tested
Regression tested to Nuke 7.0v10
Expected behaviour
The point cloud should be using the Camera's data to project the point cloud in 3D space, as pre-Nuke 11 versions have.
Actual behaviour
When the Camera is added to the DeeptoPoints node through the Camera input the points from the point cloud disappear in Nuke 11 releases.