ID 176563 - ReadGeo alembic results with UV projection do not match for the same Nuke internal geometry or .fbx

 

REPRO:

use attached TF_repro.nk

-with a WriteGeo1 node write out the geometry as Alembic (abc) 
-with a ReadGeo13 node load in the file you just created 

-with a WriteGeo2 node write out the geometry as Alembic (abc) 
-with a ReadGeo1 node load in the file you just created 
-View ScanlineRender in either projection mode perspective or uv
-Change Switch node to [0 to see cylinder, 1 to see .abc and 2 to see .fbx] and compare the output of ScanlineRenderer

 

0=Cylinder (Nuke internal geometry) 

1= ReadGeo .abc (rendered from Cylinder) 

2= ReadGeo.fbx  (rendered from Cylinder) 

 

RESULT- for ReadGeo .abc  (on Switch=1) does not match results for .fbx or Nuke internal geometry (a cylinder)

All three should match, but .abc does not.

 

see screenshots :

fbx_result.png 

abc_result.png

 

 

 

Reproduced by support
8.0v6-10.0v3 same incorrect result ( for earlier versions, comparison results vary but still, none are correct)

MacOS 10.10.4

Expected behaviour

ReadGeo alembic results with UV projection should match for the same Nuke internal geometry ( a cylinder)  or .fbx file

 

Actual behaviour

ReadGeo alembic results with UV projection do not match for the same Nuke internal geometry ( a cylinder) or .fbx file