State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:537531|
Problem summary
Expression linking to a SplineWarp node's translate knob will create an additional keyframe at frame 0.
Customer reported version
Nuke 12.2v8
Customer reported platform
Windows 10
Steps to reproduce
1) Open Nuke.
2) Navigate to Edit > Project Settings and change the frame range knob values to 50 and 100.
3) Create a SplineWarp node.
4) At frame 50, create a curve on the SplineWarp.
5) Right-click the curve in the SplineWarp's curves list > Duplicate and join.
6) Between frames 50-100, create a few keyframes on this curve.
7) Create a Transform node.
8) Open the Dope Sheet to ensure that there are no key frames on frame 0.
9) On the SplineWarp node, select Root from the curves list and open the Transform tab.
10) Ctrl+drag the Transform's translate knob to the SplineWarp's Root translate knob.
11) Add another keyframe to the animate curve in the SplineWarp.
12) Relink the Transform to the SplineWarp's root transform, in the same way as steps 9 and 10.
13) Observe that there is now a key at frame 0 in the dope sheet
Expected behaviour
Expression linking to a SplineWarp node's translate knob should not create any additional key frames.
Actual behaviour
Expression linking to a SplineWarp node's translate knob will create an additional keyframe at frame 0.
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
Nuke 14.0v3 - Windows 10 - Linux CentOS 7
Nuke 12.0v1 - Windows 10
Nuke 10.0v1 - Windows 10 - Linux CentOS 7
Earliest version tested
Nuke 10.0v1
- This issue appears to be in all tested versions of the product
We're sorry to hear that
Please tell us why