Grasshopper

algorithmic modeling for Rhino

Not sure if this is a bug, but I am trying to have a simple unit (made of three intersecting lines) copy and locate itself at each of its three endpoints. This copy should be oriented with the line it is attaching to (see script)...anyway, when I am changing the angle of the original unit the oriented copies strangely appear and disappear depending on the azimuth angle of the original unit lines.

Move the red colored slider to see that at certain numbers (ie 8, 15, 40) one of the copies will appear and disappear.

I cannot figure out why this is happening - Is this a bug?

Thx 

Views: 499

Attachments:

Replies to This Discussion

Bueller? 

I think the problem is that you're using the [Orient Direction] component, which is somewhat underdefined. Using only vectors to indicate a new direction means the component has to invent a rotation around those vectors, which almost always works fine except when the orientation vectors are anti-parallel-ish. Then the rotation becomes undefined and the results become unpredictable.

I recreated you file using Plane orientation (which is not undefined) however due to the nature of your file, it is not possible to make it entirely unambiguous. If the azimuth rotation is 90 degrees, it will still fail.

Attachments:

Ahhh..this is working perfectly. Using the Cross Product is a clever solution, and the step I was completely missing. 

I am now running multiple generations through HoopSnake, and with this change, everything seems to be orienting well.

I can't tell you how much this helps!

Thanks much. 

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service