State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:219921|
Problem summary
Alembic exports of changing particles are not the same as the Nuke script which created it. If exporting an OBJ sequence of the same Nuke script, then the results are correct.
Customer reported version
nuke.10.0v1
Customer reported platform
centos7
Steps to reproduce
1) Open the attached Nuke script
2) Select the WriteGeo1 node, set the path to your drive, then execute the export.
3) Read it in with the ReadGeo1 node, clear the properties bin, then compare the what should have been exported vs what was, they are different.
4) Disable the TransformGeo1 node, and repeat steps 2 and 3, now the comparison will be the same.
Also writing out an OBJ sequence produces the correct results.
Additionally using a ProcGeo node in place of the TransformGeo node also creates the same issue.
Reproduced by support
The issue has been reproduced on:
NukeX 10.0v3 - Windows 10 - CentOS 6.7
NukeX 9.0v8 - Windows 10
NukeX 9.0v1 - Windows 10
NukeX 8.0v6 - Windows 10 - CentOS 6.7
Expected behaviour
For the alembic export to be the same as what is in Nuke
Actual behaviour
The alembic file was different
We're sorry to hear that
Please tell us why