Problem summary When the Bounding Box warning is activated, and there is an error related to a Group node in the script, several tracking related nodes will not track as expected.
From testing, this issue has only been shown to occur in the Tracker and PlanarTracker nodes, only within Windows and Linux (not MacOS), and only occurs in Nuke 11.3 releases.
Customer reported version nuke.11.3v4
Customer reported platform centos7
Steps to reproduce
1) Turn on the 'Bounding Box Warning' feature with the 'General > Panels > Node Graph' preferences.
2) Read in a short clip (to be used to track)
3) Create a Tracker node, connecting it to the Read node.
4) Using the 'Track to End' function within the Tracker node, track several frames of footage. Result: Works as intended with un-interrupted tracking.
5) Create a new Read node
6) Alter the file location of the node to a fake file location eg. 'path/to/file.dpx'. (this will create the 'error' required in the Read node)
7) Create a Group from this error-ing Read node by selecting the Read node and pressing 'ctrl+g' (this will create the Group node with an error)
8) Within the Tracker node, delete the existing track created in step 4 above
9) Create a new track using the 'Track to End' function again. Result: The Tracker node will go for a frame or two then stop automatically without prompt.
Expected behaviour The Tracker node should track the same duration whether the Group node in the script contains an error or not, when the Bounding Box Warning feature is active.
Actual behaviour Tracker node stops prematurely if a Group node in the script has an error, even if its not in the node tree.
Workaround Unknown. Ensure Group nodes that have any errors, do not exist in a script that has the Bounding Box Warning feature active.
Reproduced by support This bug has been reproduced in: Nuke 11.3v4 - Windows 7 - CentOS 7 Nuke 11.3v1 - Windows 7 - CentOS 7
