Grasshopper

algorithmic modeling for Rhino

What is problem of this definition? Please help!

Views: 398

Attachments:

Replies to This Discussion

Hi JackyCheung,

There is a data matching problem with the Region Difference Component. With this particular case I needed the Path Mapper to get all the curves onto the correct branches to intersect. I would think that all the work David has put into getting better path management form components that this definition would have worked in the new version 0.9 which is due for release in the next week or so.

Attachments:

Hi Danny Boyes

Thanks for the prompt reply.

The problem if fix for plugin, Is this possible or not?

I use Rhino 4 SR8 and Grasshppper 0.8.0066

 

Thank

Does the definition I posted work for you? It was written in version 0.8.0066.

Is work, Thank you so much~!

but, Just some warning in PLine, always this component... I have no idea!

 

PS: Your help has been of great value. Thank you!

Ok to fix this the data/paths issue that I talked about before is a result of the surface curve intersection component. moving the Path Mapper to just after the results and sorting them will fix this.

Attachments:

OMG~!!! you did that~!!!! OMG~!!!! How did you make it? This problem bothering me for a long time, is finally! Amazing~!!!! Thank you~!

Like I said, its a bug that I think will be fixed come the next version.

Thank for your help!

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service