RE: alembic from hou to xsi issues
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 > 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 > 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 > 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/>> > > <>
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 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] On Behalf Of Sebastian > Kowalski > Sent: Thursday, September 11, 2014 3:45 AM > To: 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 > mailto: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 > mailto: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/> > >
RE: alembic from hou to xsi issues
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] On Behalf Of Sebastian Kowalski Sent: Thursday, September 11, 2014 3:45 AM To: 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 mailto: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 mailto: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/> <>
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 : > 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 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 >
Re: alembic from hou to xsi issues
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 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
Re: alembic from hou to xsi issues
With the crate version im sure you can rewire the abc point node and retrieve any custom values you might have assigned . If i can recall correctly you could hack the abc load point node, get the alembic points duplicate it and point the identifier to the attribute, and rewire it so it sets the needed data, but this was ages ago, and im not sure if has changed as i haven't used it in nearly two years, but im sure it worked on a color attribute from a houdini mesh. On Wed, Sep 10, 2014 at 5:53 PM, Angus Davidson wrote: > Why donšt you try the exocortex crate implementation, you can use the > trial that works on 100 frames or so. > > On 2014/09/10, 5:29 PM, "Sebastian Kowalski" 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 > > style="width:100%;"> > > size="1" color="#99">This communication > is intended for the addressee only. It is confidential. If you have > received this communication in error, please notify us immediately and > destroy the original message. You may not copy or disseminate this > communication without the permission of the University. Only authorised > signatories are competent to enter into agreements on behalf of the > University and recipients are thus advised that the content of this message > may not be legally binding on the University and may contain the personal > views and opinions of the author, which are not necessarily the views and > opinions of The University of the Witwatersrand, Johannesburg. All > agreements between the University and outsiders are subject to South > African Law unless the University agrees in writing to the contrary. > > > > > >
Re: alembic from hou to xsi issues
Why don¹t you try the exocortex crate implementation, you can use the trial that works on 100 frames or so. On 2014/09/10, 5:29 PM, "Sebastian Kowalski" 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 This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary.
alembic from hou to xsi issues
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
