Problem summary: SphericalTransform2 nodes do not preserve incoming metadata unless the metaDataOperations knob has been manually toggled
Customer reported version: Nuke 13.2v6
Customer reported platform: CentOS 7
Steps to reproduce: 1) Launch Nuke and create a CheckerBoard node in the Node Graph. 2) Create a ModifyMetaData node, and add a key-value pair of your choice:
3) Create a SphericalTransform node, and then a ViewMetaData node. 4) In the ViewMetaData node's Properties panel, observe how the metadata from step 2 does not appear. 5) Open the SphericalTransform's Properties, and toggle the metaDataOperation knob from Ignore to Apply (or Transform), then back to Ignore.
6) Observe how the metadata returns:
Expected behavior: When a SphericalTransform node's metaDataOperation knob is set to Ignore, all metadata should pass through the node unchanged:
Actual behavior: Adding a SphericalTransform2 node to the Node Graph will remove any existing incoming metadata by default.
Although toggling the metaDataOperation knob does temporarily resolve the issue, saving and reloading the Nuke script resets this. Additionally, Copy/Pasting a SphericalTransform node with the corrected state does not transfer to subsequent SphericalTransform nodes.
Python similar to the following can also be used to resolve the issue, but only if the code is executed one line at a time:
n = nuke.toNode("SphericalTransform1") n["metaDataOperation"].setValue("Apply") n["metaDataOperation"].setValue("Ignore")
Workaround: No known workaround at this time
Reproduced by Support in: Nuke 15.0v2 - Windows 10, macOS 13 Ventura Nuke 14.1v1 - Windows 10 Nuke 14.0v1 - Windows 10 Nuke 13.0v1 - Windows 10 Nuke 12.1v1 - Windows 10
Earliest version tested: Nuke 12.1v1 - This feature (SphericalTransform2) did not exist before this version
