ID 604480 - The F_DeFlicker2 node's vectorDetail knob is not always disabled when useMotion is turned off

Problem summary:
The F_DeFlicker2 node's vectorDetail knob is not always disabled when useMotion is turned off   
 
Customer reported version:
Nuke 14.1v4
 
Customer reported platform:
Rocky9
 
Steps to reproduce:
1) Launch NukeX and create a F_DeFlicker2 node in the Node Graph
2) In the node's Properties, disable the Use Motion knob and note how Vector Detail is disabled:

3) Copy and Paste this node into the Node Graph, and observe how the Vector Detail knob is now enabled:

 
Expected behavior:
The F_DeFlicker2 node's "Vector Detail" knob should remain disabled when "Use Motion" is turned off.
 
Actual behavior:
When a F_DeFlicker2 node's Use Motion knob is turned off, the Vector Detail knob will be disabled but only for that specific node during the current Nuke session. If the file is saved and reopened or the node is copy/pasted, the Vector Detail knob will become enabled until the Use Motion knob is toggled on and off again.
 
Workaround:
A knobChanged callback like the one below can be used to ensure vectorDetail is only enabled if useMotion is turned on:

def disableVectorDetail():     n = nuke.thisNode()     k = nuke.thisKnob()     if k.name()=="useMotion" or k.name()=="showPanel":         n['vectorDetail'].setEnabled(n['useMotion'].value()) nuke.addKnobChanged(disableVectorDetail, nodeClass="OFXuk.co.thefoundry.furnace.f_deflicker2_v403")

 
Reproduced by Support in:
NukeX 16.0v4 - Windows 11, macOS 14 Sonoma
NukeX 15.0v1 - Windows 11
NukeX 14.0v1 - Windows 11
NukeX 13.0v1 - Windows 11
NukeX 12.0v1 - Windows 11
 
Earliest version tested:
NukeX 12.0v1 - This issue appears to be in all tested versions of the product