JamesSathre Posted July 26, 2013 Share Posted July 26, 2013 Hello, I'm having trouble accessing point attributes as hscript expressions in the mountain node. Do I use a different function for vex type nodes? // -- function call that works as an add attribute point("../pointjitter1", 1, "circle_grad", 0) thanks, James Quote Link to comment Share on other sites More sharing options...
magneto Posted July 26, 2013 Share Posted July 26, 2013 Where are you using that? If you want to override the parameters of a Mountain SOP per point, you need to create a point attribute with the same name as the parameter. "height" for Height for example. 1 Quote Link to comment Share on other sites More sharing options...
JamesSathre Posted July 27, 2013 Author Share Posted July 27, 2013 Ok, I understand now. You have to setup the nodes parameters before you get to that node. I guess this is the workaround, thanks for the info. Quote Link to comment Share on other sites More sharing options...
breadbox Posted June 21, 2017 Share Posted June 21, 2017 (edited) Picking back up on this topic, now that the mountain has been changed in H16 it seems that some variables do not map with point attributes? I am trying to use gflow as a point attr to influence the gradient warp. File attached. PointVariables_Mountain.hipnc Edited June 21, 2017 by breadbox Quote Link to comment Share on other sites More sharing options...
breadbox Posted June 21, 2017 Share Posted June 21, 2017 OK found the issue the variable for some reason was mapping as "parm_gflow" instead of just "gflow". Had to dive into the VOP Net and peck around until I found the variable mapping was changed. 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.