Problem with Alembic export of shattered geometry to Maya
7183 10 1- Tanto
- Member
- 401 posts
- Joined: Nov. 2016
- Offline
Hi, I'm importing a mesh with UV's from Maya, shattering it and simulating it in Houdini, as well as adding new UV's for the inside prims, and re-exporting it as an Alembic to be lit and rendered in Maya. All went well until there was an update in the modelling UV's and I had to pass it through the setup again. Now, when importing the Alembic back to Maya, I get:
// Warning: normal vector scope does not match size of data, skipping normals //
// Warning: UV set sample size is: 2343643 expecting: 823070 or 2343630 //
And the model doesn't have UV's anymore. I tried several different things, the most promising of which was to use a polydoctor, it worked on one frame but when importing the whole sequence, Maya crashes. I went through this thread [forums.odforce.net] but most of the solutions either didn't work or implied making changes to the simulation that is already approved. Anybody encountered that and has an idea how to fix it?
// Warning: normal vector scope does not match size of data, skipping normals //
// Warning: UV set sample size is: 2343643 expecting: 823070 or 2343630 //
And the model doesn't have UV's anymore. I tried several different things, the most promising of which was to use a polydoctor, it worked on one frame but when importing the whole sequence, Maya crashes. I went through this thread [forums.odforce.net] but most of the solutions either didn't work or implied making changes to the simulation that is already approved. Anybody encountered that and has an idea how to fix it?
- Midasssilver
- Member
- 310 posts
- Joined: July 2012
- Offline
Hi there, your issue seems hip file specific, so I'd probably need that to see where the issue arises. If you do post it, lock any imported files in the scene so we can check them out. You said you used a polydoctor in Houdini, which can clean up geometry, but I don't think it would resolve your UV problem. As long as they are inherited before the sim, they should transfer correctly. Also test with a partial alembic write, so you don't need to wait for the entire write to do iterations.
- Tanto
- Member
- 401 posts
- Joined: Nov. 2016
- Offline
Thanks Midassilver, I ended up exporting .ass files instead of Alembic, since it rendered correctly in HtoA. The Polydoctor actually solved the problem when exporting a single frame, but the Alembic of the whole sequence crashed Maya. I'm thinking it might be a problem with Maya's Alembic importer, since re-importing the Alembic in Houdini worked perfectly.
- Midasssilver
- Member
- 310 posts
- Joined: July 2012
- Offline
- Tanto
- Member
- 401 posts
- Joined: Nov. 2016
- Offline
- Midasssilver
- Member
- 310 posts
- Joined: July 2012
- Offline
- Tanto
- Member
- 401 posts
- Joined: Nov. 2016
- Offline
- mrVal
- Member
- 4 posts
- Joined: Aug. 2014
- Offline
- Intuition
- Member
- 28 posts
- Joined: Jan. 2016
- Offline
I am at this step now as well.
Fractured an object using RBDMaterialFracture >ran object through UV process before it gets to RBDConfigure>RBDBulletSolver>FileCache
So now I have this pretty nice sim in FileCache that refreshes decently quick in Houdini but every attempt to get it back into Maya crashes Maya on import. Like... it doesn't kill Maya but rather freezes it up indefinitely.
I did successfully get a sim out of an earlier iteration of this using the convert node before the alembic ROP but that takes a very long time. About 13 hours to convert the whole sequence. Using Convert All Types to Polygon.
But for some reason this new iteration isn't successful in creating an Alembic that Maya can import. The Earlier iteration that worked didn't have UVs for the inner pieces and this version does. I can read the UVs if I preview the convert node after the File Cache. So they are transferring across the node network. Just need a way to make an Alembic that is usable in Maya.
Fractured an object using RBDMaterialFracture >ran object through UV process before it gets to RBDConfigure>RBDBulletSolver>FileCache
So now I have this pretty nice sim in FileCache that refreshes decently quick in Houdini but every attempt to get it back into Maya crashes Maya on import. Like... it doesn't kill Maya but rather freezes it up indefinitely.
I did successfully get a sim out of an earlier iteration of this using the convert node before the alembic ROP but that takes a very long time. About 13 hours to convert the whole sequence. Using Convert All Types to Polygon.
But for some reason this new iteration isn't successful in creating an Alembic that Maya can import. The Earlier iteration that worked didn't have UVs for the inner pieces and this version does. I can read the UVs if I preview the convert node after the File Cache. So they are transferring across the node network. Just need a way to make an Alembic that is usable in Maya.
- Intuition
- Member
- 28 posts
- Joined: Jan. 2016
- Offline
Switched convert node to From Type "All Types" and Convert To "Polygon Soup" and the alembic successfully makes it into Maya.
Scrubs pretty nicely as well. BUT... no UVs
I can still see them at the Convert node and the other nodes to test. But just ran from Convert to Alembic Rop to try and get it out to Maya. So It does make it to Maya but no UVs. Any idea how to force the UV attribute into the Alembic file?
Scrubs pretty nicely as well. BUT... no UVs
I can still see them at the Convert node and the other nodes to test. But just ran from Convert to Alembic Rop to try and get it out to Maya. So It does make it to Maya but no UVs. Any idea how to force the UV attribute into the Alembic file?
- sepu
- Member
- 432 posts
- Joined: Feb. 2012
- Offline
-
- Quick Links