Problem summary
ReadGeo takes 2-3x as long to evaluate the Node Graph, when loading multiple meshes
'all in one' vs. single alembic files . You can see this by comparing the time it takes to open
open scripts in Nuke with the same alembic files saved all-in-one vs. as separate nodes.
Apparently, having multiple meshes in a single Alembic file is less efficient than storing in individual Alembic files.
Customer reported version
nuke.9.0v6-10,0v1
Customer reported platform
n_a_linux and MacOSX
Steps to reproduce
un-zip attached forFoundry.tar.gz
test_allInOne.nk
test_separated.nk
1) Un-zip archive , replace paths to alembic files (using text editor to replace <yourpath>/alembic/ )
and save with valid paths in Read Geo for test_allInOne.nk and test_separated.nk
2) Launch test_allInOne.nk from command line and record time it takes to open, evaluate nodegraph
e.g. on my MacOS 10.2.2. = 32 secs. to open
3) Launch test_separated.nk from command line and record time it takes to open, evaluate nodegraph
e.g. on my MacOS 10.2.2. = 11 secs. to open
Reproduced by support
yes
8,.0v1-10,0v1
Expected behaviour
Alembic multiple meshes loaded in Read Geo with 'Create all-in-one node should not load so slowly
Actual behaviour
Alembic multiple meshes loaded in Read Geo with 'Create all-in-one node should not load so slowly
Alembic single files loaded separately load at least 3x quicker