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

Community Reputation

0 Neutral

About bjs

  • Rank

Personal Information

  • Name Bastian J. Schiffer
  • Location Germany
  1. Thanks Vitor for taking the time to answer and sorry for not being clearer on the problem. I've attached the file this time, which will hopefully clarify what I am trying to do (the red CUTTER node is responsible for what gets cut from the geometry). I've found a way to close the holes step by step though adding a PolyCap after each Clip. It's not pretty but it seems to work. I guess I was just hoping to get better topology (the "limit insetting" option on the PolyExtrude is enabled, but there is still some invisible geometry which I guess is causing the problems with the PolyCap) – but the problem may lie deeper as you suggest ... I'll consider what you said and see if I find a smarter way to get the result. Thanks for your input! Solid-Extrude-1.hiplc
  2. So the PolyCap SOP seems to work quite well in this case. Only when there should be a hole in the cap, there instead is an overlap. Any ideas how to solve this? Thanks in advance!
  3. I have been researching for a couple of days on a seemingly simple problem: I would like to add some thickness to a mesh (which will end up being more complicated than the example below) and then clip it from various sides. After clipping, I would like to cap the mesh, so it appears to be a solid body (in the example with the box, it would be hollow inside). Two problems arise: – How can I get a clean extruded face without any of the intersections (see example "Extrude-1")? – For the capping, I tried the Dissolve and PolyCap SOP. But both cap the whole side (not considering the interior "negative space") (see example "Extrude-3"). I tried creating a manual cap using the unshared edges and a PolyLoft SOP, but was wondering if there were any better ways to do this? The technique will eventually be used for open, plane-like geometry – not hollow bodies (see example "Extrude-2"). Which might make it a bit more complicated. I'd be grateful for any kind of help – thanks, Bastian.
  4. Since it was originally my goal to limit the nearpoints() function to an exisiting point group, it might be worth to mention that Moritz pointed out to me how that is done successfully (see screenshot for this). Note that activeGroup is the name of the existing point group ...
  5. Exactly this was driving me crazy. The help fails to mention that the "@" character must be masked, as suggested by F1 ...
  6. Sorry for not reporting back sooner ... I masked the "@" character, as F1 suggested, and it worked perfectly! Thanks to everyone for their help! Added the screenshot for future reference ...
  7. I am also wondering if it's the smartest way of filtering the result? Of course, another option would be to get all the nearest points and filter afterwards. But I thought since the manual explicitly states the option to do so, it would be a really smart and efficient way to do it: int [] nearpoints(string geometry, string ptgroup, vector pt, float maxdist) ptgroup: A point group pattern to limit the search to. Can be a SOP-style group pattern such as 0-10 or@Cd.x>0.5. An empty string will match all points.
  8. Same result with your proposed solution, Pavel – no error, but not the intended result: string ptgroup = detail(0,"at")+"Cd.x<1.0"; int nearest[] = nearpoints(0, ptgroup, v@P, 1); i@found = len(nearest); i@first = nearest[1]; Added the screenshot as well. Shouldn't there now also be a detail attribute on the geometry (lower pane), or am I missing something?
  9. Thanks to both of you! Due to the time difference I could only now check your answers. Yunus, as suggested, I simply omitted the "@" and put the expression in quotation marks: int nearest[] = nearpoints(0, "Cd.x<1.0", v@P, 1); i@found = len(nearest); i@first = nearest[1]; While I don't get an error, this doesn't yield any result either. I attached a screenshot to illustrate the setup.
  10. Hello – after quite a bit of searching and a pretty long struggle I've decided to post my simple question concerning the "nearpoints" function (http://www.sidefx.com/docs/houdini15.5/vex/functions/nearpoints) that I am using on a Point Wrangle SOP. The manual states that, under "ptgroup", one can specify a "point group pattern to limit the search to": int [] nearpoints(string geometry, string ptgroup, vector pt, float maxdist) While inputting a simple pattern like "0 11 18" works (limiting the "nearpoints" function to these points like it's supposed to), I can't get it to work when I put in the sample expression "@Cd.x>0.5". Has anyone ever used the "ptgroup" argument with an expression, because all the examples I found always only used GEOHANDLE + POSITION + MAXDIST with an optional MAXPTS at the end? Here's the code on the Point Wrangle SOP that works: int nearest[] = nearpoints(0, "0 11 18", @P, 1); i@found = len(nearest); i@first = nearest[1]; This one doesn't, giving me a wrong result and a green "implicit cast from vector to float" error: int nearest[] = nearpoints(0, @Cd<1.0, @P, 1); i@found = len(nearest); i@first = nearest[1]; I am afraid it is a very beginner's mistake, so I am grateful for any answers! Thanks, Bastian.