Problem summary:
SphericalTransform nodes produce artifacts when the Input Projection is set to Cubemap
Customer reported version:
Nuke 14.0v3
Customer reported platform:
macOS 13 Ventura
Steps to reproduce:
1) Open Nuke and create a Constant node in the Node Graph.
2) Make the Constant grey by changing the color knob to 0.5 in the Properties bin.
3) Create a SphericalTransform node, then set its Input Projection to Cubemap, and Format to Views:
4) View the SphericalTransform node and observe the artifacts, pictured below:
Alternative steps:
This behavior also occurs when the SphericalTransform node's Format is set to Faces or Image, and appears to happen regardless of which Output Projection is selected. When the Format is Image, providing the node with a packed 6x1 or 3x2 grid of faces might appear to prevent the issue from occurring, but artifacts can still be observed if the faces are different colors:
Expected behavior:
The SphericalTransform node should create a seamless, artifact-free image.
Actual behavior:
The SphericalTransform's output is segmented by lines near the boundaries of each shape.
Workaround
This issue doesn't seem to occur if the SphericalTransform node's Format is set to Faces, and each input has an AdjustBBox node that adds 1 pixel (pictured below).
Reproduced by Support in:
Nuke 14.0v4 - Windows 10, CentOS 7
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.1v1 - Windows 10, CentOS 7
Earliest version tested:
Nuke 12.1v1 - This feature (the SphericalTransform2 node) did not exist before this version.
