magneto Posted January 16, 2012 Share Posted January 16, 2012 (edited) I am trying to make a VOP SOP using the graph editor but I am not sure if I am able to access these attributes correctly. I added a Get Attribute operator and set Signature to "Float Attribute", Attribute to "CEX", Attribute Class to "Detail". Am I doing it wrong or am I not allowed to access these variables? Thanks Edited January 16, 2012 by magneto Quote Link to comment Share on other sites More sharing options...
Macha Posted January 16, 2012 Share Posted January 16, 2012 I am not sure what you are trying exactly, but with parameter you can read detail attributes, unless they are N,V, etc, in which case you have to rename them first. Quote Link to comment Share on other sites More sharing options...
3dbeing Posted January 16, 2012 Share Posted January 16, 2012 I just use the bounding box vop... Quote Link to comment Share on other sites More sharing options...
hopbin9 Posted January 16, 2012 Share Posted January 16, 2012 (edited) You're up late for a Sunday. Aren't CEX and SIZEX expression variables, and not really attributes? Edited January 16, 2012 by hopbin9 Quote Link to comment Share on other sites More sharing options...
magneto Posted January 16, 2012 Author Share Posted January 16, 2012 (edited) Thanks guys. @Macha, what do you mean by N, V? @3dbeing, that might be a good solution. @hopbin, yes always trying to squeeze in some Houdini time I use this page for reference where CEX and SIZEX exists: http://www.sidefx.com/docs/houdini11.0/nodes/sop/standardvariables So they are just variables not attributes? Thanks. Edited January 16, 2012 by magneto Quote Link to comment Share on other sites More sharing options...
sam.h Posted January 16, 2012 Share Posted January 16, 2012 So they are just variables not attributes? They are local variables. Use the Parameter node, set it to invisible and the value to $SOMETHING ... or you can use a constant node with an expression in the value. Quote Link to comment Share on other sites More sharing options...
magneto Posted January 16, 2012 Author Share Posted January 16, 2012 Thanks, I just tried the Parameter OP where I set the the values to $CEX, $CEY, $CEZ, but it says it cannot evaluate undefined variable in the Parameter OP. Would the Constant OP be different in this case? Quote Link to comment Share on other sites More sharing options...
hopbin9 Posted January 16, 2012 Share Posted January 16, 2012 Make a parameter and ensure it's visible, also a Vector type. Then step up one level and you should see it as a new parameter for the VOP SOP. Now set an expression using $CEX in X, $CEY in Y and $CEZ in Z. Quote Link to comment Share on other sites More sharing options...
hopbin9 Posted January 16, 2012 Share Posted January 16, 2012 oh wait, that might not work, cause $CEX is for primitives... I think we both need get some sleep. Quote Link to comment Share on other sites More sharing options...
3dbeing Posted January 16, 2012 Share Posted January 16, 2012 Make a parameter and ensure it's visible, also a Vector type. Then step up one level and you should see it as a new parameter for the VOP SOP. Now set an expression using $CEX in X, $CEY in Y and $CEZ in Z. I can't get that to work either, this is the first time i've heard of local variables being availible in vop fields. So i'd love to see a working version.... Quote Link to comment Share on other sites More sharing options...
magneto Posted January 16, 2012 Author Share Posted January 16, 2012 (edited) Thanks hopbin, that should do it. But is there also a way to access these variables inside VOP SOP? Because ideally I would like them to be inside the VOP SOP, and always set to those values. I imagine I could also do this in the parameter options dialog and make it invisible. For this case, I will use the bbox VOP but I still want to know in case I want to access some other attributes later on. EDIT: lol guys, I am glad you haven't encountered this before, and I agree on the sleep Edited January 16, 2012 by magneto Quote Link to comment Share on other sites More sharing options...
hopbin9 Posted January 16, 2012 Share Posted January 16, 2012 I think the trick here is that $CEX/$SIZEX are local variables for SOP nodes that define them. They are not global variables that are available for use in any SOP node. They shouldn't be confused with attributes. Quote Link to comment Share on other sites More sharing options...
sam.h Posted January 16, 2012 Share Posted January 16, 2012 haha oops, I was thnking of using things like $PI... why not just use an expression? like centroid(opinputpath(".",0),D_X) Quote Link to comment Share on other sites More sharing options...
magneto Posted January 16, 2012 Author Share Posted January 16, 2012 @hopbin, gotcha that makes sense. @sam, that is a good solution too. Thanks guys, appreciate the replies Quote Link to comment Share on other sites More sharing options...
ikarus Posted January 16, 2012 Share Posted January 16, 2012 (edited) edit: already answered by sam.h Edited January 16, 2012 by ikarus 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.