CameraTracker nodes solved with 'Unknown Lens' lose data when the file is reopened or the node is copied
Customer reported version:
NukeX
Customer reported platform:
N/A
Steps to reproduce:
1) Open NukeX and create a Read node in the Node Graph, then select footage of your choice.
2) Create a CameraTracker node, and change its Lens Distortion knob from "No Lens Distortion" to "Unknown Lens":
3) Next, press the Track button in the CameraTracker's Properties bin.
4) Once the Track is complete, press the Solve button and make note of the successful tracks:
5) Save, close, and reopen the file.
6) Double click on the CameraTracker node to open its Properties, and observe how the tracks have changed:
Expected behavior:
The CameraTracker's data should be preserved when a file is saved and reopened, or when the node is copied into the Node Graph.
Actual behavior:
The CameraTracker node loses data after the file is saved and opened again. Additionally, the same behavior can be observed by duplicating the node (Alt+C), or by copying/pasting it into the Node Graph.
Workaround:
After the initial Solve is complete, press the Update Solve button once. This seems to allow the CameraTracker node to retain all of its data and not change unexpectedly when it is copied or the file is reloaded.
However, please note that this does seem to increase the Solve's Error amount and also alter the tracked points slightly, so they won't be exactly the same as before. Instead, it is possible to raise the Max Error value in the AutoTracks tab to return the red points to their previously green state.
Reproduced by Support in:
NukeX 14.0v3 - Windows 10, CentOS 7
NukeX 13.0v1 - Windows 10
NukeX 12.0v1 - Windows 10
NukeX 11.0v1 - Windows 10
NukeX 10.0v1 - Windows 10, CentOS 7
Earliest version tested:
NukeX 10.0v1 - This issue appears to be in all tested versions of the product
