Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Sign in to follow this  
Followers 0
RandomGex

Alembic File from Houdini causes Max to crash

Hey, guys! I'm a bit flummoxed as I've been exporting Alembic files from Houdini to use in 3D Studio Max for a while with no issues. But I've been struggling with a particular file all afternoon that's causing Max to crash. I've dealt with alembic files at least twice as large as the one in Max without any issue, so I doubt it's a size issue. I pulled the file back into Houdini and had no issues with the file in Houdini. I've tried both Ogawa and HDF5 formats. I've tried it on a couple different computers with the same results of Max crashing. It crashes when it gets about half way through both playback of the alembic as well as trying to export a Vray proxy mesh. Now, the effect in question does rely heavily on a boolean opperation from houdini to basically dissolve away a mesh, so could this have something to do with it? Any ideas?

Share this post


Link to post
Share on other sites

Had a lot of shit with Houdini->Alembic->3dsmax too.
So FBX export will save your time.
And then if you really need alembic at the end just reexport it in alembic from 3dsmax, so max will eat it with no issue after this.

Edited by JDee

Share this post


Link to post
Share on other sites

Hmm. Last I checked was that FBX required a static point count to work, but I'll give it a shot.

Share this post


Link to post
Share on other sites
17 minutes ago, malexander said:

Have you submitted a sample alembic to SideFX as a bug?

More likely to Autodesk, that makes no sense )

Share this post


Link to post
Share on other sites

It depends on whether it's a bug in our Exporter or their Importer. I'd submit it to both.

1 person likes this

Share this post


Link to post
Share on other sites

I think it's more a bug in Max 2016, since that version of Max seems to hate alembic files. I got it to work, but it involved bringing it into Maya and then re-exporting it from Maya to Max.

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  
Followers 0