Import Attribute Vop

[henderthing]

What, exactly, does this parameter do when there is only one input?

When I use it to get the position of the neighbor of every nth point, and have a single input--the result changes dramatically when i use different values for OP input index.

Shouldn't it just fail? What's going on here?

(to clarify--my understanding was, in the case of a SOP VOPnet where multiple SOPS are connected to the VOPnet SOP's inputs, the OP input index was used to select which connected SOP is evaluated--and that input zero is appropriate for 1 input)

Thanks

-m

[edward]

So what's wrong with your understanding? That's how I understand it as well.

[henderthing]

The problem is that I have only one input, but when OP input index is set to 0, nothing happens (appears to fail), as I go to 1, 2, 3 etc...the vopnet is doing something--something different for each index, for that matter.

Is OP input index sensitive to primitives or groups in some way that I don't understand? The input SOP in question has a dozen primitives, and four point groups and the VOPnet cycles to doing nothing on every 4th input index beginning with 0...

I'm confused.

-m

So what's wrong with your understanding? That's how I understand it as well.

21933[/snapback]

[edward]

But if you have only 1 input into your SOP, then only an input index of 0 makes sense to be used in the Import Attribute VOP, right? Behaviour of using non-existent inputs would be undefined.

[henderthing]

well...yes. which is why i had it that way, and only began

messing with it as the importAttrib node was failing to

do anything with index at 0.

I think it has something to do with the way i'm trying to

use the neighbor vop beforehand. I'm only operating

(if block) on points that pass the test of $PT%5 ==2

test, then, inside the if block, I want to get info from

a neighboring point. It sure seems like everythign is

OK---but the importAttrib node is failing. Miserably.

If i connect its adata output directly to P output,

nothing happens. Remembering that I'm working

on the 3rd point of every 5, that point should move

to it's neighbor's position.

AH!--more tests show that there is a problem with

my neighbor vop. It doesn't like negative numbers.

It would appear that I've misused it. I wanted to go

back 2 points from the current point. Turns out it's

better--much--to just subtract 2 from point number

on the way into the importAttrib vop. I've got a lot

to get used to...

I'm still curious what the heck the opindex thingy was

doing there...

Thanks for making me look harder elsewhere!

-m

But if you have only 1 input into your SOP, then only an input index of 0 makes sense to be used in the Import Attribute VOP, right? Behaviour of using non-existent inputs would be undefined.

21935[/snapback]