Hi Sebastian Do you mind sending us the Alembic file you exported from Houdini? Vec3f is a basic type we support in XSI Alembic, unless Houdini exports the data into some unexpected Alembic type.
From: [email protected] [mailto:[email protected]] On Behalf Of Sebastian Kowalski Sent: Thursday, September 11, 2014 3:45 AM To: [email protected] Subject: Re: alembic from hou to xsi issues I can work with that issue. just writing 3 different float attributes for every vector attribute I need. Stupid, but a workaround,....again. s. Am 10.09.2014 um 21:21 schrieb Andy Goehler <[email protected]<mailto:[email protected]>>: Hi Sebastian, as already mentioned Exocortex Crate does this reliable. See here: http://exocortex.com/blog/crate_custom_attribute_softimage Just a side note, getting custom attributes from XSI into Houdini can be a pain too and I've had much better luck exporting those from 2015 with its onboard Alembic than with Crate. Andy On Sep 10, 2014, at 17:29, Sebastian Kowalski <[email protected]<mailto:[email protected]>> wrote: I am exporting some points into an alembic file from houdini to xsi and stumble on one issue. Transferring attributes works good for what you could call 'factory attributes' like P or v (we have to rename that to something with more than just one letter, cause it wont appear in xsi). But I also compute angular velocity (w) and couple other 'arbitrary user attributes', all vectors (3f). This suckers come in as single float value. Not even as a array of 3 values per point. As the same alembic file works like expected as re-import in houdini, I am pretty sure it is an eff up in xsi. Just want to make sure I am not doing something stupid. Anyone experience the same? Its with the 2015 version of xsi. sebastian ------------------------------ http://www.sekow.com<http://www.sekow.com/>
<<attachment: winmail.dat>>
