I also had issues figuring that out at first. There doesn't seem to be any hard rule nor consitency and that's simply because not every node operates on the same kind of data (nor provide support for the same feature set). One way to know is to check if the $PT variable is available when typing an HScript expression in a parameter. Which is not the case for the Peak SOP, at least for me in Houdini 13.
But you know what? You can have the same result with a custom operator made in less than 2 minutes. Create a VOP SOP, or an Attribute Wrangle SOP, and for each point you only have to add the normal to the position, with the coefficient value from your painted attribute. Example in VEX: v@P += normalize(v@N) * f@my_painted_attribute; On 2 March 2017 at 20:38, <[email protected]> wrote: > > Hi, > > I’ve just started learning Houdini. I’m finding it hard to find knowledge > on how to have an attribute, that I’ve created then painted, to drive ,say > the per point value of a peak deformer node > > I have tried the point expression, but I get a load of errors. > > does anyone know please? > > thanks > Paul ‘pooby’ Smith > > ------ > Softimage Mailing List. > To unsubscribe, send a mail to [email protected] > with "unsubscribe" in the subject, and reply to confirm. > -- Christopher Crouzet *https://christophercrouzet.com* <https://christophercrouzet.com>
------ Softimage Mailing List. To unsubscribe, send a mail to [email protected] with "unsubscribe" in the subject, and reply to confirm.
