ID 534629 - Connected nodes with axis inputs don't pass World matrix information to Expression linked knobs.

Follow

Problem summary:
Connected nodes with axis inputs don't pass World matrix information to Expression linked knobs.
 
This affects the following node classes from the Classic 3D System:
Axis3, Camera3, DirectLight, Environment, Light3, Light, and SpotLight.
 
And the following node classes from the New 3D System:
Axis4, Camera4, DirectLight1, EnvironmentLight, SpotLight1, and PointLight
 
Customer reported version:
Nuke 14.0v2

Customer reported platform:
Mac 13

Steps to reproduce:
1) Open Nuke and create an Axis node in the Node Graph.
2) Enter some values into the translate, rotate, or scaling knobs, then close the Axis node's Properties.
3) Click on the empty space in the Node Graph to deselect the Axis1 node, then create a second Axis node.
4) Close the Properties for the second Axis node.
5) Attach Axis1 to the input of Axis2.
6) Create a Matrix node with a width and height of 4, then click on the Animation menu in its Properties.
7) Select the Edit expressions... option, enter Axis2.world_matrix in the Expression field, and click OK.
8) Observe how the Matrix Expression is just an identity matrix:
9) Open the Properties for Axis2, and observe how the Matrix Expression updates after a change is made:

 
Expected behavior:
The Expression linked knob should consistently display the correct World matrix of the node(s).

Actual behavior:
The Expression linked knob reports that the node's World matrix is a default identity matrix, until some change is made to the node's Properties. This seems to affect all Expression linked knobs, but NoOp, BlinkScript, Matrix, Axis4, Axis3, and the Expression node were specifically verified. Additionally, closing Nuke and reopening the file will reset the Expression linked knob back to the identity matrix.
 
As an example, any of the following node configurations produce the same results:
 
Workaround:
Open the second node's Properties and expand the World Matrix or Local Matrix dropdowns, or otherwise change a knob value. Please note that this only works until the file is reloaded.
 
Reproduced by Support in:
Nuke 14.0v3 - Windows 10, CentOS 7
Nuke 14.0v2 - Windows 10, CentOS 7
Nuke 14.0v1 - Windows 10, CentOS 7 - Regression
 
Unable to reproduce bug in:
Nuke 13.2v6 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 13.2v6 - This issue doesn't appear in this version and has regressed.

    We're sorry to hear that

    Please tell us why