ID 163888 - Project3D doesn't draw correctly in GL view if projected only on front or back of Card

Problem summary
Project3D doesn't draw correctly in GL view if projected only on front or back of Card. However, this appears to only affect the 3d Viewer as the result will look correct when viewed with a ScanlineRender node. Projecting on "both" also works as expected.

This may also be specific to the Card node, as projecting on the front and back of other 3d geometry, such as Cubes or Spheres, seems to work as expected too.

Customer reported version
Nuke 12.1v2

Customer reported platform
CentOS 7

Steps to reproduce

1) Open Nuke. Press Tab on the Viewer to view the 3D Viewer.

2) Create a Project3D node and connect a ColorWheel to its unnamed input. 

3) Create a Card and connect it downstream from the Project3D node.

4) Create a Camera and connect it to the "camera" input of the Project3D. Move the camera so that you can see it projecting the ColorWheel onto the Card.

5) Open the Project3D node's properties and set "project on" to "front".

It may appear to be projecting on the wrong side of the card, in which case you can try to rotate the Card 180 degrees:

The ColorWheel will then look like a black circle in the 3d Viewer.

Expected behaviour
The image should be correctly projected on the front of the Card in the 3d Viewer.

Actual behaviour
When "project on" is set to "front", the image will either appear to be projected on the wrong side of the Card or the image will be shown as black in the 3d Viewer.

Workaround
You may be able to achieve the same final result by setting "project on" to "both".

Alternatively, if you export the Card with a WriteGeo node, then importing it again (with a ReadGeo), the projection should now look correct in the 3d Viewer. 

Reproduced by support

This bug has been reproduced in:
Nuke 12.2v1 - WIndows 10 - macOS 10.13 (High Sierra) - Linux CentOS 7

Nuke 8.0v1 - Windows 10 - macOS 10.13 (High Sierra) - Regression

Unable to reproduce bug in:

Nuke 7.0v10 - Windows 10 - macOS 10.13 (High Sierra)

Earliest version tested
Nuke 7.0v10
- This issue doesn't appear in this version and has regressed