think of it as a set data node
Am 06.05.2014 um 15:08 schrieb Nika Ragua <nikaragu...@gmail.com>: > And what is Blind Export again? > > > 2014-05-06 17:07 GMT+04:00 Nika Ragua <nikaragu...@gmail.com>: > 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 <nikaragu...@gmail.com>: > > 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 <nikaragu...@gmail.com>: > > > 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 <nikaragu...@gmail.com>: > > 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 <nikaragu...@gmail.com> 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 )))) > > > > > > > >
