Jump to content

michael

Administrators
  • Content count

    4,275
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by michael

  1. Brick/Stone Wall - Broken Horizontals here a fun(?) little problem... given the following reference http://donnamarie113.deviantart.com/art/BRICK-WALL-298282838 http://www.desktopwallpapers4.me/abstract/brick-wall-and-wood-floor-14568/ http://fc03.deviantart.net/fs70/f/2013/054/e/4/brick_wall_by_kayosa_stock-d5vy7u3.png how would one go about building a wall like this - a brick/stone wall is VERY easy...but a wall with what I'm calling 'broken horizontals' is much more difficult... if/when I have some time I'll see what I can do and post my results...if anyone has some good suggestions
  2. Houdini 17 Wishlist

    when a video is private we can give the password out to Alpha/Beta/Whatever users, then just switch it to 'Public' when it's ready and we don't have to update any links etc. this is why we don't like things going public before they are ready :|
  3. Houdini 17 Wishlist

    @koanix5 we have been careful, but this was obviously an error - I'd have thought there would be enough general good will to make people let us know about mistakes like this rather than post something that was clearly not ready for the public.
  4. Houdini 17 Wishlist

    I know everyone is excited to see the next version of Houdini - but posting CONFIDENTIAL material will not be tolerated,
  5. expressions and rigging

    typically you'd use bones for deformations but expressions at the SOP level are good for transforming geometry
  6. Common Sense

    I think this thread has run out of steam... lets all move on.
  7. When is a network too complex?

    I've often looked back on the network(s) I'm using and thought "shit - this is crazy" and tried to go back and simplify - it's a good idea generally but it's a mistake to look at Houdini's node network(s) and think there are 'too many nodes' every DDC app worth using builds the same insanely complex networks - the difference is Houdini shows them to you...
  8. Stack of fishes. FEM or Grain?

    you can also try the good old wire object make the wire 'width' thick enough to represent your fish, then just sim the wires, capture/deform the fish with the wires: used this here:
  9. Camera missing 'LookAt'

    yep - Path parameter has been hidden also - there is a Follow Path tool on the Constraints shelf. I think there might be a bug with the focus handle but you should be able to put an expression in that parameter to measure the distance between the camera and the object.
  10. Exporting Houdini Rig to Maya

    nope. you'll not find this is any DCC app the best you can do is export from Maya as FBX and use that as I guide to rebuild the rig.
  11. Camera missing 'LookAt'

    the LookAt parameter has been deprecated in favor of the new CHOP based constraints. (it IS still there if you Edit Parameter Interface and show hidden - but use the constrains instead)
  12. Houdini 17 Wishlist

    this is a nice RFE - please submit it
  13. Houdini 17 Wishlist

    please submit these as bugs/RFEs
  14. Rigging the clavicle to follow arm?

    here is one way clavicle_follows_wrist.0.hip
  15. RGB to Kelvin

    this looks pretty good: http://www.tannerhelland.com/4435/convert-temperature-rgb-algorithm-code/
  16. Wire deformer capture weights

    it should be easier than this (I think there is a bug in the capture layer paint) but here is a file that will work simple_wire_paint.2.hip
  17. scripting/programming come into play in a number of different areas and to differing degrees. the most basic kind of scripting would be something like a channel expression - in the TX parameter of an object > sin($F) or a reference to another channel "ch("/obj/someOtherObject/tx")" these kinds of scripts can be simple or very complex and written in hscript or python VEX ( http://www.sidefx.com/docs/houdini/vex/_index ) would be used to write 'custom nodes', a wrangle is just a container for vex script that does stuff, which makes the wrangle act like a custom node. vex is super powerful and can do lots of things that would be hard or impossible with Houdini's default nodes alone. Houdini has HOM (Houdini Object Model) and this exposes most of Houdini in a python interface - so you can write custom nodes, tools with UIs etc and just generally interact with Houdini using python. so it really depends on what you're doing, what your end goal is at any particular time. having a good foundation in scripting/programming means you're better able to take advantage of these things to get work done.
  18. without seeing you file it's just a guess but - it's probably a collision geo issue. turn on Show Guide Geometry to see the blue collision geometry
  19. Best way to learn VEX

    You could start with the documentation then try to tutorials at SideFX - https://www.sidefx.com/tutorials/vexvops-01-intro-to-vex-and-vops/ https://www.sidefx.com/tutorials/vex-wrangle-workshop/ https://www.sidefx.com/tutorials/houdini-illume-webinar-vex/ Matt Estela has some great info on Tokeru: http://www.tokeru.com/cgwiki/?title=HoudiniVex
  20. houdini 16 group node

    the group node has been split into individual nodes, older tutorials will not reflect this. what kind of group are you trying to make, or what kind of operation are you trying to do? put down some of the other group nodes and have a look at what they do.
  21. you'll want all your textures to have the same naming pattern.
  22. ramp03diffuse.Base.1011 (what is the file format?...lets say .exr) ramp03diffuse.Base.1011.exr filename%(UDIM)d.ext so... ramp03diffuse.Base.%(UDIM)d.exr should work...
  23. Constraints in Houdini ?

    check out the Constraints Tab on the shelf.
  24. Houdini 17 Wishlist

    there were many people telling us that the 'one node to rule them all' was often confusing and they had trouble figuring out where/what was going on, and there was interest here to split them up to make fixes/features easier to do in simpler code. personally I find copy/paste faster, easier and far less error prone than dragging nodes around. and there would have to be lots of logic for what you want to do after the drop - copy of nodes, move nodes, make reference etc RFE it if you think it's worth it
  25. Houdini 17 Wishlist

    do you mean drag a node from one network to another (of the same type)? copy/paste works, and each network type has it's own clipboard.
×