Jump to content
Sign in to follow this  
A. Morales

Having an issue with Houdini Alembic to Maya

Recommended Posts

on second let me send you the files

Share this post


Link to post
Share on other sites

"its working :o .. how did you do that :D"

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 by mangi

Share this post


Link to post
Share on other sites

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 by Ali Rizvi

Share this post


Link to post
Share on other sites

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

Cool Ali,

Cheers

Mangi

Share this post


Link to post
Share on other sites

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 by Mrlours
  • Like 1

Share this post


Link to post
Share on other sites

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

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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×