ID 582051 - [3D Arch] The GeoUVProject node produces incorrect results if indexed "st" attributes are present

Problem summary:
The GeoUVProject node produces incorrect results if indexed st attributes are present

Customer reported version:
Nuke 15.1v1

Customer reported platform:
Windows 10

Steps to reproduce:
1) Launch Nuke and open the attached Nuke script.
2) View the ScanlineRender2 node, and observe the distorted CheckerBoard pattern:

Expected behavior:
The GeoUVProject node should create undistorted UVs for the CheckerBoard texture to be applied.

Actual behavior:
When indexed st attributes are present, the GeoUVProject doesn't produce the correct results. It changes the st attribute but leaves the st:indices attribute in place, causing the new UVs to be read in the wrong order. Prior to Nuke 15.1v1, the ScanlineRender2 node would render this USD completely black.

Workaround:
It is possible to resolve the problem by manually removing the st:indices attribute, like with a GeoScript node:

GeoScript { usd_source "#usda 1.0\n\nover \"pCylinder1\"\n\{\n    int\[] primvars:st:indices = None\n\}\n"}

Reproduced by Support in:
Nuke 15.1v1 - Windows 11, macOS 13 Ventura
Nuke 14.1v1 - Windows 11
Nuke 14.0v1 - Windows 11

Earliest version tested:
Nuke 14.0v1 - This feature (the New 3D System) did not exist before this version