ID 547536 - GeoBindMaterial does not display correctly with ScanlineRender2 when a USD mesh contains "interpolation = 'faceVarying' " or "int[] primvars:st:indices = None"

Follow

Problem summary:
GeoBindMaterial does not display correctly with ScanlineRender2 when a USD mesh contains interpolation = "faceVarying" or int[] primvars:st:indices = None
 
Customer reported version:
Nuke 14.0v4
 
Customer reported platform:
Windows 11
 
Steps to reproduce:
1) Download the attached USD file and launch Nuke.
2) Create a GeoImport node and select the downloaded file.
3) Create a GeoBindMaterial node and set its Mask knob to //*


4) Create a ColorBars node and connect it to the GeoBindMaterial's mat input.
5) Create a Camera4 node and position it so the objects are in frame.
6) Create a ScanlineRender2 node and connect its obj/scn input to the GeoBindMaterial node, and its cam input to the Camera node.
7) Observe the difference between the ScanlineRender node (left) and the 3D Viewer (right):

 
Expected behavior:
The GeoBindMaterial should be displayed correctly in both the ScanlineRender2 node and the 3D Viewer, regardless of the underlying USD geometry.
 
Actual behavior:
When USD geometry has interpolation = "faceVarying" and int[] primvars:st:indices = None, the GeoBindMaterial node will only show a single color when viewed from a ScanlineRender2 node. The color appears to be determined by the center of the GeoBindMaterial's mat input:

 
Workaround:
Removing the interpolation = "faceVarying" and int[] primvars:st:indices = None lines from the USD file seems to allow the ScanlineRender2 node to produce the expected results. However, please note that this may cause the 3D Viewer to no longer display the GeoBindMaterial correctly, pictured below:

 
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
 
Earliest version tested
Nuke 14.0v1 - This feature (the GeoBindMaterial node) did not exist before this version

    We're sorry to hear that

    Please tell us why