ID 333828 - When exporting a Group to a Gizmo that calls a 3D node's 'disable' knob, when re-imported as a Gizmo, the knob is broken.

Problem summary
Within Nuke a Gizmo is generally created from Group node. Before exporting as a Gizmo, you can add in the knobs and expressions to the Group node via calling these knobs and expressions from nodes located within the Group node.

When a Gizmo is calling the 'disable' knob of any 3D node (eg. Sphere), this will not correctly enable and disable the Sphere's geometry within the Gizmo. This only occurs when the Gizmo is created and works correctly when it is a Group before converting to a Gizmo.

This also only appears to occur with the 'disable' knob and does not occur in other tested knobs within the Sphere's general or node properties.

If this process is conducted with a 2D node (eg. Rotopaint) this works as expected and the node is disabled via the Gizmo's controls

Customer reported version
nuke.11.1v1

Customer reported platform
centos6

Steps to reproduce

Open attached gizmo and attempt to toggle disable value

or

1) Create a Sphere node

2) Move it inside a Group (ctrl + g)

3) Right-click in the Group properties in the properties bin and select 'Manage User Knobs'

4) In the pop-up select 'Pick...'

5) In the Sphere1 menu, select the 'Node' submenu and then select 'disable' and 'ok'
This will create a link to the Sphere's 'disable' knob
​

​

6) Look at the Group node through the viewer and toggle on and off the 'disable' value
Result: works correctly

7) Under the 'Node' tab in the Group node select 'export as gizmo...'

8) Select a directory and name the Gizmo 'Sphere_Gizmo' (it will automatically give it the .gizmo extension)

9) Open a new Nuke script, select File>Import Comp Nodes and select the 'Sphere_Gizmo.gizmo'

10) Look at the imported Gizmo through the viewer and toggle the disable value
Result: does not work correctly

Note: This will also happen if the Gizmo is added to your .nuke directory and read in after selecting 'Plugins> Update All'.

Workaround
If the objective of the Gizmo connect is to turn off the visibility of the 3D node, it is possible to alter the 'display' knob associate with that Node.

For example, with a Sphere node, you can select the Sphere's 'display' knob value as appose to the Sphere's node's 'disable' value.
​

If you select 'off' in the 'display' knob, this knob will remain when brought back into as a Gizmo as appose to the 'disable' knob which does not,

Note: This will remove the visibility of the node within the viewer, but not the processing of the node.

Reproduced by support
This bug has been reproduced in:

Nuke 11.1v1 - Windows 7 - MacOSX 10.13 - CentOS 6.9
Nuke 11.0v4 - Windows 7
Nuke 11.0v1 - Windows 7 - MacOSX 10.13 - CentOS 6.9
Nuke 10.5v7 - Windows 7
Nuke 10.5v1 - Windows 7 - MacOSX 10.13 - CentOS 6.9
Nuke 10.0v6 - Windows 7
Nuke 10.0v1 - Windows 7 - MacOSX 10.13 - CentOS 6.9
Nuke 9.0v9 - Windows 7
Nuke 9.0v1 - Windows 7 - MacOSX 10.13 - CentOS 6.9
Nuke 8.0v7 - Windows 7
Nuke 8.0v1 - Windows 7
Nuke 7.0v10 - Windows 7 - MacOSX 10.12 - CentOS 6.9

Earliest version tested
Nuke 7.0v10
- This issue appears to be in all versions of the product

Expected behaviour
You should be able to enable and disable a 3D node's visibility if it is contained within a Gizmo

Actual behaviour
When exporting a Gizmo from a Group that has a knob calling a 3D node's disable value, the 'disable' knob does not work correctly when re-imported back into Nuke as a Gizmo.