@animagic
Well there are already the "traditional links" to be used such as *.obj and *.fbx import/export, now including morphs with H16. iClone can also export alembic files but it is still one way to Houdini. We would need iClone alembic import to bring back some simulations into iClone.
What would be great is to have OpenVDB import into iClone too but as these carry heavy volumic data (3d data grids) this is another beast to render in realtime or even at interactive rates.
One workaround I can think of for now is to export some blocking assets and camera from iClone to Houdini, then render/bake volume simulations to popVideos/Bilboards/Sprites and use those back into iClone.
Last "link" would be to have Houdini Engine as a plugin to iClone. With the upcoming iClone API, perhaps this will be possible.
To clarify what kind of data could be transferred through which channel:
- OpenVDB files (*.vdb) carry data grids which embed density, velocity, temperature, fuel, etc.. those are useful for smoke, explosion, etc..
- Alembic files (*.abc) carry cameras, polygonal geometries, particles, transforms, useful for water simulations (you nearly always reconstruct polygon mesh geometries from water and viscous fluids simulation for rendering, and use particles for water splashes, foam, etc..), also useful for everything that deform (clothes, soft bodies, etc..) or not (rigid body dynamics).
- Filmbox files (*.fbx) for textured polygonal meshes (alembic does not carry textures nor material settings, only surface names), skinned characters, static or morphable geometries, hierarchical skeletons, cameras
- Wavefront Object files (*.obj) for textured polygonal meshes, morphs
--
guy rabiller | GOETZIWOOD STUDIOS
"N.O.E." (Nations Of Earth) Sci-Fi TV Show, Showrunner.
Edited
7 Years Ago by
grabiller