Jump to content

noc2

Members
  • Content count

    37
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

1 Neutral

About noc2

  • Rank
    Peon

Personal Information

  • Name
    Ajlan Altug
  1. Ok, I apologize. I figured it out. The values were indeed being spewed out, I seem to have not checked the out hard enough (really tired :() AJ
  2. Hi; I have a scene in which I'm smoothing out a portion of a geometry progressively over time using the solver SOP. When I connect a visualizer node I can see the attribute I'm using to constrain the smoothing effect changing over time, but when I look at the spreadsheet, the attribute @decay is '0' all throughout. What gives?? Thanx in advance, cheers; AJ
  3. Hi everyone I have a project at hand in which I'm supposed to pull vein out from incision. I want the vein to act like a strand of macaroni, which is the way vein like tissue behave in general, yet my initial tests using the Vellum solver always tend to yield results that wobble. I opted to use tetrahedral softbody so as to be able to preserve the overall volume of the vein as it's grabbed and pulled out by the scissors but as soon as the scissors come to a halt, the vein wobbles until it comes to a rest although I jacked up damping ratio on all constraints. How can I go about accomplishing this in vellum, or am I better off switching to the FEM solver instead for this task? Thanx in advance and cheers AJ
  4. Hi; I have a set of nodes that I want to turn into an HDA, but am having trouble with group utilization. On my pre-HDA setup, some of the nodes are making use of incoming primitive and point groups. What I need is this: 1-I want the user to be able to select these groups from the HDA's parameters so that they can be passed into the HDA to be used by these nodes. 2- And Once they're passed, I really don't know how to get the nodes to recognize these selected groups. So any help would be wildly appreciated. Thanx so much in advanxce; AJ PS: I looked here in the forums, but this didn't help. I wasn't able to see any of my groups in the string list (probably missed a lot, that's the reason I guess )
  5. Hi; I have a set of nodes that I want to turn into an HDA, but am having trouble with group utilization. On my pre-HDA setup, some of the nodes are making use of incoming primitive and point groups. What I need is this: 1-I want the user to be able to select these groups from the HDA's parameters so that they can be passed into the HDA to be used by these nodes. 2- And Once they're passed, I really don't know how to get the nodes to recognize these selected groups. So any help would be wildly appreciated. Thanx so much in advanxce; AJ PS: I looked here in the forums, but this didn't help. I wasn't able to see any of my groups in the string list (probably missed a lot, that's the reason I guess )
  6. Thanx Konstantin. I kind of suspected that (as a newbie of course) what I was after called for a scripted operation. The foreach loop, by nature, seems to bear within itself a recursive type of operation where the prim count increases with each division operation thus leading to the loop doing its execution on the next prim it produces. Thank you again for you reply, highly appreciated. cheers; AJ
  7. I've already achieved this using vex, but I'm at odds as to how to go about accomplishing the task through this route, hope that makes sense (kinda)
  8. Hi; I'm trying to cut a plane into n number of pieces using a knife sop. I'm using a foreach loop for this, but since I want the divisions to be made consecutively rather than recursively (I want the single prim to be divided into n parts equally instead of recursive division like one into the next), I kept the plane and the knife sop out of the loop. From the outset, I seem to be getting what I want but the resulting geometry ends up having 11 overlapping prims where there should be 4 prims instead at 4 iterations. I must be doing something wrong, but can't quite figure out what. Could you please help out? Thanx and cheers; AJ
  9. Thanx so much your replies, morn66 and Atom. Now I get the picture. What I was intending to do was to displace the certain points on a piece of geometry according to a predetermined per point height attribute, and now I know that it is literally "height" But now, I'm having trouble trying to figure out how I can keep the displacement centered around the undisplaced point positions :-/ Attribute blur just doesn't help at all. The height attribute was created on the points in a corners group created automatically by a previous polybevel sop. You can see in the attached image that the displacement always goes above the median when "center Noise" is not checked or inside when checked. How can I tell Houdini to have the displacement take place along the median point positions? Do I need to dive inside the vop net and fiddle with the vop nodes? Thank you
  10. Hi there; I'm kind of confused with the way mountain SOP works. As I've read on some of the topics here on this forum, the mountain SOP doesn't recognize (at least as of version 16) point attributes and that's what I'm trying to get it to do essentially. I've also read here that the VOP network that the SOP is comprised of, due to its very construction, recognizes point attributes with a prefix of "parm_" instead of their raw names. No matter what I've tried so far, I haven't been able to pass a point attribute to control say, the "height" attribute or "gain" attribute with an expression like: point(0, @ptnum, "attrib", 0) Any help would be wildly appreciated Cheers; AJ
  11. Thanx so much Albert and Tomas. I got the gist Cheers and thanx again; AJ
  12. Hi; I'm having a wee bit of a problem trying to get Houdini to detect internal edges so as to dissolve them with a dissolve sop later on. I can have Hou to pseudo-detect these edges through halfedges, but just can't translate it into a viable edge selection to dissolve them. Any help would be wildly appreciated Thanx and Cheers; AJ
  13. Subdivision Sop Producing bad results

    Ah, woe is me! So sorry to have causes a ruckus out of nothing guys. A modeler colleague of mine just reminded me today, that when it comes to inner corners on a geometry that has such a 90 degree angled stepping form, the bridging corner edges between adjacent loops need to be beveled as well and showed me that this is universal. Was so tired yesterday and couldn't see straight, hence why I couldn't see it I guess. Again thanx for all the replies and my apologies AJ
  14. Subdivision Sop Producing bad results

    Thanx Noobini, but the model really calls for all corners to be beveled But thanx all the same...
  15. Subdivision Sop Producing bad results

    Hi Noobini; Yup, I tried that as well to see what it would do, to no avail I'm afraid. The result is no where near what should be. This is really quite a shame for Sidefx who really get everything else quite right in Houdini.
×