t;>> now. Also really need to say, while I'm not programmer, unfortunately or
>>>>> not I have to communicate with them every day, even in private life, so
>>>>> maybe I become a bit resistant. I think we all know how is going with this
>>>>> kind o
m>"
<softimage@listproc.autodesk.com
<mailto:softimage@listproc.autodesk.com>>
*Sent:* Wednesday, March 2, 2016 1:29 PM
*Subject:* OT Houdini build Array VOP question
(and a bit of rant
<christopher.crou...@gmail.com
> <mailto:christopher.crou...@gmail.com>>
> To: Softimage Mailing List <softimage@listproc.autodesk.com
> <mailto:softimage@listproc.autodesk.com>>
> Sent: Thursday, March 3, 2016 4:40 AM
> Subject: Re: OT Houdini build Array V
n private life, so
>>>> maybe I become a bit resistant. I think we all know how is going with this
>>>> kind of people - one has this or that opinion, another has completely
>>>> opposite, all long stories full of smart words. No need to waste your time
>>>
's say in short :) Of course I've read everything you said here.
>>> thanks again...
>>>
>>> ----------
>>> *From:* Christopher Crouzet <christopher.crou...@gmail.com>
>>> *To:* Softimage Mailing List <softimage@listproc
;> *From:* Christopher Crouzet <christopher.crou...@gmail.com>
>> *To:* Softimage Mailing List <softimage@listproc.autodesk.com>
>> *Sent:* Thursday, March 3, 2016 4:40 AM
>> *Subject:* Re: OT Houdini build Array VOP question (and a bit of rant)
>>
>> You can think
;
> --
> *From:* Christopher Crouzet <christopher.crou...@gmail.com>
> *To:* Softimage Mailing List <softimage@listproc.autodesk.com>
> *Sent:* Thursday, March 3, 2016 4:40 AM
> *Subject:* Re: OT Houdini build Array VOP question (and a bit of
ject: Re: OT Houdini build Array VOP question (and a bit of rant)
You can think of each geometry attribute as an array which length equals the
number of points (if dealing with points). VOPs simply iterate over these
points and process the graph for each of them. Since each attribute is an
array,
do some pretty interesting networks :) for Kristinka
>> Hair for H - while everything worked at the end of day, anyway.
>>
>> If you're around arrays and nodes, Fabric is waiting for You
>>
>>
>> --------------
>> *From:* Olivier Jeannel <facialdel...@gmail.com>
>
and nodes, Fabric is waiting for You
>
>
> --
> *From:* Olivier Jeannel <facialdel...@gmail.com>
> *To:* "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com>
> *Sent:* Wednesday, March 2, 2016 1:29 PM
> *Subject:* OT Houdini build
com>
To: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com>
Sent: Wednesday, March 2, 2016 1:29 PM
Subject: OT Houdini build Array VOP question (and a bit of rant)
Hello serious list :)
I'm a bit confused with houdini vop array.While I managed to do it in vex,
No, no you're not mis-understanding. Probably me doing it wrong
I will try that too, thank you for making that clear :)
All that "thinking" is because I had this project
https://vimeo.com/155960784
It's a bit complicate to describe in words.
To achieve the rotation per primitive I had to define
Maybe I'm misunderstanding but if you already know which point you want an
attribute value of, then why would you want to store the values for every
point in an array? That'd be a lot of processing for nothing. No need to
iterate with a for loop neither. In VOP there's the `Get Attribute VOP`
node
Thank you so much for your time, explanations and examples Christopher.
I'm taking those picture and will reproduce them :)
Well, I wanted an array because I need to see if I could be able to
retrieve the second element of an array (Ptnum =1 ) using Get Element (I
guess).
On Wed, Mar 2, 2016
Basically, arrays are a convenient structure to pass data around (and to
potentially make your code more readable, which won't apply to VOP). If all
you need is to perform a computation in place and directly use the result
in your VOP graph, then iterating over your points is all it takes—no array
Yes I saw it, sorry, I thought there was another additionnal method with
For Loop :
"Instead, you should be able to just loop over each point with a `For Loop
VOP` and do your computation directly in there"
Have I misunderstood ? You're doing a for-loop without building an array in
the end.
On
I did attach a screenshot in my previous email, are you not seeing
anything? Or are you asking for the H13 for loop?
On 2 March 2016 at 21:20, Olivier Jeannel wrote:
> Ah THANK YOU !
>
> I'm "aware" of the PCOpen+PcFilter to gather infos based on distance.
> I also
It seems like they've extended the support for arrays in H14, which makes
it now possible to use them as geometry attributes. In the previous
versions I guess that there was no real point (but convenience) in creating
arrays in VOP since you couldn't pass them downstream with the geometry
data.
Ah THANK YOU !
I'm "aware" of the PCOpen+PcFilter to gather infos based on distance.
I also use the PrimUV a bit and XYZ+PrimUV for location things.
I'd be curious on the For Loop Vop, if you have any pictures :/ Sorry to
ask.
It's a shame there's no tutorial or phylosophycal explanations
Hello serious list :)
I'm a bit confused with houdini vop array.
While I managed to do it in vex, I would like to make a build array (like
build array from set) of the pointposition (P) in VOP.
I understand you need to for-loop on each Ptnum and probably append the P
values and this will buid an
20 matches
Mail list logo