ID 326776 - Nuke 11.1's Tracker creates a redundant link to a pre-existing Transform node if it has the same name as a newly exported Transform node.

Follow

Problem summary
After you Track a shot, you have the option of exporting out that Tracking information into a CornerPin or Transform node. This will automatically create a linked node that has the correct attributes and saves manual linking.

In Nuke 11.1, this export option has a problem. If you export a Transform (Matchmove or Stabilize) and there is already a Transform node with the same name eg. 'Transform_MatchMove1' or 'Transform_Stabilize1', the exporter will create a 'Transform_MatchMove2' (as expected), but what it will also do is create a link to both Transform nodes.

In versions previous to Nuke 11.1, the link will only connect to the exported node and not both.

Customer reported version
nuke.11.1v1

Customer reported platform

Steps to reproduce

1)Open Nuke 11.1 release and Create a Transform node, calling it "Transform_MatchMove1"
2) Create a Tracker node and track some footage.
3) Under the "Tracker" tab in the Tracker node, click "Create" in the export options to export a Transform node using the "Transform (match-move)" option.
Result: Both the Transform_MatchMove1 and TransformMatchMove2 will be relationship linked to the tracking and TransformMatchMove1 will not contain any linked data.

Workaround
Suggested workaround would to avoid naming any Transforms/Cornerpins the same name as the Tracker nodes export preset names. eg. Transform_MatchMove1. in Nuke 11.1 release.

Reproduced by support
This bug has been reproduced in:
Nuke 11.1v1 - Windows 7 - MacOSX 10.13 - CentOS 6.9 - regression

Unable to reproduce bug in:
Nuke 11.0v3 - Windows 7 - MacOSX 10.13 - CentOS 6.9

Earliest version tested
Nuke 11.0v3 - Windows 7 - MacOSX 10.13 - CentOS 6.9
- This issue no longer appears in this version

Expected behaviour
When a new Transform node is created from the Tracker's export option, the Tracker should only link to exported Transform nodes, not ones that existed before the export.

Actual behaviour
The Tracker exports the Transform node and links to any other Transforms with the same name as the exported Transform node.
 

    We're sorry to hear that

    Please tell us why