Jump to content

Search the Community

Showing results for tags 'vex vop define node'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Lounge/General chat
    • Education
    • Jobs
    • Marketplace
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering + Solaris!
    • Compositing
    • Games
    • Tools (HDA's etc.)
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Name


Location


Interests

Found 1 result

  1. 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
×
×
  • Create New...