State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:381874|
Problem summary
The Framehold node is ignored when an Axis node has an animated world matrix downstream.
Customer reported version
nuke.11.3v1
Customer reported platform
n/a
Steps to reproduce:
1) In Nuke, create an Axis node with a World Matrix applied.
2) Create a Framehold set for frame 10.
3) Create another Axis node, attached to the previous Framehold.
4) Select the Axis 1 node and animate the translate values for x,y,z.
5) View the World Matrix for Axis 2 node.
Workaround:
There is no workaround at this time.
Reproduced by Support in:
Nuke 11.3v2 - Windows 10
Nuke 11.2v1 - Windows 10
Nuke 11.1v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.5v1 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v1 - Windows 10
Earliest version tested:
Nuke 8.0v1 - This issue appears to be in all versions of the product
Expected behavior:
The metadata of the World Matrix should not be applied to other Axis nodes when a Framehold node is placed.
Actual behavior:
The World Matrix of the new Axis node will ignore the upstream Framehold and stream through the metadata,.
We're sorry to hear that
Please tell us why