Jump to content

Fenolis

Members
  • Content count

    44
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Everything posted by Fenolis

  1. I created a Curve SOP and used float parameters on a Null to control the curve's points. Strangely, when the float values are (rounded to) integers, the curve's points are located incorrectly. Attached short video demonstrating the bug. 2018-05-05 15-09-13.mp4
  2. [BUG] with Curve SOP

    Okay it's probably not the bug I was expecting. I didn't notice that Pasting Relative References into the curve's coords field was pasting them as strings, and I guess converting a float value to a string has some...weird consequences like adding them together in a string field becomes a concatenation operation. Changing the pasted "chs()" into "ch()" resulted in the behaviour I was expecting, and the correct one. My bad!
  3. Ah. I was replying to a comment >2 months old regarding the point sorting order. I thought perhaps sorting by uvs would cause the smallest number to always be in the same position. Edit: Cool model, by the way. Missing proper normals on the windows but I like the style!
  4. Cant Find "Missing Point"?!

    In order to ensure a smooth seam, the curve needs as many points as its Order to interpolate. By merging the two end points into one, it avoids a hard "Corner" vertex.
  5. How to make a skinned sweep that can be subdivided ?

    What is the difference between using the Skin SOP after the Sweep, as compared to using the "Skin Output" option on the Sweep SOP? I imagine you could do a PolyFill after skinning, then finding a way to subdivide that. Maybe with a PolyExtrude inset?
  6. Entagma Packing the torus tutorial

    Attaching your scene is usually helpful, if you're allowed to do so. Most of the issues regarding use of the Cookie/Boolean(Updated version) node is related to the inputs you provide. If you provide contiguous surfaces (no holes) it usually works fine. Here is a thread you may find helpful: Boolean
  7. "Tent": Connect 1 pt to a bunch of others pts

    Turn your process into a HDA at the SOP level, and be the change you want to see!
  8. Modelling Parts for a Pillar

    I had fun with the math shape. astroid.hipnc
  9. Wall generation from wireframes

    looks like you did an inset after... PolyExpand3D!?
  10. Technique for modeling a wheel

    I would like to know if you have any ideas on how to start modeling a shape like this procedurally in Houdini: I've already managed to build the tyre with help from the Creep SOP, but if you have any techniques you'd like to share, I'd be happy to learn those as well!
  11. Technique for modeling a wheel

    That was very helpful! Thank you! Here's a design using Polybridge.
  12. Technique for modeling a wheel

    Thank you for the link! I've actually seen that one before a few times, and while I feel that there are some good steps there I have come up with an easier process. You used bending to achieve the curvature along both axes, while I drew a curve profile for my tyre base, revolved it to create the tyre, converted it to a NURBS surface which I then swept my tread pattern along using the Creep SOP. The Creep SOP also allows for control over surface coverage quite easily, as well as making sure it is impossible to create any overlaps. I'm sure the way you generated the tread pattern is similar to mine, and will work in my process as well.
  13. Capsule

    You could always hack the height with a "n/bbox(opinputpath(".",0),D_YSIZE)" expression in the scaleY value of a transform node, where "n" is the height you want.
  14. Is the aimed point on the same plane as the points your normals are coming from?
  15. Greeble plugin for Houdini

    Hey this looks good! Do you have any way to resolve self-intersections?
  16. Procedural Road Creation

    Replace all $SIZEX $SIZEY $SIZEZ expressions with the "bbox()" expression. e.g. bbox(opinputpath(".",0),D_XSIZE) bbox(opinputpath(".",0),D_YSIZE) bbox(opinputpath(".",0),D_ZSIZE) Feel free to replace the "opinputpath" section with the path of the node you want to read the parameters from. It's definitely more tedious, but it works.
  17. Grape Modeling

    Hi, I have generated a bunch of grapes using Houdini's L-system SOP. I instanced the grape geometry using the leaf J input for the L-system, and the grapes sometimes intersect each other. As the model has to be used in a dynamic simulation, these intersections will cause issues in future. Is there any way to fix/prevent these geometry intersections? Attached .hip for reference: grapes_single.hip
  18. Hi guys, I am trying to make a bowl filled with water. However, the fluids keep on leaking out from the collision geometry even though the collision geometry looks fine. Could anyone take a look at my hip and see what is wrong? untitled.hip
  19. Flip Fluids leaking through geometry

    That...blew my mind. Excellent explanation of the FLIP sim and a cool solution to boot. Thank you very much!
  20. Copy stamp a string value?

    Hi.. 3 years later and I've come across a similar question. Good examples and effective solutions, but perhaps, chs("../node/stringparm#") BECOMES chs("../node/stringparm"+stamp("../copystamp","copy",0)) This will allow stamping of string parameters using the copy SOP, with one variable in the copy SOP called "copy" with a value of "$CY+1" (or whichever variance you wish to stamp by)
  21. Flip Fluids leaking through geometry

    Can't upload .bgeo files: angel_first_bowl_pour_origin.zip
  22. Hey Marc, still too busy for this? :x
  23. I've been trying to switch the input for a Sweep SOP between a Null SOP and several Curve SOPs to disable/generate a bunch of profiled lines. However, on switching to the Null SOP, the Sweep SOP still produces geometry (that's handled by other nodes further downstream) even though the input contains no geometry (I middle mouse clicked on the Switch to confirm this). One solution I could find was to refresh the Sweep SOP by double clicking on Bypass, then it decides that there is no geometry coming in and accordingly produces no output. However, I have to do this each time the Null is switched to. The other solution is to have a second switch after the Sweep and switch to the Null there. I don't know why this has to be a workaround, it feels a little less intuitive than just switching the input of the Sweep to a Null. Anyone else encountered this? HIP file: sweepbug.hip
  24. Is this a Sweep bug?

    Thanks for confirmation! -RFE'd
×