Jump to content

Daverod

Members
  • Posts

    5
  • Joined

  • Last visited

Personal Information

  • Name
    Dav Rod
  • Location
    Europe
  • Interests
    learning and sharing

Daverod's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I could do it as you said with: In my case I used: for i in range(1,20): ... new_folder.addParmTemplate(hou.StringParmTemplate("parm"+str(i), "Label"+str(i), 1, default_value=([""]), naming_scheme=hou.parmNamingScheme.Base1, string_type=hou.stringParmType.NodeReference, menu_items=([]), menu_labels=([]), icon_names=([]), item_generator_script="", item_generator_script_language=hou.scriptLanguage.Python, menu_type=hou.menuType.Normal)) ... But, do we really have to use that full line of code? Is there a shorter reference to call an "operator path"? Thanks
  2. I am now in the same situation. In my grid some prims are going from black to red. I want them to emit 100 particles just when they turn red the first time and never again. Imagine: Two prims turned red and they emitted 100 particles each. I dont want them to keep on emitting despite that some other prims will be turning also red. Did I explained? Thanks in advance.
  3. Could you include an attribute inside that expression? $F == @startFrame for example?
  4. I can use perfectly my keyboard in any software and inside windows. When I am inside Houdini can not type [ or {. But I can type ] and }. Is pretty anoying going out of Houdini to copy one of that characters. Any idea about what is going on? Thanks
  5. I would appreciate if somebody can give some example, information or h file about this "Look at" node. What are the common applications for it? Thanks in advance.
×
×
  • Create New...