Grasshopper

algorithmic modeling for Rhino

I've been having a strange issue using planarsrf component: it usually disorder the input list. Pretty annoying because using spheres or other kind of geometry the list remain ordered; I've been using circles filled with planar surfaces to represent values with colors and size. I've detected the bug because the colours coming from the gradient component match perfectly spheres an other king of geometry, but the result is distorted using planarSrf component inside circumferences.

I'm ussing last GH version and Rhino5 x64 supported by W7 x64.

I hope this helps. I have the file at work if anyone needs it, I could share it without any problem the next week.

Views: 734

Replies to This Discussion

Yeah, PlanarSrf works on lists of curves. If some curves are inside other curves, they will result in a single brep with a hole. Because of this behaviour there is not always a clear relationship between input and output and the Rhino SDK function which performs the Planar Surface logic doesn't maintain list order nor provides a way to keep track of which curves ended up in which Brep.

I can ask the Seattle guys for an improved function, but it's not something I can fix myself unfortunately.

If you only have a one-curve->one-brep logic, why not just plug the curves directly into a Surface parameter? Then it will perform a one-on-one planar surface logic.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Hi!

None curve (circle) was inside other circles or curves. All curves were single circles and was the same amount of them than colours. It was like a pretty straight forward matching. I get the point about several curves creating a BREP and how Seatle guys have deal with it, but if you have a 1-1 relation between results and inputs, the list must (in my opinion) remain ordered.

I have no problems with this behaviour, but teaching, sometimes exceptions with "complicate" explanations are not the best thing for people learning GH for the first time.

Thanks for the fast reply :)

I was thinking this is the way it supposed to be and I found it so useful in many cases.

Is that happening even if you graft the curves in separate branches?

Mostapha

Yep, no matter if the list is flat or you have a grafted one. Simply, if data pass through PlanarSrf component it gets messed.

Interesting! This is what I get on my system:

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service