MENOZ Posted June 4, 2011 Share Posted June 4, 2011 HI! I created an attribute in VOP POP called treshold, and set the variable mapping to TRESHOLD. After the pop network I put a kill pop, and set the rule $TRESHOLD>3 but local variable mapping seems not to work. Instead if I append an attribute pop and set value : $TRESHOLD this time $TRESHOLD becomes green and all works. Why kill pop doesn't recognize my local variable mapping as attribute pop does? Quote Link to comment Share on other sites More sharing options...
sam.h Posted June 4, 2011 Share Posted June 4, 2011 The attribute node is special and will map the local variable if it isn't mapped already. So, the mapping doesn't need to exist for $THRESHOLD to work in the attribute node ... Quote Link to comment Share on other sites More sharing options...
MENOZ Posted June 5, 2011 Author Share Posted June 5, 2011 The attribute node is special and will map the local variable if it isn't mapped already. So, the mapping doesn't need to exist for $THRESHOLD to work in the attribute node ... From what I understand, attribute pop automatically maps incoming attributes, and for this reason I can write $TRESHOLD and see it green. My question is: if i create an attribute in VOP, and explicitly set the variable mapping, can I use this mapping outside the VOP network? for example in the kill pop, writing $TRESHOLD? or I have to put an attribute pop between the vop and the kill note to create (recreate) the variable mapping for my attributes? Quote Link to comment Share on other sites More sharing options...
sam.h Posted June 5, 2011 Share Posted June 5, 2011 It doesn't seem like vop pops map the variable, generally I just use an attribute node to make the binding like you have said Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.