ajz Posted March 3, 2015 Share Posted March 3, 2015 (edited) Hello Guys.There's this certain thing I noticed today which puzzles me. Assumption: We have a poly mesh sphere of rad(x,y,z)=0.5 and an xform node piped to it. Y-axis pivot (py) of the transform node equals .If I set py=-$SIZEY/2, it places the pivot at the bottom of the sphere, which is correct. But... If I peek at a current value of py (in Parameters pane), it still shows , while it should be equal to -0.5. If I pipe a Python SOP to check the value of SIZEY local variable, it shows me 1.0. So why inside the py parameter? hou.node('/obj/sphere_object1/xform1').parm('py').eval() also returns 0.0 instead of -0.5. So the parameter really stores .Similarly with xform's ty. If I type $SIZE/2, which levels the bottom of the sphere with the origin on Y-axis, and if I peek at the parameter's value of ty, I get 0.0. Python's eval()also shows that this parameter stores 0.0. But why? Why it's not equal to 0.5?Could someone please explain this to me? Why does this happen? Edited March 4, 2015 by ajz Quote Link to comment Share on other sites More sharing options...
jkunz07 Posted March 3, 2015 Share Posted March 3, 2015 Sounds like it's related to this: http://forums.odforce.net/topic/17482-cex-cey-cez-no-longer-working-properly/ and http://forums.odforce.net/topic/16159-what-is-the-reasoning-behind-the-variable-behavior/ 1 Quote Link to comment Share on other sites More sharing options...
ajz Posted March 4, 2015 Author Share Posted March 4, 2015 (edited) Interesting lecture. It pretty much explains everything. Thank you jkunz07. I thought I was going insane. Edited March 4, 2015 by ajz 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.