RandomGex Posted June 8, 2017 Share Posted June 8, 2017 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? Quote Link to comment Share on other sites More sharing options...
JDee Posted June 9, 2017 Share Posted June 9, 2017 (edited) 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 June 9, 2017 by JDee Quote Link to comment Share on other sites More sharing options...
RandomGex Posted June 9, 2017 Author Share Posted June 9, 2017 Hmm. Last I checked was that FBX required a static point count to work, but I'll give it a shot. Quote Link to comment Share on other sites More sharing options...
malexander Posted June 9, 2017 Share Posted June 9, 2017 Have you submitted a sample alembic to SideFX as a bug? Quote Link to comment Share on other sites More sharing options...
JDee Posted June 9, 2017 Share Posted June 9, 2017 17 minutes ago, malexander said: Have you submitted a sample alembic to SideFX as a bug? More likely to Autodesk, that makes no sense ) Quote Link to comment Share on other sites More sharing options...
malexander Posted June 9, 2017 Share Posted June 9, 2017 It depends on whether it's a bug in our Exporter or their Importer. I'd submit it to both. 1 Quote Link to comment Share on other sites More sharing options...
RandomGex Posted June 9, 2017 Author Share Posted June 9, 2017 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. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.