Problem summary When using the PointsTo3D node with your footage to define a location in 3d space, when the results are calculated, the generated 2d point is offset from the user created reference points.
Customer reported version nuke.12.2v3
Customer reported platform windows10
Steps to reproduce
1) Within a new Nuke session, import footage to track
2) Using the CameraTracker node, track a short range of this imported footage
3) When the track is complete, export the result as a new Camera using the 'Create' option
4) Create a PointsTo3D node, connecting the image to the img input and the new Camera to the cam input
6) Once the points are placed correctly, Calculate the result Result: The generated result 'point2d' is offset from the user placed points
Expected behaviour The point2d result should line up with the user placed points
Actual behaviour The point2d result is offset, which in turn is passed through to the Axis node which affects its location in 3D space.
Workaround As the result appears to be offset, when the data from the Axis node is used for placement within a Card or 3D object, using a TransformGeo node under this Card/3D object to line up to the user placed points will fix the offset issue.
Note: You may need to keyframe the TransformGeo translation properties on the user placed point keyframes, for trickier tracks.
Reproduced by support This bug has been reproduced in: Nuke 12.2v3 - Windows 10 - MacOS 10.15.6 - CentOS 7 Nuke 12.2v1 - Windows 10 Nuke 12.1v1 - Windows 10 Nuke 12.0v1 - Windows 10 Nuke 11.3v1 - Windows 10 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 - MacOS 10.15.6 - CentOS 7
Earliest version tested Nuke 9.0v1 - This issue appears to be in all versions of the product
