Planes
From Rhinoscript 101, this cleared up some of the ambiguous language in the help file:
A plane definition is an array of one point and three vectors, the point marks the origin of the plane and the
vectors represent the three axes. There are some rules to plane definitions, I.e. not every combination of points and vectors is a valid plane. If you create a plane using one of the RhinoScript plane methods you don’t have to worry about this, since all the bookkeeping will be done for you. The rules are as follows:
- The axis vectors must be unitized (have a length of 1.0)
- All axis vectors must be perpendicular to each other.
- The x and y axis are ordered anti-clockwise.
The best way to define the attachment face for the imminent script, that I have devised is to have the user create a right triangle at each of the connection points. The advantage of this over a circular definition (besides being easier to code) is that it allows the user to define a direction to the connection face if so desired. Using this method, the corner that hosts the right angle will be the center of the connection, and the other two points will define the X & Y axis. As the rules above state, these points must be assigned in a counter-clockwise fashion or else the normal vector of the plane will be reversed. While this is necessary, I am slightly worried about the possibilities for user error that this presents, but it will have to do for now.
This necessary, but somewhat tedious phase is needed to get my script to a point where I can actually define the techtonic connections that are necessary for something to actually be buil, before I begin evaluating design fitness and applying stochastic transformations.