Pancho Posted November 14, 2015 Share Posted November 14, 2015 I just hoped that this otl would save my day, but it just causes additional problems. http://www.creatogether.com/hou-curveoffset/ The rotate_back node at the end displays the errors which are produced in the temp_rotate node at the beginning. So I replaced $CEX,$CEY... with $GCX,.... Error messages disappear. But the expression 90*min($XMAX-$XMIN,1) still causes problems. WHY! Is $XMAX also something from the past and replaced in the meantime by another syntax? If there would be another way to inset a polygon/curve without running into interseting errors I would also be open for another solution. Cheers Tom Quote Link to comment Share on other sites More sharing options...
loopyllama Posted November 14, 2015 Share Posted November 14, 2015 $XMAX and $XMIN work. Put down a box, then a transform, then put $XMIN in tx and the box moves. Look at the value $XMIN produces in the field...0...it cannot be evaluated in the field. Try calculating that expression in an attribute, then have that "temp_rotate" node grab the value from the attribute rather than the field that it cannot evaluate. Quote Link to comment Share on other sites More sharing options...
Pancho Posted November 14, 2015 Author Share Posted November 14, 2015 Thanks for the tip! Since I'm a beginner: How would I do that pratically? Attribute Create and put the formula into the "Value" field? Would I position this before the first node of the otl? Quote Link to comment Share on other sites More sharing options...
Pancho Posted November 14, 2015 Author Share Posted November 14, 2015 (edited) O.k., I used an "Attribute Create", value is the formula and class is set either to detail or primitve, name is bbxa and bbya. When I try to get the value in the transform node with $BBXA and $BBYA or bbxa there error still remains. I used to be able to deal with variables in SI pretty easily, but in H everything seems to be a bit more complicated. So, how does it work? Cheers Tom P.S.: In the geometry spreadsheet the values appear correctly, though with class set to primitive they disappear at the fuse_close node. Edited November 14, 2015 by Pancho Quote Link to comment Share on other sites More sharing options...
loopyllama Posted November 14, 2015 Share Posted November 14, 2015 just stuff the attribute into a detail (means it only does it once). you access the attribute by the "detail" expression. If you had a point attribute, you access by the "point" expression, etc. Sometimes certain nodes have special variables only accessible to that node, called local variables. The transform has $XMIN, $XMAX, among others. Check the help for that node and scroll to the bottom to see available local variables. curveOffset_example_fixed.hipnc Quote Link to comment Share on other sites More sharing options...
Pancho Posted November 14, 2015 Author Share Posted November 14, 2015 Thanks so much! BTW, do you know of a better way to do this kind of inset? Still run into a lot of problems. Cheers Tom 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.