ID 430184 - LensDistortion node does not create features and lines correctly when using an anamorphic input

Follow

Problem summary:
When using the LensDistortion node, if you are using an anamorphic (or non-square) pixel ratio, any lines or features created will be constrained within the square pixel ratio area of the viewer.

Note: This only occurs in Nuke 12.1v1 and later versions

Customer reported version:
Nuke 12.1v1

Customer reported platform:
CentOS 7

Steps to reproduce:
1) Open Nuke.
2) Create a Checkerboard node.
3) Within the Checkerboard properties, create a new format, setting the pixel aspect ratio to 2.

4) In the Node Graph, create a LensDistortion node, connecting it to the Checkerboard node.
5) Within the LensDistortion nodes toolbar, select the Add Lines tool, and attempt to draw a line from one edge of the anamorphic footage to the other.
Result: Your points will be incorrectly placed within a predefined square pixel aspect ratio area.

 
Alternative steps: 
1) Open Nuke.
2) Create a Checkerboard node
3) Within the Checkerboard properties, create a new format, setting the pixel aspect ratio to 2.​
4) In the Node Graph, create a LensDistortion node, connecting it to the Checkerboard node.
5) On the LensDistortion node, open the Analysis tab and press Detect.
6) Try to click and drag one of the features (close to the edge of the image).
Result: The point will 'jump' towards the centre of the image.

Expected behavior:
The new LensDistortion node should take into consideration non square pixel aspect ratios

Actual behavior:
The new LensDistortion node creates points inside a square pixel aspect ratio, irrelevant of source footage.

Workaround:
Before drawing lines or adjusting the grid, set the Mode knob (under Output) to STMap. This should then allow you to draw lines, or adjsut features, close to the edge of the frame without encountering the issue. You can set the desired output mode back when you are done.

Reproduced by Support in:
Nuke 15.1v4 - Windows 11
Nuke 12.1v1 - Windows 10 - CentOS 8 - MacOS 10.14.6

Unable to reproduce bug in:
Nuke 12.0v6 - Windows 10 - CentOS 8 - MacOS 10.14.6

Earliest version tested
Nuke 12.1v1 - The new LensDistortion node was introduced in Nuke 12.1v1

    We're sorry to hear that

    Please tell us why