Problem summary When using the CameraTrackerPointCloudexport option created by the CameraTracker node, when attempting to create a mesh from the point cloud using a PoissonMesh node, you will receive the following error.
This error occurs as the generated CameraTrackerPointCloud node does not create the normal data required for the PoissonMesh node.
Customer reported version nuke.n/a
Customer reported platform
Steps to reproduce Open attached script and view results
or
1) Read in source footage, and use the CameraTracker node create a track.
2) When you have the intended track result, export as 'Point cloud'
3) Connect the created CameraTrackerPointCloud node downstream from the CameraTracker node
4) Create a PoissonMesh node downstream of the CameraTrackerPointCloudnode Result: Error and mesh not created from PossionMesh node
Expected behaviour Mesh should be able to be generated from the CameraTracker's point cloud export node
Actual behaviour Mesh unable to be generated from the CameraTrackerPointCloud node
Workaround This issue is isolated to the CameraTrackerPointCloud node. As an alternative, you can use the PointCloudGenerator node to get the correct results using the following steps:
a) Create a Camera exported from your above processed CameraTracker node b) Create a PointCloudGenerator node connecting into the source footage c) Connect the Camera node into the PointCloudGenerator nodes' 'camera' input d) Within the PointCloudGenerator node add the keyframes as needed and Analyse Sequence e) Also within the PointCloudGenerator node, tweak the 'Track Threshold', then 'Track Points' f) Create a PoissonMesh node downstream of the PointCloudGenerator node Result: Mesh is correctly created from point cloud information
Reproduced by support This bug has been reproduced in: Nuke 12.0v3 - Windows 7 - MacOS 10.14.5 - CentOS 7 Nuke 12.0v1 - Windows 7 Nuke 11.3v1 - Windows 7 Nuke 11.2v1 - Windows 7 Nuke 11.1v1 - Windows 7 Nuke 11.0v1 - Windows 7 Nuke 10.5v1 - Windows 7 Nuke 10.0v1 - Windows 7 Nuke 9.0v1 - Windows 7 Nuke 8.0v1 - Windows 7 - MacOS 10.14.5 - CentOS 7
Earliest version tested Nuke 8.0v1 - This issue appears to be in all versions of the product
