mangi 59 Posted May 29, 2013 on second let me send you the files Share this post Link to post Share on other sites
mangi 59 Posted May 29, 2013 (edited) "its working .. how did you do that " like in this hip, just change the sequence of the bgeo inside the geometry node The Alembic rop is there aswell mangi ALMBIC_MAYA.rar Edited May 29, 2013 by mangi Share this post Link to post Share on other sites
Ali Haider 0 Posted May 30, 2013 (edited) thanks mangi .... i observed that just save attribute check is on while exporting into alembic working in your case :\ also 2 attributes -root object -objects they are not locked but inactive , are these the real culprits, curios to know the answer !! Edited May 30, 2013 by Ali Rizvi Share this post Link to post Share on other sites
mangi 59 Posted May 30, 2013 Ali Root Object The root object of the scene. All displayed objects contained under this node will be included in the Alembic archive. Objects A pattern/bundle of objects to include in the alembic archive. Also Save Attributes is just for that , saving attributes. " save attribute check" this is on by default. Mangi Share this post Link to post Share on other sites
mangi 59 Posted May 31, 2013 Cool Ali, Cheers Mangi Share this post Link to post Share on other sites
Mrlours 1 Posted June 4, 2013 (edited) Hello for the oldest version of maya it seem that between houdini alembic loose one connection between connectAttr the AlembicNode.outPolyMesh and the geo .inMesh; you can fix it in your hypergraph connection and do manually the connection. or run connectAttr NAME OF YOUR ALEMBIC_AlembicNode.outPolyMesh[0] NAMEOFYOURGEO.inMesh; David Edited June 4, 2013 by Mrlours 1 Share this post Link to post Share on other sites
A. Morales 6 Posted June 22, 2013 David, your post should be stickied, that fixed every issue when i was running into an alembic import glitch thanks Adad Share this post Link to post Share on other sites
Bonedaddy 0 Posted October 29, 2020 Tossing this into this thread in the hope it'll help someone -- I, in the good year of our lord 2020 (who am I kidding, this is the worst goddamn year), ran into this issue, and the root cause was a bad path variable. We had an artist exporting using a prim 'path' variable to create hierarchy in Maya. However, his path values were all over the place, wildly inconsistent. What Maya is looking for is something like this: /Group/Object/ObjectShape Once we fixed that, everything worked much better. Share this post Link to post Share on other sites