Hi Sebastian It seems that Houdini exported the ‘up’ attribute not as vec3f, but an array of floats. I know binary-wise it’s the same, but Alembic still treats it as custom data, and we don’t support these on our side. To work around this, can you convert them into vec3f type in Houdini first before exporting?
From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of l...@sekow.com Sent: Thursday, September 11, 2014 8:00 PM To: softimage@listproc.autodesk.com Subject: RE: alembic from hou to xsi issues hey, here is the file: https://drive.google.com/file/d/0B5cLxJeOrDLldXN2LUtQQTlaVTA/edit?usp=sharing there are following attributes included: - vel (3f), loads as vector - normal (3f), loads as vector - up (3f), loads as single float in softimage - angular (3f), loads as single float in softimage thanks for looking into it. -sebastian > Ho Chung Nguyen > <hochung.ngu...@autodesk.com<mailto:hochung.ngu...@autodesk.com>> hat am 11. > September 2014 um 06:00 geschrieben: > > > 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: > softimage-boun...@listproc.autodesk.com<mailto:softimage-boun...@listproc.autodesk.com> > > [mailto:softimage-boun...@listproc.autodesk.com]<mailto:[mailto:softimage-boun...@listproc.autodesk.com]> > On Behalf Of Sebastian Kowalski > Sent: Thursday, September 11, 2014 3:45 AM > To: softimage@listproc.autodesk.com<mailto:softimage@listproc.autodesk.com> > 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 > <lists.andy.goeh...@gmail.com<mailto:lists.andy.goeh...@gmail.com<mailto:lists.andy.goeh...@gmail.com%3cmailto:lists.andy.goeh...@gmail.com>>>: > > > 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 > <l...@sekow.com<mailto:l...@sekow.com<mailto:l...@sekow.com%3cmailto:l...@sekow.com>>> > 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/<http://www.sekow.com%3chttp:/www.sekow.com/>> > >
<<attachment: winmail.dat>>
