Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

  • Days Won


Community Reputation

6 Neutral

About pelos

  • Rank

Personal Information

  • Name D
  • Location US
  1. i am trying to set up the hou module in pycharm, so i added to the path of python2.7libs project structure and this is what i get. import _hou ImportError: DLL load failed: The specified module could not be found. i am trying to find the _hou any one got something similar?
  2. is it possible to run Houdini in a table 32 bits? =)
  3. when I link some parameters some of the main node get crazy wire messing up the node. example Node A has some parameters link between them. example nodeA.parm("bla") and nodeA.parm("ble") is set as reference link to nodeA.parm("bla") nothing crazy one parameter looking at another one in the same node. now I want to create a new node and link all the parameters to this new node I want nodeB parameters to look at nodeA, after running the code witch is a regular stuff just setting parameters, some of the paramters in nodeA that were just a integer now have an expression poiting to another parameter =( should I create something like if its an expression use "setExpression" if is not an expression use the regular set? def linkParmsTo(source_node, target_node): """ Link the parms of the source node to those of the target node if a parameter with the same name exists. # Produced by: # Graham Thompson # captainhammy@gmail.com # www.captainhammy.com """ for parm_to_link in source_node.parms(): # Skip folder parms. if isinstance(parm_to_link.parmTemplate(), hou.FolderSetParmTemplate): continue parm_to_link_to = target_node.parm(parm_to_link.name()) # If the target parm exists if parm_to_link_to is not None: parm_to_link.set(parm_to_link_to)
  4. try Fabio Hair system will rock your world!!!! for exporting you might need to convert the hair into actual geometry and then export that as obj, fbx, alembic etc. and import that into Houdini. but importing all those curve might be heavy. what about just export the guide curves into Houdini and then use Fabio?
  5. multi solver with cloth and sop solver, where inside the sopsolver you put a peak sop to push the geometry,?
  6. thanks for sharing the file. great example on how to use vops.
  7. cof cof, setNextInput
  8. sop solver with a bound node inside will do the trick and outside the sop solver a time shift with the last frame to hold it.
  9. I don't recommend using udims for driving the fur in any application, even a map low as 1000*1000 is enough to tell the engine where and what the fur should do. don't forget you wont be seeing that texture in the frame, you only using it to drive parameters. we usually have 2 uv sets, one for the textures, udims and all that stuff, (usually one map for the head, and one for the body, depends the character might be broken into limbs) and another simple uv for driving the fur.
  10. the reason that you don't see the uvs attributes or cant pass them along, since they come from another application, I am pretty sure they come as primitives attributes, there for you might need to use attribute promote, and move the uv attribute from primitive to points. then the shader will be able to pick it up
  11. I have an otl with some geo nodes inside, and I promoted the translation (position)/ and the rotation, but I want to be able to have the button to pre transform, clean extract... and so on on the otl interface, is there a way to do that? or Houdini have a magical scrip under the hood? thanks guys.
  12. 1.7.5 - converted the shop context of the shader to vopsop, now the shader can be seen in the viewport. (use it with just a couple of hairs, since it loops all the points with attributes can be little bit expensive if you try to see the render density)
  13. thanks spencer, at the end I plugged a bind node (some one told that were faster than a parameter, since they don't evaluate, just pass the information along)
  14. how can I use the pic function in vopsop? I am watching the tutorial on how to color the particles base on the image and he use the point node, with pic, but I need to do a couple more things to the points, does any one know or might have an easy example on how to use the pic in vopsops? thanks guys.
  15. I have a vopsop node and I added a ramp parameter and a couple other toggle parameters, since this ones are automaticly promoted by Houdini, they do have lines to disable, hide, and a callback script, but doesn't let me change the option to python. so I manually edit the interface, I added a toggle and a ramp parameter directly to the UI. this params have more options than the one that Houdini promoted. and I am using this ones as temp parms. the temp parms have a script to modify the normal parameter and the other things I wanted to do from the beginning. example: ramp1 ramp manually done call back script, copy paste this ramp into the ramp 2 + print "hello" ramp 2 ramp promoted by Houdini this one is hidden and use in the vop sop. is there a way to be ale to tell the promoted parameters from Houdini to use proper callbacks?