Jump to content


  • Content count

  • Donations

    10.00 CAD 
  • Joined

  • Last visited

  • Days Won


acey195 last won the day on October 17

acey195 had the most liked content!

Community Reputation

144 Excellent

1 Follower

About acey195

  • Rank
    Houdini Master
  • Birthday 01/10/1991

Contact Methods

  • Website URL

Personal Information

  • Name
  • Location

Recent Profile Visitors

6,980 profile views
  1. I would do the following: Create a convex hull Measure the distance between the mesh and the hull Constrain the smoothing, based on this distance. Possibly you want to do this in an iterative loop, smoothing in smaller increments, re-evaluating the constraints every iteration.
  2. Also, for object aligned boxes, I would generally loop over the objects, just use the Box SOP and then in VEX, do a intersect along the Normal (z), Up (y) vector and crossproduct(N, up) for the x axis, to get the scales.
  3. In this case you just type the name of the HDA name (not label) where it says: 'geo' I believe
  4. Also note that the "0" as the argument, refers to the input number, you can also use 1,2,3 to access the other input nodes (or even -1, -2, etc if you use spare inputs)
  5. How to selects a point ID using VEX?

    Because of how Houdini deals with ints, you can also do that (if your "whatever" fits on one line of code)
  6. trying to understand how arrays work

    Hey, didn't have time to check the file, but I have a hunch you used the setdetailattrib(0, "foo", yourArray); and then tried to read from it. This you cannot do inside the same wrangle. all the functions that write attributes, are only applied in the output of the node, not in the local data. so if you want to keep using it, use "yourArray" instead of "detail(0, "foo")" this restriction is not there for bound attribs like: "@foo" to your other question, of course. You can for example use the group parameter at the top of the node, to only process a subset (or a single) of your primitives
  7. For-Each Numbers Node Houdini 17

    Everything in the old foreach subnets can be done with the new ones, in slightly different ways (which will make more sense/are more flexible in the long run, than the old one) if you want an introduction to the new foreach logic, you can always watch Jeff's tutorial:
  8. trying to understand how arrays work

    you can use setdetailattrib() http://www.sidefx.com/docs/houdini16.0/vex/functions/setdetailattrib something like: int yourArray[]; /* stuff to build your array */ string selection = sprintf("selectionOfPrim%d", @primnum); setdetailattrib(0, selection, yourArray); note that, if this is what you actually want to do, its better just to save it as a prim attribute of course. if you just want one attribute, then run the wrangle in detail mode and build rebuild the logic to work with that. (you'll need to change the way you read and write your data)
  9. Houdini 18 Wishlist

    This works for Subnets, but unfortunately not at the top level of your geometry nodes. So for rendering your geometry, and for usage in Houdini Engine, you still have to set the render flag by hand, at the top level.
  10. Force python sop NOT to cook

    Maybe you could try something with the "stash" SOP or scripts related to its functionality? It can save geometry data to a parameter, if you load your geometry from there, downstream, I would guess it will not "dirty the node" and request a cook automatically.
  11. make window in the wall

    Hole is good, if you have only a few objects to cut out of your main object. when you start to have a lot and the order of the cuts is going to affect the result, because of the bridging edges, or if you start to have recursive holes (holes in holes) I would generally still advise the usage of the new Booleans. The booleans also have a mode specifically made for flat objects, and like you already found out, you would not need to clean the tiny sliver of a mesh below the doorframe in your case. also, as a second alternative, you could also use the "Trim" SOP if you work with NURBS surfaces.
  12. Is the SORT tool somehow broken?

    Apart from the join sop, you could also use the polyPath sop, which is more flexible in my opinion. The join sop only works if all the vertex numbers are in the correct order (and only merging connecting pieces requires extra nodes) the polyPath, just requires pre-fusing the points.
  13. Houdini Terrain Pipeline Vol 2

    Hey All! The first part of this tutorial has been available for almost a year now, but because of the sad news that hit CMI, I was unable to upload the 2nd "half" there. So instead I just made it available on Youtube for everyone, to make up for that I suppose. I'm considering putting the first part on there as well, if enough people want that. In this tutorial covers the following, using Houdini * Generating water meshes * Updating the terrain based on the water * Generate walking paths on the terrain * Create some basic instances * Build a flexible system using external files to place these instances. Built on Houdini 16.5, but should work on 16 too, or all the way back to H14 if you skip the heightfield part. Recommended specs: at least 16GB of RAM, reduce the terrain size if you have less. Disclaimer: Work files are as is, and do not contain the cached geometry to save on space, this may explain node errors on the various "File Cache" nodes. It does however also contain the work done in the first half of the tutorial, albeit mostly undocumented: https://tinyurl.com/y89egjvq Hopefully its of some use! Twan
  14. Just wanted to say thanks......

    Welcome Dennis! From your other post, I was curious where you were studying. Igad(Breda), HKU or self taught ? Also Dutch you see , not very new to Houdini anymore I suppose, but still learning all the same. Enjoy your stay!
  15. Learning Curve of Popular 3D Software

    Its Hilarious, its also a classic I believe I first saw it when I was still in school, more than 4 years ago ^^