ID 607046 - Blinkscript doesn't initially update values from a look controlled world matrix expression link

Follow

Problem summary
Blinkscript doesn't initially update values from a look controlled world matrix expression link
 
Customer reported platform
windows11
 
Steps to reproduce
 
1) Open Nuke

2) Paste the following nodes:
 

BlinkScript { inputs 0 ProgramGroup 1 KernelDescription "3 \"Test\" iterate componentWise 913f4bcde49a7c1721310f3ed500d4f58b78de1c0f09a97014671507f28c9309 1 \"dst\" Write Point 1 \"Input\" Float 1 AACAPw== 1 \"expressionInput\" 1 1 Default 0" kernelSource "kernel Test : ImageComputationKernel<eComponentWise> \{\n  Image<eWrite, eAccessPoint> dst;\n\nparam:\n  float expressionInput;   \n\nlocal:\n  void define() \{\n    defineParam(expressionInput, \"Input\", 1.0f);\n  \}\n  void process() \{\n    dst() = expressionInput;\n  \}\n\};\n\n" rebuild "" Test_Input {{parent.Axis2.world_matrix.5}} rebuild_finalise "" name BlinkScript1 xpos 279 ypos -51}push $cut_paste_inputAxis3 { translate {1 2 1} name Axis1 xpos 173 ypos -159}push 0Axis3 { inputs 2 name Axis2 xpos 173 ypos -66}
 
3) View the Blinkscript node it is white, though checking the expression knob, the value should be 0.577
 
4) In the Axis2 node, open the properties and open the World Matix panel, the Viewer image will change
 
5) If you paste the nodes again and view the new BlinkScript node, the same thing happens again
 
Expected behaviour
For the image output from BlinkScript node to always be 0.577 gray
 
Actual behaviour
When you first load the Blinkscript node, it outputs the wrong value
 
Workaround
Don't us the look input on nodes
 
Reproduced by support
This bug has been reproduced in:
Nuke 16.0v6 - Windows 11, macOS Sonoma
Nuke 16.0v4 - Windows 11 - regression
Nuke 15.2v6 - Windows 11
Nuke 15.2v4 - Windows 11 - regression
 
Unable to reproduce in:
Nuke 16.0v3 - Windows 11
Nuke 15.2v3 - Windows 11
 
Earliest version tested
Nuke 15.2v3 - This issue appears to have regressed in this version
 

    We're sorry to hear that

    Please tell us why