Re: ICE Exodus - porting ICE to VEX part 1
aha...(scratching head) ok, i guess, more playing with this stuff will show the way ))) i think we should organize a crusade for porting our favourite ICE solutions into VEX... and the transition problems will reveal themselves, just like the answers 2014-05-06 17:47 GMT+04:00 Andy Goehler : > with the 'parameter' node you can get data > > > On 06.05.2014, at 15:42, Nika Ragua wrote: > > i mean, ok, i inserted the bind export node, but how to read it now? what > will be the get data analog? > > > 2014-05-06 17:30 GMT+04:00 Nika Ragua : > >> h...bind export node...i write blind export ahahah ))) okay, i`ll dig >> it later, seems to be complex stuff... and could it be read in the same VEX >> tree, just like in ICE with get data? >> >> >> 2014-05-06 17:25 GMT+04:00 Andy Goehler : >> >> sure, go ahead and attach it. glad I could help a little bit. >>> >>> Andy >>> >>> Sent on the road >>> >>> On 06.05.2014, at 15:07, Nika Ragua wrote: >>> >>> Andy showed 4 different variants of doing the same thing in houdini - >>> very handy and illustrative. >>> Never knew about the Point Wrangle node - it is so cool - heh, i`m not >>> actually a great fan of inserting code in channels - damn hard to realize >>> how the stuff is working lately. >>> Point Wrangle could be a nice option. >>> >>> Andy, you did a great job !!! i want to attach your scenes to the video? >>> can i do it? >>> >>> >>> >>> >>> 2014-05-06 16:52 GMT+04:00 Nika Ragua : >>> the full sanostol answer in case i misundersood something to solve the mismatch in the results, add a degree to radians vop in You network in front of all trigonometric functions, like sin and cos, they expect all values in radians. in hscript degrees are ok for the parameter stuff, I'm not sure what You are trying to achive. It looks like You are writing data to geometry in the first set data , and then read it out later. I'm not sure why You want this, but that does not work that way in houdini,You can not work import data in the same vex tree that is set here. that must happen in a previous vopsop 2014-05-06 16:50 GMT+04:00 Nika Ragua : > How to port our precious ICE stuff into houdini vex. Questions raised > - how to create a custom parameter in VEX, just like we do in ICE, and why > there are different results in math. > > ok i got the answers from houdini experts - sanostol and Stefano > Jannuzzo > > 1 You can not work import data in the same vex tree that is set here. > that must happen in a previous vopsop > 2 I think the problem is with the trigonometry nodes, since ICE treats > the input as degrees, Houdini as radians. > > You are mixing the two in your graphs, however if you want to get the > same behavior in Houdini, you should plug a dagtorad node between your t > and the sin and cos nodes. > dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg > > > 2014-05-06 16:45 GMT+04:00 Nika Ragua : > > thank you, Stefano, your help is much appreciated !!! >> >> >> 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo < >> stefano.jannu...@gmail.com>: >> >> Ooops, too late I read the same answer on the houdini forum >>> >>> >>> On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo < >>> stefano.jannu...@gmail.com> wrote: >>> Nice. I think the problem is with the trigonometry nodes, since ICE treats the input as degrees, Houdini as radians. You are mixing the two in your graphs, however if you want to get the same behavior in Houdini, you should plug a dagtorad node between your t and the sin and cos nodes. Ciao On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions > raised - how to create a custom parameter in VEX, just like we do in > ICE, > and why there are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha > > >>> >> > >>> >> >
Re: ICE Exodus - porting ICE to VEX part 1
or with just the bind node Am 06.05.2014 um 15:47 schrieb Andy Goehler : > with the 'parameter' node you can get data > > > On 06.05.2014, at 15:42, Nika Ragua wrote: > >> i mean, ok, i inserted the bind export node, but how to read it now? what >> will be the get data analog? >> >> >> 2014-05-06 17:30 GMT+04:00 Nika Ragua : >> h...bind export node...i write blind export ahahah ))) okay, i`ll dig it >> later, seems to be complex stuff... and could it be read in the same VEX >> tree, just like in ICE with get data? >> >> >> 2014-05-06 17:25 GMT+04:00 Andy Goehler : >> >> sure, go ahead and attach it. glad I could help a little bit. >> >> Andy >> >> Sent on the road >> >> On 06.05.2014, at 15:07, Nika Ragua wrote: >> >>> Andy showed 4 different variants of doing the same thing in houdini - very >>> handy and illustrative. >>> Never knew about the Point Wrangle node - it is so cool - heh, i`m not >>> actually a great fan of inserting code in channels - damn hard to realize >>> how the stuff is working lately. >>> Point Wrangle could be a nice option. >>> >>> Andy, you did a great job !!! i want to attach your scenes to the video? >>> can i do it? >>> >>> >>> >>> >>> 2014-05-06 16:52 GMT+04:00 Nika Ragua : >>> the full sanostol answer in case i misundersood something >>> >>> to solve the mismatch in the results, add a degree to radians vop in You >>> network in front of all trigonometric functions, like sin and cos, they >>> expect all values in radians. in hscript degrees are ok >>> >>> for the parameter stuff, I'm not sure what You are trying to achive. It >>> looks like You are writing data to geometry in the first set data , and >>> then read it out later. I'm not sure why You want this, but that does not >>> work that way in houdini,You can not work import data in the same vex tree >>> that is set here. that must happen in a previous vopsop >>> >>> >>> 2014-05-06 16:50 GMT+04:00 Nika Ragua : >>> >>> >>> How to port our precious ICE stuff into houdini vex. Questions raised - how >>> to create a custom parameter in VEX, just like we do in ICE, and why there >>> are different results in math. >>> >>> ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo >>> >>> 1 You can not work import data in the same vex tree that is set here. that >>> must happen in a previous vopsop >>> 2 I think the problem is with the trigonometry nodes, since ICE treats the >>> input as degrees, Houdini as radians. >>> >>> You are mixing the two in your graphs, however if you want to get the same >>> behavior in Houdini, you should plug a dagtorad node between your t and the >>> sin and cos nodes. >>> dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg >>> >>> >>> 2014-05-06 16:45 GMT+04:00 Nika Ragua : >>> >>> thank you, Stefano, your help is much appreciated !!! >>> >>> >>> 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo : >>> >>> Ooops, too late I read the same answer on the houdini forum >>> >>> >>> On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo >>> wrote: >>> Nice. >>> I think the problem is with the trigonometry nodes, since ICE treats the >>> input as degrees, Houdini as radians. >>> You are mixing the two in your graphs, however if you want to get the same >>> behavior in Houdini, you should plug a dagtorad node between your t and the >>> sin and cos nodes. >>> Ciao >>> >>> >>> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: >>> >>> yo, raps !!! >>> >>> friends, take a look >>> https://vimeo.com/94066674 >>> >>> How to port our precious ICE stuff into houdini vex. Questions raised - how >>> to create a custom parameter in VEX, just like we do in ICE, and why there >>> are different results in math. >>> This is interesting i think. >>> If you know the answers feel free to comment ))) >>> Hakuna Matata ))) ahahahaha >>> >>> >>> >>> >>> >>> >>> >> >>
Re: ICE Exodus - porting ICE to VEX part 1
with the 'parameter' node you can get data > On 06.05.2014, at 15:42, Nika Ragua wrote: > > i mean, ok, i inserted the bind export node, but how to read it now? what > will be the get data analog? > > > 2014-05-06 17:30 GMT+04:00 Nika Ragua : >> h...bind export node...i write blind export ahahah ))) okay, i`ll dig it >> later, seems to be complex stuff... and could it be read in the same VEX >> tree, just like in ICE with get data? >> >> >> 2014-05-06 17:25 GMT+04:00 Andy Goehler : >> >>> sure, go ahead and attach it. glad I could help a little bit. >>> >>> Andy >>> >>> Sent on the road >>> On 06.05.2014, at 15:07, Nika Ragua wrote: Andy showed 4 different variants of doing the same thing in houdini - very handy and illustrative. Never knew about the Point Wrangle node - it is so cool - heh, i`m not actually a great fan of inserting code in channels - damn hard to realize how the stuff is working lately. Point Wrangle could be a nice option. Andy, you did a great job !!! i want to attach your scenes to the video? can i do it? 2014-05-06 16:52 GMT+04:00 Nika Ragua : > the full sanostol answer in case i misundersood something > > to solve the mismatch in the results, add a degree to radians vop in You > network in front of all trigonometric functions, like sin and cos, they > expect all values in radians. in hscript degrees are ok > > for the parameter stuff, I'm not sure what You are trying to achive. It > looks like You are writing data to geometry in the first set data , and > then read it out later. I'm not sure why You want this, but that does not > work that way in houdini,You can not work import data in the same vex > tree that is set here. that must happen in a previous vopsop > > > 2014-05-06 16:50 GMT+04:00 Nika Ragua : > >> >> How to port our precious ICE stuff into houdini vex. Questions raised - >> how to create a custom parameter in VEX, just like we do in ICE, and why >> there are different results in math. >> >> ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo >> >> 1 You can not work import data in the same vex tree that is set here. >> that must happen in a previous vopsop >> 2 I think the problem is with the trigonometry nodes, since ICE treats >> the input as degrees, Houdini as radians. >> >> You are mixing the two in your graphs, however if you want to get the >> same behavior in Houdini, you should plug a dagtorad node between your t >> and the sin and cos nodes. >> dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg >> >> >> 2014-05-06 16:45 GMT+04:00 Nika Ragua : >> >>> thank you, Stefano, your help is much appreciated !!! >>> >>> >>> 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo >>> : >>> Ooops, too late I read the same answer on the houdini forum > On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo > wrote: > Nice. > I think the problem is with the trigonometry nodes, since ICE treats > the input as degrees, Houdini as radians. > You are mixing the two in your graphs, however if you want to get the > same behavior in Houdini, you should plug a dagtorad node between > your t and the sin and cos nodes. > Ciao > > >> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua >> wrote: >> >> yo, raps !!! >> >> friends, take a look >> https://vimeo.com/94066674 >> >> How to port our precious ICE stuff into houdini vex. Questions >> raised - how to create a custom parameter in VEX, just like we do in >> ICE, and why there are different results in math. >> This is interesting i think. >> If you know the answers feel free to comment ))) >> Hakuna Matata ))) ahahahaha >
Re: ICE Exodus - porting ICE to VEX part 1
I believe this is not possible inside the same VOPSOP. Andy > On 06.05.2014, at 15:30, Nika Ragua wrote: > > h...bind export node...i write blind export ahahah ))) okay, i`ll dig it > later, seems to be complex stuff... and could it be read in the same VEX > tree, just like in ICE with get data? > > > 2014-05-06 17:25 GMT+04:00 Andy Goehler : >> sure, go ahead and attach it. glad I could help a little bit. >> >> Andy >> >> Sent on the road >> >>> On 06.05.2014, at 15:07, Nika Ragua wrote: >>> >>> Andy showed 4 different variants of doing the same thing in houdini - very >>> handy and illustrative. >>> Never knew about the Point Wrangle node - it is so cool - heh, i`m not >>> actually a great fan of inserting code in channels - damn hard to realize >>> how the stuff is working lately. >>> Point Wrangle could be a nice option. >>> >>> Andy, you did a great job !!! i want to attach your scenes to the video? >>> can i do it? >>> >>> >>> >>> >>> 2014-05-06 16:52 GMT+04:00 Nika Ragua : the full sanostol answer in case i misundersood something to solve the mismatch in the results, add a degree to radians vop in You network in front of all trigonometric functions, like sin and cos, they expect all values in radians. in hscript degrees are ok for the parameter stuff, I'm not sure what You are trying to achive. It looks like You are writing data to geometry in the first set data , and then read it out later. I'm not sure why You want this, but that does not work that way in houdini,You can not work import data in the same vex tree that is set here. that must happen in a previous vopsop 2014-05-06 16:50 GMT+04:00 Nika Ragua : > > How to port our precious ICE stuff into houdini vex. Questions raised - > how to create a custom parameter in VEX, just like we do in ICE, and why > there are different results in math. > > ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo > > 1 You can not work import data in the same vex tree that is set here. > that must happen in a previous vopsop > 2 I think the problem is with the trigonometry nodes, since ICE treats > the input as degrees, Houdini as radians. > > You are mixing the two in your graphs, however if you want to get the > same behavior in Houdini, you should plug a dagtorad node between your t > and the sin and cos nodes. > dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg > > > 2014-05-06 16:45 GMT+04:00 Nika Ragua : > >> thank you, Stefano, your help is much appreciated !!! >> >> >> 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo : >> >>> Ooops, too late I read the same answer on the houdini forum >>> >>> On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo wrote: Nice. I think the problem is with the trigonometry nodes, since ICE treats the input as degrees, Houdini as radians. You are mixing the two in your graphs, however if you want to get the same behavior in Houdini, you should plug a dagtorad node between your t and the sin and cos nodes. Ciao > On Tue, May 6, 2014 at 9:09 AM, Nika Ragua > wrote: > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions raised > - how to create a custom parameter in VEX, just like we do in ICE, > and why there are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha >
Re: ICE Exodus - porting ICE to VEX part 1
i mean, ok, i inserted the bind export node, but how to read it now? what will be the get data analog? 2014-05-06 17:30 GMT+04:00 Nika Ragua : > h...bind export node...i write blind export ahahah ))) okay, i`ll dig > it later, seems to be complex stuff... and could it be read in the same VEX > tree, just like in ICE with get data? > > > 2014-05-06 17:25 GMT+04:00 Andy Goehler : > > sure, go ahead and attach it. glad I could help a little bit. >> >> Andy >> >> Sent on the road >> >> On 06.05.2014, at 15:07, Nika Ragua wrote: >> >> Andy showed 4 different variants of doing the same thing in houdini - >> very handy and illustrative. >> Never knew about the Point Wrangle node - it is so cool - heh, i`m not >> actually a great fan of inserting code in channels - damn hard to realize >> how the stuff is working lately. >> Point Wrangle could be a nice option. >> >> Andy, you did a great job !!! i want to attach your scenes to the video? >> can i do it? >> >> >> >> >> 2014-05-06 16:52 GMT+04:00 Nika Ragua : >> >>> the full sanostol answer in case i misundersood something >>> >>> to solve the mismatch in the results, add a degree to radians vop in You >>> network in front of all trigonometric functions, like sin and cos, they >>> expect all values in radians. in hscript degrees are ok >>> >>> for the parameter stuff, I'm not sure what You are trying to achive. It >>> looks like You are writing data to geometry in the first set data , and >>> then read it out later. I'm not sure why You want this, but that does not >>> work that way in houdini,You can not work import data in the same vex tree >>> that is set here. that must happen in a previous vopsop >>> >>> >>> 2014-05-06 16:50 GMT+04:00 Nika Ragua : >>> >>> How to port our precious ICE stuff into houdini vex. Questions raised - how to create a custom parameter in VEX, just like we do in ICE, and why there are different results in math. ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo 1 You can not work import data in the same vex tree that is set here. that must happen in a previous vopsop 2 I think the problem is with the trigonometry nodes, since ICE treats the input as degrees, Houdini as radians. You are mixing the two in your graphs, however if you want to get the same behavior in Houdini, you should plug a dagtorad node between your t and the sin and cos nodes. dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg 2014-05-06 16:45 GMT+04:00 Nika Ragua : thank you, Stefano, your help is much appreciated !!! > > > 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo < > stefano.jannu...@gmail.com>: > > Ooops, too late I read the same answer on the houdini forum >> >> >> On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo < >> stefano.jannu...@gmail.com> wrote: >> >>> Nice. >>> I think the problem is with the trigonometry nodes, since ICE treats >>> the input as degrees, Houdini as radians. >>> You are mixing the two in your graphs, however if you want to get >>> the same behavior in Houdini, you should plug a dagtorad node between >>> your >>> t and the sin and cos nodes. >>> Ciao >>> >>> >>> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: >>> yo, raps !!! friends, take a look https://vimeo.com/94066674 How to port our precious ICE stuff into houdini vex. Questions raised - how to create a custom parameter in VEX, just like we do in ICE, and why there are different results in math. This is interesting i think. If you know the answers feel free to comment ))) Hakuna Matata ))) ahahahaha >>> >> > >>> >> >
Re: ICE Exodus - porting ICE to VEX part 1
h...bind export node...i write blind export ahahah ))) okay, i`ll dig it later, seems to be complex stuff... and could it be read in the same VEX tree, just like in ICE with get data? 2014-05-06 17:25 GMT+04:00 Andy Goehler : > sure, go ahead and attach it. glad I could help a little bit. > > Andy > > Sent on the road > > On 06.05.2014, at 15:07, Nika Ragua wrote: > > Andy showed 4 different variants of doing the same thing in houdini - > very handy and illustrative. > Never knew about the Point Wrangle node - it is so cool - heh, i`m not > actually a great fan of inserting code in channels - damn hard to realize > how the stuff is working lately. > Point Wrangle could be a nice option. > > Andy, you did a great job !!! i want to attach your scenes to the video? > can i do it? > > > > > 2014-05-06 16:52 GMT+04:00 Nika Ragua : > >> the full sanostol answer in case i misundersood something >> >> to solve the mismatch in the results, add a degree to radians vop in You >> network in front of all trigonometric functions, like sin and cos, they >> expect all values in radians. in hscript degrees are ok >> >> for the parameter stuff, I'm not sure what You are trying to achive. It >> looks like You are writing data to geometry in the first set data , and >> then read it out later. I'm not sure why You want this, but that does not >> work that way in houdini,You can not work import data in the same vex tree >> that is set here. that must happen in a previous vopsop >> >> >> 2014-05-06 16:50 GMT+04:00 Nika Ragua : >> >> >>> How to port our precious ICE stuff into houdini vex. Questions raised - >>> how to create a custom parameter in VEX, just like we do in ICE, and why >>> there are different results in math. >>> >>> ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo >>> >>> 1 You can not work import data in the same vex tree that is set here. >>> that must happen in a previous vopsop >>> 2 I think the problem is with the trigonometry nodes, since ICE treats >>> the input as degrees, Houdini as radians. >>> >>> You are mixing the two in your graphs, however if you want to get the >>> same behavior in Houdini, you should plug a dagtorad node between your t >>> and the sin and cos nodes. >>> dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg >>> >>> >>> 2014-05-06 16:45 GMT+04:00 Nika Ragua : >>> >>> thank you, Stefano, your help is much appreciated !!! 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo >>> >: Ooops, too late I read the same answer on the houdini forum > > > On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo < > stefano.jannu...@gmail.com> wrote: > >> Nice. >> I think the problem is with the trigonometry nodes, since ICE treats >> the input as degrees, Houdini as radians. >> You are mixing the two in your graphs, however if you want to get the >> same behavior in Houdini, you should plug a dagtorad node between your t >> and the sin and cos nodes. >> Ciao >> >> >> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: >> >>> >>> yo, raps !!! >>> >>> friends, take a look >>> https://vimeo.com/94066674 >>> >>> How to port our precious ICE stuff into houdini vex. Questions >>> raised - how to create a custom parameter in VEX, just like we do in >>> ICE, >>> and why there are different results in math. >>> This is interesting i think. >>> If you know the answers feel free to comment ))) >>> Hakuna Matata ))) ahahahaha >>> >>> >> > >>> >> >
Re: ICE Exodus - porting ICE to VEX part 1
sure, go ahead and attach it. glad I could help a little bit. Andy Sent on the road > On 06.05.2014, at 15:07, Nika Ragua wrote: > > Andy showed 4 different variants of doing the same thing in houdini - very > handy and illustrative. > Never knew about the Point Wrangle node - it is so cool - heh, i`m not > actually a great fan of inserting code in channels - damn hard to realize how > the stuff is working lately. > Point Wrangle could be a nice option. > > Andy, you did a great job !!! i want to attach your scenes to the video? > can i do it? > > > > > 2014-05-06 16:52 GMT+04:00 Nika Ragua : >> the full sanostol answer in case i misundersood something >> >> to solve the mismatch in the results, add a degree to radians vop in You >> network in front of all trigonometric functions, like sin and cos, they >> expect all values in radians. in hscript degrees are ok >> >> for the parameter stuff, I'm not sure what You are trying to achive. It >> looks like You are writing data to geometry in the first set data , and then >> read it out later. I'm not sure why You want this, but that does not work >> that way in houdini,You can not work import data in the same vex tree that >> is set here. that must happen in a previous vopsop >> >> >> 2014-05-06 16:50 GMT+04:00 Nika Ragua : >> >>> >>> How to port our precious ICE stuff into houdini vex. Questions raised - how >>> to create a custom parameter in VEX, just like we do in ICE, and why there >>> are different results in math. >>> >>> ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo >>> >>> 1 You can not work import data in the same vex tree that is set here. that >>> must happen in a previous vopsop >>> 2 I think the problem is with the trigonometry nodes, since ICE treats the >>> input as degrees, Houdini as radians. >>> >>> You are mixing the two in your graphs, however if you want to get the same >>> behavior in Houdini, you should plug a dagtorad node between your t and the >>> sin and cos nodes. >>> dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg >>> >>> >>> 2014-05-06 16:45 GMT+04:00 Nika Ragua : >>> thank you, Stefano, your help is much appreciated !!! 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo : > Ooops, too late I read the same answer on the houdini forum > > >> On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo >> wrote: >> Nice. >> I think the problem is with the trigonometry nodes, since ICE treats the >> input as degrees, Houdini as radians. >> You are mixing the two in your graphs, however if you want to get the >> same behavior in Houdini, you should plug a dagtorad node between your t >> and the sin and cos nodes. >> Ciao >> >> >>> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua >>> wrote: >>> >>> yo, raps !!! >>> >>> friends, take a look >>> https://vimeo.com/94066674 >>> >>> How to port our precious ICE stuff into houdini vex. Questions raised - >>> how to create a custom parameter in VEX, just like we do in ICE, and >>> why there are different results in math. >>> This is interesting i think. >>> If you know the answers feel free to comment ))) >>> Hakuna Matata ))) ahahahaha >
Re: ICE Exodus - porting ICE to VEX part 1
bind export node = set data node Am 06.05.2014 um 15:22 schrieb Nika Ragua : > > Sebastian, sorry, i don`t get you...think of what as a set data node? > > > 2014-05-06 17:14 GMT+04:00 Sebastian Kowalski : > think of it as a set data node > > > Am 06.05.2014 um 15:08 schrieb Nika Ragua : > >> And what is Blind Export again? >> >> >> 2014-05-06 17:07 GMT+04:00 Nika Ragua : >> Andy showed 4 different variants of doing the same thing in houdini - very >> handy and illustrative. >> Never knew about the Point Wrangle node - it is so cool - heh, i`m not >> actually a great fan of inserting code in channels - damn hard to realize >> how the stuff is working lately. >> Point Wrangle could be a nice option. >> >> Andy, you did a great job !!! i want to attach your scenes to the video? >> can i do it? >> >> >> >> >> 2014-05-06 16:52 GMT+04:00 Nika Ragua : >> >> the full sanostol answer in case i misundersood something >> >> to solve the mismatch in the results, add a degree to radians vop in You >> network in front of all trigonometric functions, like sin and cos, they >> expect all values in radians. in hscript degrees are ok >> >> for the parameter stuff, I'm not sure what You are trying to achive. It >> looks like You are writing data to geometry in the first set data , and then >> read it out later. I'm not sure why You want this, but that does not work >> that way in houdini,You can not work import data in the same vex tree that >> is set here. that must happen in a previous vopsop >> >> >> 2014-05-06 16:50 GMT+04:00 Nika Ragua : >> >> >> How to port our precious ICE stuff into houdini vex. Questions raised - how >> to create a custom parameter in VEX, just like we do in ICE, and why there >> are different results in math. >> >> ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo >> >> 1 You can not work import data in the same vex tree that is set here. that >> must happen in a previous vopsop >> 2 I think the problem is with the trigonometry nodes, since ICE treats the >> input as degrees, Houdini as radians. >> >> You are mixing the two in your graphs, however if you want to get the same >> behavior in Houdini, you should plug a dagtorad node between your t and the >> sin and cos nodes. >> dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg >> >> >> 2014-05-06 16:45 GMT+04:00 Nika Ragua : >> >> thank you, Stefano, your help is much appreciated !!! >> >> >> 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo : >> >> Ooops, too late I read the same answer on the houdini forum >> >> >> On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo >> wrote: >> Nice. >> I think the problem is with the trigonometry nodes, since ICE treats the >> input as degrees, Houdini as radians. >> You are mixing the two in your graphs, however if you want to get the same >> behavior in Houdini, you should plug a dagtorad node between your t and the >> sin and cos nodes. >> Ciao >> >> >> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: >> >> yo, raps !!! >> >> friends, take a look >> https://vimeo.com/94066674 >> >> How to port our precious ICE stuff into houdini vex. Questions raised - how >> to create a custom parameter in VEX, just like we do in ICE, and why there >> are different results in math. >> This is interesting i think. >> If you know the answers feel free to comment ))) >> Hakuna Matata ))) ahahahaha >> >> >> >> >> >> >> >> > >
Re: ICE Exodus - porting ICE to VEX part 1
Sebastian, sorry, i don`t get you...think of what as a set data node? 2014-05-06 17:14 GMT+04:00 Sebastian Kowalski : > think of it as a set data node > > > Am 06.05.2014 um 15:08 schrieb Nika Ragua : > > And what is Blind Export again? > > > 2014-05-06 17:07 GMT+04:00 Nika Ragua : > >> Andy showed 4 different variants of doing the same thing in houdini - >> very handy and illustrative. >> Never knew about the Point Wrangle node - it is so cool - heh, i`m not >> actually a great fan of inserting code in channels - damn hard to realize >> how the stuff is working lately. >> Point Wrangle could be a nice option. >> >> Andy, you did a great job !!! i want to attach your scenes to the video? >> can i do it? >> >> >> >> >> 2014-05-06 16:52 GMT+04:00 Nika Ragua : >> >> the full sanostol answer in case i misundersood something >>> >>> to solve the mismatch in the results, add a degree to radians vop in You >>> network in front of all trigonometric functions, like sin and cos, they >>> expect all values in radians. in hscript degrees are ok >>> >>> for the parameter stuff, I'm not sure what You are trying to achive. It >>> looks like You are writing data to geometry in the first set data , and >>> then read it out later. I'm not sure why You want this, but that does not >>> work that way in houdini,You can not work import data in the same vex tree >>> that is set here. that must happen in a previous vopsop >>> >>> >>> 2014-05-06 16:50 GMT+04:00 Nika Ragua : >>> >>> How to port our precious ICE stuff into houdini vex. Questions raised - how to create a custom parameter in VEX, just like we do in ICE, and why there are different results in math. ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo 1 You can not work import data in the same vex tree that is set here. that must happen in a previous vopsop 2 I think the problem is with the trigonometry nodes, since ICE treats the input as degrees, Houdini as radians. You are mixing the two in your graphs, however if you want to get the same behavior in Houdini, you should plug a dagtorad node between your t and the sin and cos nodes. dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg 2014-05-06 16:45 GMT+04:00 Nika Ragua : thank you, Stefano, your help is much appreciated !!! > > > 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo < > stefano.jannu...@gmail.com>: > > Ooops, too late I read the same answer on the houdini forum >> >> >> On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo < >> stefano.jannu...@gmail.com> wrote: >> >>> Nice. >>> I think the problem is with the trigonometry nodes, since ICE treats >>> the input as degrees, Houdini as radians. >>> You are mixing the two in your graphs, however if you want to get >>> the same behavior in Houdini, you should plug a dagtorad node between >>> your >>> t and the sin and cos nodes. >>> Ciao >>> >>> >>> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: >>> yo, raps !!! friends, take a look https://vimeo.com/94066674 How to port our precious ICE stuff into houdini vex. Questions raised - how to create a custom parameter in VEX, just like we do in ICE, and why there are different results in math. This is interesting i think. If you know the answers feel free to comment ))) Hakuna Matata ))) ahahahaha >>> >> > >>> >> > >
Re: ICE Exodus - porting ICE to VEX part 1
think of it as a set data node Am 06.05.2014 um 15:08 schrieb Nika Ragua : > And what is Blind Export again? > > > 2014-05-06 17:07 GMT+04:00 Nika Ragua : > Andy showed 4 different variants of doing the same thing in houdini - very > handy and illustrative. > Never knew about the Point Wrangle node - it is so cool - heh, i`m not > actually a great fan of inserting code in channels - damn hard to realize how > the stuff is working lately. > Point Wrangle could be a nice option. > > Andy, you did a great job !!! i want to attach your scenes to the video? > can i do it? > > > > > 2014-05-06 16:52 GMT+04:00 Nika Ragua : > > the full sanostol answer in case i misundersood something > > to solve the mismatch in the results, add a degree to radians vop in You > network in front of all trigonometric functions, like sin and cos, they > expect all values in radians. in hscript degrees are ok > > for the parameter stuff, I'm not sure what You are trying to achive. It looks > like You are writing data to geometry in the first set data , and then read > it out later. I'm not sure why You want this, but that does not work that way > in houdini,You can not work import data in the same vex tree that is set > here. that must happen in a previous vopsop > > > 2014-05-06 16:50 GMT+04:00 Nika Ragua : > > > How to port our precious ICE stuff into houdini vex. Questions raised - how > to create a custom parameter in VEX, just like we do in ICE, and why there > are different results in math. > > ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo > > 1 You can not work import data in the same vex tree that is set here. that > must happen in a previous vopsop > 2 I think the problem is with the trigonometry nodes, since ICE treats the > input as degrees, Houdini as radians. > > You are mixing the two in your graphs, however if you want to get the same > behavior in Houdini, you should plug a dagtorad node between your t and the > sin and cos nodes. > dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg > > > 2014-05-06 16:45 GMT+04:00 Nika Ragua : > > thank you, Stefano, your help is much appreciated !!! > > > 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo : > > Ooops, too late I read the same answer on the houdini forum > > > On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo > wrote: > Nice. > I think the problem is with the trigonometry nodes, since ICE treats the > input as degrees, Houdini as radians. > You are mixing the two in your graphs, however if you want to get the same > behavior in Houdini, you should plug a dagtorad node between your t and the > sin and cos nodes. > Ciao > > > On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions raised - how > to create a custom parameter in VEX, just like we do in ICE, and why there > are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha > > > > > > > >
Re: ICE Exodus - porting ICE to VEX part 1
And what is Blind Export again? 2014-05-06 17:07 GMT+04:00 Nika Ragua : > Andy showed 4 different variants of doing the same thing in houdini - > very handy and illustrative. > Never knew about the Point Wrangle node - it is so cool - heh, i`m not > actually a great fan of inserting code in channels - damn hard to realize > how the stuff is working lately. > Point Wrangle could be a nice option. > > Andy, you did a great job !!! i want to attach your scenes to the video? > can i do it? > > > > > 2014-05-06 16:52 GMT+04:00 Nika Ragua : > > the full sanostol answer in case i misundersood something >> >> to solve the mismatch in the results, add a degree to radians vop in You >> network in front of all trigonometric functions, like sin and cos, they >> expect all values in radians. in hscript degrees are ok >> >> for the parameter stuff, I'm not sure what You are trying to achive. It >> looks like You are writing data to geometry in the first set data , and >> then read it out later. I'm not sure why You want this, but that does not >> work that way in houdini,You can not work import data in the same vex tree >> that is set here. that must happen in a previous vopsop >> >> >> 2014-05-06 16:50 GMT+04:00 Nika Ragua : >> >> >>> How to port our precious ICE stuff into houdini vex. Questions raised - >>> how to create a custom parameter in VEX, just like we do in ICE, and why >>> there are different results in math. >>> >>> ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo >>> >>> 1 You can not work import data in the same vex tree that is set here. >>> that must happen in a previous vopsop >>> 2 I think the problem is with the trigonometry nodes, since ICE treats >>> the input as degrees, Houdini as radians. >>> >>> You are mixing the two in your graphs, however if you want to get the >>> same behavior in Houdini, you should plug a dagtorad node between your t >>> and the sin and cos nodes. >>> dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg >>> >>> >>> 2014-05-06 16:45 GMT+04:00 Nika Ragua : >>> >>> thank you, Stefano, your help is much appreciated !!! 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo >>> >: Ooops, too late I read the same answer on the houdini forum > > > On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo < > stefano.jannu...@gmail.com> wrote: > >> Nice. >> I think the problem is with the trigonometry nodes, since ICE treats >> the input as degrees, Houdini as radians. >> You are mixing the two in your graphs, however if you want to get the >> same behavior in Houdini, you should plug a dagtorad node between your t >> and the sin and cos nodes. >> Ciao >> >> >> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: >> >>> >>> yo, raps !!! >>> >>> friends, take a look >>> https://vimeo.com/94066674 >>> >>> How to port our precious ICE stuff into houdini vex. Questions >>> raised - how to create a custom parameter in VEX, just like we do in >>> ICE, >>> and why there are different results in math. >>> This is interesting i think. >>> If you know the answers feel free to comment ))) >>> Hakuna Matata ))) ahahahaha >>> >>> >> > >>> >> >
Re: ICE Exodus - porting ICE to VEX part 1
Andy showed 4 different variants of doing the same thing in houdini - very handy and illustrative. Never knew about the Point Wrangle node - it is so cool - heh, i`m not actually a great fan of inserting code in channels - damn hard to realize how the stuff is working lately. Point Wrangle could be a nice option. Andy, you did a great job !!! i want to attach your scenes to the video? can i do it? 2014-05-06 16:52 GMT+04:00 Nika Ragua : > the full sanostol answer in case i misundersood something > > to solve the mismatch in the results, add a degree to radians vop in You > network in front of all trigonometric functions, like sin and cos, they > expect all values in radians. in hscript degrees are ok > > for the parameter stuff, I'm not sure what You are trying to achive. It > looks like You are writing data to geometry in the first set data , and > then read it out later. I'm not sure why You want this, but that does not > work that way in houdini,You can not work import data in the same vex tree > that is set here. that must happen in a previous vopsop > > > 2014-05-06 16:50 GMT+04:00 Nika Ragua : > > >> How to port our precious ICE stuff into houdini vex. Questions raised - >> how to create a custom parameter in VEX, just like we do in ICE, and why >> there are different results in math. >> >> ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo >> >> 1 You can not work import data in the same vex tree that is set here. >> that must happen in a previous vopsop >> 2 I think the problem is with the trigonometry nodes, since ICE treats >> the input as degrees, Houdini as radians. >> >> You are mixing the two in your graphs, however if you want to get the >> same behavior in Houdini, you should plug a dagtorad node between your t >> and the sin and cos nodes. >> dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg >> >> >> 2014-05-06 16:45 GMT+04:00 Nika Ragua : >> >> thank you, Stefano, your help is much appreciated !!! >>> >>> >>> 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo >>> : >>> >>> Ooops, too late I read the same answer on the houdini forum On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo < stefano.jannu...@gmail.com> wrote: > Nice. > I think the problem is with the trigonometry nodes, since ICE treats > the input as degrees, Houdini as radians. > You are mixing the two in your graphs, however if you want to get the > same behavior in Houdini, you should plug a dagtorad node between your t > and the sin and cos nodes. > Ciao > > > On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: > >> >> yo, raps !!! >> >> friends, take a look >> https://vimeo.com/94066674 >> >> How to port our precious ICE stuff into houdini vex. Questions raised >> - how to create a custom parameter in VEX, just like we do in ICE, and >> why >> there are different results in math. >> This is interesting i think. >> If you know the answers feel free to comment ))) >> Hakuna Matata ))) ahahahaha >> >> > >>> >> >
Re: ICE Exodus - porting ICE to VEX part 1
the full sanostol answer in case i misundersood something to solve the mismatch in the results, add a degree to radians vop in You network in front of all trigonometric functions, like sin and cos, they expect all values in radians. in hscript degrees are ok for the parameter stuff, I'm not sure what You are trying to achive. It looks like You are writing data to geometry in the first set data , and then read it out later. I'm not sure why You want this, but that does not work that way in houdini,You can not work import data in the same vex tree that is set here. that must happen in a previous vopsop 2014-05-06 16:50 GMT+04:00 Nika Ragua : > > How to port our precious ICE stuff into houdini vex. Questions raised - > how to create a custom parameter in VEX, just like we do in ICE, and why > there are different results in math. > > ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo > > 1 You can not work import data in the same vex tree that is set here. that > must happen in a previous vopsop > 2 I think the problem is with the trigonometry nodes, since ICE treats the > input as degrees, Houdini as radians. > > You are mixing the two in your graphs, however if you want to get the same > behavior in Houdini, you should plug a dagtorad node between your t and the > sin and cos nodes. > dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg > > > 2014-05-06 16:45 GMT+04:00 Nika Ragua : > > thank you, Stefano, your help is much appreciated !!! >> >> >> 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo : >> >> Ooops, too late I read the same answer on the houdini forum >>> >>> >>> On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo < >>> stefano.jannu...@gmail.com> wrote: >>> Nice. I think the problem is with the trigonometry nodes, since ICE treats the input as degrees, Houdini as radians. You are mixing the two in your graphs, however if you want to get the same behavior in Houdini, you should plug a dagtorad node between your t and the sin and cos nodes. Ciao On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions raised > - how to create a custom parameter in VEX, just like we do in ICE, and why > there are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha > > >>> >> >
Re: ICE Exodus - porting ICE to VEX part 1
How to port our precious ICE stuff into houdini vex. Questions raised - how to create a custom parameter in VEX, just like we do in ICE, and why there are different results in math. ok i got the answers from houdini experts - sanostol and Stefano Jannuzzo 1 You can not work import data in the same vex tree that is set here. that must happen in a previous vopsop 2 I think the problem is with the trigonometry nodes, since ICE treats the input as degrees, Houdini as radians. You are mixing the two in your graphs, however if you want to get the same behavior in Houdini, you should plug a dagtorad node between your t and the sin and cos nodes. dropbox.com/s/olcfye6aea0dqmc/ice_cycloid_fix%20copy.jpg 2014-05-06 16:45 GMT+04:00 Nika Ragua : > thank you, Stefano, your help is much appreciated !!! > > > 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo : > > Ooops, too late I read the same answer on the houdini forum >> >> >> On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo < >> stefano.jannu...@gmail.com> wrote: >> >>> Nice. >>> I think the problem is with the trigonometry nodes, since ICE treats the >>> input as degrees, Houdini as radians. >>> You are mixing the two in your graphs, however if you want to get the >>> same behavior in Houdini, you should plug a dagtorad node between your t >>> and the sin and cos nodes. >>> Ciao >>> >>> >>> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: >>> yo, raps !!! friends, take a look https://vimeo.com/94066674 How to port our precious ICE stuff into houdini vex. Questions raised - how to create a custom parameter in VEX, just like we do in ICE, and why there are different results in math. This is interesting i think. If you know the answers feel free to comment ))) Hakuna Matata ))) ahahahaha >>> >> >
Re: ICE Exodus - porting ICE to VEX part 1
thank you, Stefano, your help is much appreciated !!! 2014-05-06 16:25 GMT+04:00 Stefano Jannuzzo : > Ooops, too late I read the same answer on the houdini forum > > > On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo < > stefano.jannu...@gmail.com> wrote: > >> Nice. >> I think the problem is with the trigonometry nodes, since ICE treats the >> input as degrees, Houdini as radians. >> You are mixing the two in your graphs, however if you want to get the >> same behavior in Houdini, you should plug a dagtorad node between your t >> and the sin and cos nodes. >> Ciao >> >> >> On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: >> >>> >>> yo, raps !!! >>> >>> friends, take a look >>> https://vimeo.com/94066674 >>> >>> How to port our precious ICE stuff into houdini vex. Questions raised - >>> how to create a custom parameter in VEX, just like we do in ICE, and why >>> there are different results in math. >>> This is interesting i think. >>> If you know the answers feel free to comment ))) >>> Hakuna Matata ))) ahahahaha >>> >>> >> >
Re: ICE Exodus - porting ICE to VEX part 1
Ooops, too late I read the same answer on the houdini forum On Tue, May 6, 2014 at 2:20 PM, Stefano Jannuzzo wrote: > Nice. > I think the problem is with the trigonometry nodes, since ICE treats the > input as degrees, Houdini as radians. > You are mixing the two in your graphs, however if you want to get the same > behavior in Houdini, you should plug a dagtorad node between your t and the > sin and cos nodes. > Ciao > > > On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: > >> >> yo, raps !!! >> >> friends, take a look >> https://vimeo.com/94066674 >> >> How to port our precious ICE stuff into houdini vex. Questions raised - >> how to create a custom parameter in VEX, just like we do in ICE, and why >> there are different results in math. >> This is interesting i think. >> If you know the answers feel free to comment ))) >> Hakuna Matata ))) ahahahaha >> >> >
Re: ICE Exodus - porting ICE to VEX part 1
Nice. I think the problem is with the trigonometry nodes, since ICE treats the input as degrees, Houdini as radians. You are mixing the two in your graphs, however if you want to get the same behavior in Houdini, you should plug a dagtorad node between your t and the sin and cos nodes. Ciao On Tue, May 6, 2014 at 9:09 AM, Nika Ragua wrote: > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions raised - > how to create a custom parameter in VEX, just like we do in ICE, and why > there are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha > >
Re: ICE Exodus - porting ICE to VEX part 1
There’s definitively something strange in VOPs or it’s something I have not wrapped my head around, but a simple point expression seems to do the job. Let’s take this further at the SESI forum so some Houdini cracks will have a look at it. I’ve uploaded the .hip there as I feel dirty attaching it to this list :-P Andy On May 06, 2014, at 9:09, Nika Ragua wrote: > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions raised - how > to create a custom parameter in VEX, just like we do in ICE, and why there > are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha >
Re: ICE Exodus - porting ICE to VEX part 1
Side Effects Software Inc. That’s my guess ;-) On May 06, 2014, at 11:52, Rob Chapman wrote: > Side Effects Software I = International...? > > > On 6 May 2014 10:40, Nika Ragua wrote: > aaah, i`m already there ))) didn`t know that it is named SESI > > > 2014-05-06 13:36 GMT+04:00 Andy Goehler : > > sidefx.com and then register for the forum. > > On May 06, 2014, at 11:28, Nika Ragua wrote: > >> thank you friends !!! >> SESI forum? what is it? Andy, could you give a link? >> And what is Blind Export? >> ahahah ))) great, great, more questions appearing...a good sign >> >> >> 2014-05-06 13:24 GMT+04:00 Andy Goehler : >> Hi Nika, >> >> very nice video. You should post this on the SESI forum too. With my limited >> VOP experience I was able to export data with ‘Bind Export’. I’m currently >> recreating your VOP setup to look into it. >> >> Andy >> >> >> >> On May 06, 2014, at 9:09, Nika Ragua wrote: >> >>> >>> yo, raps !!! >>> >>> friends, take a look >>> https://vimeo.com/94066674 >>> >>> How to port our precious ICE stuff into houdini vex. Questions raised - how >>> to create a custom parameter in VEX, just like we do in ICE, and why there >>> are different results in math. >>> This is interesting i think. >>> If you know the answers feel free to comment ))) >>> Hakuna Matata ))) ahahahaha >>> >> >> > > >
Re: ICE Exodus - porting ICE to VEX part 1
Side Effects Software I = International...? On 6 May 2014 10:40, Nika Ragua wrote: > aaah, i`m already there ))) didn`t know that it is named SESI > > > 2014-05-06 13:36 GMT+04:00 Andy Goehler : > > sidefx.com and then register for the forum. >> >> On May 06, 2014, at 11:28, Nika Ragua wrote: >> >> thank you friends !!! >> SESI forum? what is it? Andy, could you give a link? >> And what is Blind Export? >> ahahah ))) great, great, more questions appearing...a good sign >> >> >> 2014-05-06 13:24 GMT+04:00 Andy Goehler : >> >>> Hi Nika, >>> >>> very nice video. You should post this on the SESI forum too. With my >>> limited VOP experience I was able to export data with ‘Bind Export’. I’m >>> currently recreating your VOP setup to look into it. >>> >>> Andy >>> >>> >>> >>> On May 06, 2014, at 9:09, Nika Ragua wrote: >>> >>> >>> yo, raps !!! >>> >>> friends, take a look >>> https://vimeo.com/94066674 >>> >>> How to port our precious ICE stuff into houdini vex. Questions raised - >>> how to create a custom parameter in VEX, just like we do in ICE, and why >>> there are different results in math. >>> This is interesting i think. >>> If you know the answers feel free to comment ))) >>> Hakuna Matata ))) ahahahaha >>> >>> >>> >> >> >
Re: ICE Exodus - porting ICE to VEX part 1
aaah, i`m already there ))) didn`t know that it is named SESI 2014-05-06 13:36 GMT+04:00 Andy Goehler : > sidefx.com and then register for the forum. > > On May 06, 2014, at 11:28, Nika Ragua wrote: > > thank you friends !!! > SESI forum? what is it? Andy, could you give a link? > And what is Blind Export? > ahahah ))) great, great, more questions appearing...a good sign > > > 2014-05-06 13:24 GMT+04:00 Andy Goehler : > >> Hi Nika, >> >> very nice video. You should post this on the SESI forum too. With my >> limited VOP experience I was able to export data with ‘Bind Export’. I’m >> currently recreating your VOP setup to look into it. >> >> Andy >> >> >> >> On May 06, 2014, at 9:09, Nika Ragua wrote: >> >> >> yo, raps !!! >> >> friends, take a look >> https://vimeo.com/94066674 >> >> How to port our precious ICE stuff into houdini vex. Questions raised - >> how to create a custom parameter in VEX, just like we do in ICE, and why >> there are different results in math. >> This is interesting i think. >> If you know the answers feel free to comment ))) >> Hakuna Matata ))) ahahahaha >> >> >> > >
Re: ICE Exodus - porting ICE to VEX part 1
sidefx.com and then register for the forum. On May 06, 2014, at 11:28, Nika Ragua wrote: > thank you friends !!! > SESI forum? what is it? Andy, could you give a link? > And what is Blind Export? > ahahah ))) great, great, more questions appearing...a good sign > > > 2014-05-06 13:24 GMT+04:00 Andy Goehler : > Hi Nika, > > very nice video. You should post this on the SESI forum too. With my limited > VOP experience I was able to export data with ‘Bind Export’. I’m currently > recreating your VOP setup to look into it. > > Andy > > > > On May 06, 2014, at 9:09, Nika Ragua wrote: > >> >> yo, raps !!! >> >> friends, take a look >> https://vimeo.com/94066674 >> >> How to port our precious ICE stuff into houdini vex. Questions raised - how >> to create a custom parameter in VEX, just like we do in ICE, and why there >> are different results in math. >> This is interesting i think. >> If you know the answers feel free to comment ))) >> Hakuna Matata ))) ahahahaha >> > >
Re: ICE Exodus - porting ICE to VEX part 1
so can any Houdini Vex experts comment on the custom variable - is it easy as declaring it as it is in Ice? On 6 May 2014 10:24, Andy Goehler wrote: > Hi Nika, > > very nice video. You should post this on the SESI forum too. With my > limited VOP experience I was able to export data with ‘Bind Export’. I’m > currently recreating your VOP setup to look into it. > > Andy > > > > On May 06, 2014, at 9:09, Nika Ragua wrote: > > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions raised - > how to create a custom parameter in VEX, just like we do in ICE, and why > there are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha > > >
Re: ICE Exodus - porting ICE to VEX part 1
thank you friends !!! SESI forum? what is it? Andy, could you give a link? And what is Blind Export? ahahah ))) great, great, more questions appearing...a good sign 2014-05-06 13:24 GMT+04:00 Andy Goehler : > Hi Nika, > > very nice video. You should post this on the SESI forum too. With my > limited VOP experience I was able to export data with ‘Bind Export’. I’m > currently recreating your VOP setup to look into it. > > Andy > > > > On May 06, 2014, at 9:09, Nika Ragua wrote: > > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions raised - > how to create a custom parameter in VEX, just like we do in ICE, and why > there are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha > > >
Re: ICE Exodus - porting ICE to VEX part 1
Hi Nika, very nice video. You should post this on the SESI forum too. With my limited VOP experience I was able to export data with ‘Bind Export’. I’m currently recreating your VOP setup to look into it. Andy On May 06, 2014, at 9:09, Nika Ragua wrote: > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions raised - how > to create a custom parameter in VEX, just like we do in ICE, and why there > are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha >
Re: ICE Exodus - porting ICE to VEX part 1
Very cool vid! Am 06.05.2014 09:09, schrieb Nika Ragua: yo, raps !!! friends, take a look https://vimeo.com/94066674 How to port our precious ICE stuff into houdini vex. Questions raised - how to create a custom parameter in VEX, just like we do in ICE, and why there are different results in math. This is interesting i think. If you know the answers feel free to comment ))) Hakuna Matata ))) ahahahaha
Re: ICE Exodus - porting ICE to VEX part 1
This is totally awesome!!! Jordi Bares jordiba...@gmail.com On 6 May 2014, at 08:09, Nika Ragua wrote: > > yo, raps !!! > > friends, take a look > https://vimeo.com/94066674 > > How to port our precious ICE stuff into houdini vex. Questions raised - how > to create a custom parameter in VEX, just like we do in ICE, and why there > are different results in math. > This is interesting i think. > If you know the answers feel free to comment ))) > Hakuna Matata ))) ahahahaha >
