Problem summary:
Transformed image textures do not display correctly on Classic 3D System geometry
This issue does not seem to affect the New 3D System.
Customer reported version:
Nuke 14.0v5
Customer reported platform:
RHEL 7
Steps to reproduce:
1) Launch Nuke and create a CheckerBoard node in the Node Graph.
2) Create a Transform node. Optionally, set its scale knob to 2 to exaggerate the issue.
3) Add a Sphere node and then View it.
4) Navigate in the 3D Viewer and observe how the image texture changes:
Expected behavior:
Image textures should remain unchanged when navigating in the Viewer.
Actual behavior:
When a Transform node is upstream of Classic 3D System nodes, the apparent scale of projected image textures will consistently increase until eventually the object is transparent in the 3D Viewer, and the image is a solid color in the 2D Viewer. However, this doesn't seem to happen if the Transform's scale is set to certain values, such as .9999 or 1.5.
This also affects nodes that are upstream of the Transform, as the CheckerBoard node in the example below displays different results depending on the state of the image texture in the Viewer:
Workaround:
Before the issue occurs, place a Grade node in-between the Transform and Sphere nodes. If the Viewer is already incorrect, disabling and then reenabling the Transform node should reset it to the expected state. Alternatively, deleting the Viewer node and creating a new one should also reset the problem.
Reproduced by Support in:
Nuke 14.0v5 - Windows 10, CentOS 7
Nuke 14.0v4 - Windows 10
Nuke 14.0v3 - Windows 10
Nuke 14.0v2 - Windows 10
Nuke 14.0v1 - Windows 10, CentOS 7 - Regression
Unable to reproduce bug in:
Nuke 13.2v8 - Windows 10, CentOS 7
Nuke 14.0v6 - Windows 10, CentOS 7
Earliest version tested:
Nuke 13.2v8 - This issue doesn't appear in this version and has regressed
