Search the Community
Showing results for tags 'vex vop define node'.
Found 1 result
-
Hi there, I've created a material that contains an inlineCode node with some vex inside. I'd like to be able to create a generic version of this node that can be re used but there are a few problems. when i add inputs to the node they inherit the names of their input, I'd like them to be generic, i.e. "input1" rather than "product" if i connect the output of a multiply node or "s" if i connect a texture coordinate. Also as the node just creates code any variables contained within are placed in the resulting code verbatim and if i have many copies of the inlineCode node with the same contents then I get clashing variable names. Has anyone done this? or does anybody know where to look for docs on createing new vop node templates that are more flexible. Cheers jon
