Problem summary
Creating a custom Bitmask_Knob works correctly for the current script, but will convert itself into a drop-down knob on save and restore of the script.
Additionally, copying and pasting the node will cause the knob change behaviour.
This can be troubling when the user expects to choose multiple options at once, but no longer can.
Customer reported version
nuke.11.2v5
Customer reported platform
windows10
Steps to reproduce
1) Open a fresh Nuke script
2) Copy and execute the following into Nuke's Script Editor:
This will create a NoOp node with the custom specified User knob within the Node Graph
3) Review the new node in the Properties and note the Knob layout:
4) Save the script and reopen it in a new Nuke session OR copy and paste the node.
Result: Reopening the node's Properties will display a dropdown, instead of the three checkboxes:
Workaround
As a workaround, use a series of Boolean Knobs instead to create the same effect:
n = nuke.nodes.NoOp()n.addKnob(nuke.Boolean_Knob("opt1"))n.addKnob(nuke.Boolean_Knob("opt2"))n.addKnob(nuke.Boolean_Knob("opt3"))
Reproduced by support
This bug has been reproduced in:
Nuke11.2v5 - Windows 7 - Mac10.13 - CentOS6.9
Nuke11.2v1 - Windows 7
Nuke11.1v6 - Windows 7
Nuke11.1v1 - Windows 7
Nuke11.0v4 - Windows 7
Nuke11.0v1 - Windows 7
Nuke10.5v7 - Windows 7 - Mac10.13 - CentOS6.9
Nuke10.5v1 - Windows 7
Nuke10.0v6 - Windows 7
Nuke10.0v1 - Windows 7
Nuke9.0v9 - Windows 7
Nuke9.0v1 - Windows 7
Nuke8.0v7 - Windows 7
Nuke7.0v10 - Windows 7 - Mac10.13 - CentOS6.9
Earliest version tested
- This issue appears to be in all versions of the product
Expected behaviour
Bitmask knob should save as a Bitmask knob
Actual behaviour
Bitmask knob is converted into a dropdown on relaunching.